Overview
A Payment Gateway helps end users pay merchants. This includes wallet apps where users scan QR codes, as well as hosted checkout pages where users are redirected to complete purchases. Your users don’t need their own OCID - they use your service to make payments.OpenAPI Specification
View the complete Payment Gateway OpenAPI specification
What You Build
As a payment gateway, you provide:- Payment UI - Hosted checkout pages or mobile wallet apps
- User management - Maintain wallets or payment methods for your users
- Payment flows - QR code scanning, checkout redirects, or both
- Settlement - Send payment proofs to merchants or Merchant Gateways
Base URL
Host your API at the endpoint you register in the Router Registry:Endpoints
| Endpoint | Method | Description |
|---|---|---|
/metadata.json | GET | Your gateway’s public metadata |
/capabilities | GET | Partner-specific capabilities |
/checkout/create | POST | Create hosted checkout session |
/orders/create/{sessionId} | POST | Receive orders from merchants (QR flow) |
/transfer/create | POST | Process transfers |
/transfer/webhook | POST | Receive transfer notifications |
Payment Flows
1. Hosted Checkout (Web Redirect)
Merchant Gateway sends an order to you. End user is redirected to your checkout page to complete payment.3. Customer Displays QR (Merchant Scans)
Your app generates a QR code for the user. Merchant scans it to request payment.4. Merchant Displays QR (Customer Scans)
Merchant displays a QR code with order info. Customer scans and pays.QR Code Format
Your App’s QR Code (for merchant to scan)
Merchant’s QR Code (for your app to scan)
Inventory QR Code (permanent)
Settlement
To complete a payment, you need to settle with a provider the merchant accepts. Check the order’saccepts array:
Authentication
Sign your requests with these headers:| Header | Description |
|---|---|
X-OC-ID | Your OCID |
X-OC-Timestamp | Unix timestamp in seconds |
X-OC-Nonce | Unique request identifier |
X-OC-Signature | Signature of canonical request |