Payment providers
A payment provider is the outside service that actually moves a wallet's money. Each wallet is connected to at most one provider; the platform operator sets the connection up, and the wallet owner sees which provider it is and its account number.
Overview#
A wallet holds the platform's record of a tenant's or merchant's money; the provider is the service that carries payments in and out of it. Tenant and merchant wallets can both be connected to a provider. Each wallet has at most one provider setup. The setup is in two layers: the owner asks for it and sees its status, and the platform operator enters the provider details, which owners never see. Switching an owner to another provider creates a new wallet and retires the old one; see Active and retired wallets.
Providers#
| Provider | How it settles | Account identifier |
|---|---|---|
| Goopay | Payment by payment, in real time: the money is held at Goopay, then confirmed. | The wallet's Goopay technical account. A payment from a wallet whose Goopay setup has no technical account is refused when it is created. |
| OnePay | In batches: the day's payments are grouped per tenant and settlement date, and settled together. OnePay settles tenant payments only. | The tenant's virtual account number (VAN), which attributes incoming funds to the right tenant. |
| Dibee | Not used for new payments. Dibee is the platform's former name; wallets from that time keep it as their provider so their history stays legible. | — |
Goopay and OnePay are the providers payments can be sent through.
OnePay settlement stages#
A OnePay payment moves through Aggregated, Transfer Initiated, Funds Received, Payout Sent and Payout Confirmed, with the time of each stage recorded; a batch that cannot complete is Failed. A nightly run moves each batch on to its next stage. A step that fails temporarily leaves the batch at the stage it reached and is tried again on the next run; a step that fails for good marks the batch Failed and sends a settlement-batch-failed notification. A OnePay payment's page shows these stages, with the expected settlement date, under OnePay Settlement Timeline.
What a wallet owner sees#
The wallet page has a Payment Provider card:
| Situation | The card shows |
|---|---|
| Connected | The provider, its status (active or inactive) and the wallet's account identifier at that provider. |
| Not connected | "Not configured yet". |
| Retired wallet | The provider that wallet had, not the owner's current one. |
- Tenant and merchant wallets show their provider the same way.
- Provider credentials and other setup details are never shown to owners.
- The owner can ask the operator to set up or fix the provider with Request provider setup; see Request payment provider setup for your wallet.
- The platform operator can switch any wallet's provider off and on with Deactivate provider and Activate provider; activation is offered only when it would succeed, which rules out an inactive wallet and a Dibee setup. On a tenant wallet the operator also sees Manage, which opens the provider setup.
- Deactivating a wallet deactivates its provider too; reactivating the wallet does not reactivate the provider.
- While a wallet's provider is inactive, payments are not routed through it.
Permissions#
| Role | Provider status on own wallet | Request provider setup | Configure providers |
|---|---|---|---|
| Tenant Owner, Tenant Admin, Merchant Owner, Merchant Admin | Yes | Yes | No |
| Tenant Accountant, Merchant Accountant, supervisors | No | No | No |
| Platform Operator | All wallets | — | Yes; on a merchant wallet, on/off only from the card |