Settlement & fees model
Model | How it works | |
|---|---|---|
Invoice | OnePipe (via Polaris client) will invoice the calling app periodically for all calls to the endpoint. At settlement, Polaris will debit aggregated fee from the app’s client bank account, credit the settlement account. The OnePipe-Polaris agreed fee will then be debited from the settlement account and split to relevant parties. Amount or Commission | The Polaris should have it's own way of debiting the auth creds (account number), then execute the transfer. Polaris needs to send a share of income to the settlement account at the host which will then be shared with OnePipe, host and ISO |
Process flows
Sequence of calls
App of JS calls
/transactwith the right auth detailsProvider responds with
WaitingForOTPif not overriddenApp calls
/transact/validateto supply OTPProvider responds with any of the completion codes
SuccessfulorFailed.To query the status of a transaction, the app can call
/transact/queryWhere the provider supports it, the app can call
/transact/reverseto request a reversal
The process flow follows the scenario 2 approach, where the provider micro service (optionally) implements 2FA for a given transaction.
| Gliffy | |
|---|---|
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Special notes
...
|