Payment Methods
Your gateway can receive payment through several channels:| Method | Endpoint | Source |
|---|---|---|
| Checkout redirect | /orders/checkout | Redirect to a Payment Gateway |
| Internal transfer | /transfer/create | Your own payment apps / mobile apps |
| Partner transfer | /transfer/create | 3rd party with reserve account |
| Third-party settlement | /payment/create + /payment/settle | 3rd party payment app |
| Direct webhook | /transfer/webhook | Settlement provider |
Checkout Redirect
The most common flow for e-commerce merchants. The merchant sends an order to your/orders/checkout endpoint, and you return a redirect URL to a Payment Gateway’s checkout page. The Payment Gateway handles collecting payment from the end user.
The Payment Gateway can be your own service or a third-party. See Payment Gateway API to learn how Payment Gateways work.
Implement a redirect mechanism
Internal Transfers
Process transfer requests from your own mobile app or web wallet. When your webapp or mobile app calls this endpoint, ensure the payment is or has been collected, eg by deduction balance, visa etc. The example below assumes we deduct the users balance.,Third-Party Partner payment apps
When a partner payment app doesn’t have a direct account with you, they use the two-step process:Step 1: Create Pending Payment
Step 2: Settle with Proof
Crediting Merchants
After any successful payment, credit the merchant’s account:Notifying Merchants
Always send a signed proof to the merchant’s webhook:Next Steps
- Merchant Onboarding - Onboard merchants
- Transfer Webhook - Receive settlement notifications