Merchant settlement and payout across five markets, on one approval chain.
Your reference stays on the merchant statement, so support tickets stop being reconciliation work. Onward provision of accounts to your own clients is a separate approval, stated up front.
Settlement funds arrive in the name of the entity holding the payment institution, e-money or money services authorisation your product relies on.
Collections for merchants of an unlicensed partner are declined.
Five gates, and the one that decides a payment platform.
| GATE | WHAT WE ASK FOR | STATUS |
|---|---|---|
| 01 LICENCE | Regulator, permissions held, and whether they cover the flow you intend to run. | CLEARED |
| 02 JURISDICTION | Where you are authorised, where your clients sit, and every market in the settlement chain. | CLEARED |
| 03 FUNDS MODEL | Whose money moves. Own funds, safeguarded or segregated client funds, or institution settlement. | CLEARED |
| 04 PERMITTED USE | The named flow types written into terms, enforced on the instruction. | DECISIVE |
| 05 COMMITTEE | Approval by profile with conditions, limits, FX margin and a named specialist. | TERMS SET |
What this account may carry.
The commercial line that matters for platforms is between settling your own contracted merchants and providing accounts to your clients. We approve the first on the profile and the second on its own file.
Who owns an exception, and what pricing is written.
Bespoke by profile. Priced against volume bands and payout markets.
Fixed in terms so your merchant pricing holds through the payout leg.
Your own maker and checker roles apply across every currency account.
One person owns held payouts and reference requests to resolution.
Describe the product. We will name the flows in your terms.
Send your licence scope, funds model and corridor list. A named specialist returns the permitted use envelope, limits and the FX margin in writing before anything is signed.