CoolCMS API

ExpressServiceRegistry
in package

FinalYes

Module word → {@see ExpressServiceProviderInterface}, plus the overview for the administration.

Lazy over the container like PaymentGatewayRegistry: providers depend on module managers, and resolving them eagerly would build half the Api layer for every payment request.

There is deliberately no DB table of express services — the services are the modules' quick prices; a second list would only drift away from them.

Table of Contents

Properties

$container  : Container
$paymentGatePhoneManager  : PaymentGatePhoneManager
$providers  : array<string, ExpressServiceProviderInterface>|null

Methods

__construct()  : mixed
all()  : array<string, ExpressServiceProviderInterface>
describe()  : array<int, ExpressServiceDescription>
Every offered service with the gateway number for its price — a service without a number cannot be paid, which is exactly what the administrator needs to see.
findGatewayPhones()  : array<int, PaymentGatePhone>
findPhoneForPrice()  : PaymentGatePhone|null
Number for an exact price. A one-off (MO, level 0) number wins over an MT level of the same price.
get()  : ExpressServiceProviderInterface|null
loadProviders()  : array<string, ExpressServiceProviderInterface>

Properties

Methods

On this page

Search results