checkout_url to redirect the customer to, or embed in your payment flow.
Request
Authorization: Bearer <api_key> header.
Pricing
The base settlement currency code (e.g.,
USD, NGN). Must be a supported settlement currency.The base amount as a decimal string (e.g.,
"50.00"). Minimum 1.00 for USD, 1000 for NGN.Currency-specific price overrides. Only allowed when
base_currency is USD. Keys are currency codes, values are decimal amount strings (e.g., { "NGN": "75000.00", "GHS": "620.00" }). Fiat currencies only.Customer
Customer’s email address. Maximum 255 characters.
Customer’s first name. Maximum 255 characters.
Customer’s last name. Maximum 255 characters.
Options
URL to redirect the customer to after a successful payment. Must use
http:// or https://. Maximum 2048 characters.URL to redirect the customer to if they cancel. Must use
http:// or https://. Maximum 2048 characters.Arbitrary key-value pairs to attach to the checkout (e.g.,
order_id, user_id). Maximum 10KB total; maximum 20 keys. Values may be strings, numbers, booleans, or nested objects/arrays.How long the checkout remains open, in minutes. Accepts 1–1440 (up to 24 hours).
Your own reference for this checkout (e.g., an order ID). Must be unique within your organization. Maximum 128 characters. Auto-generated if not provided.
Test mode only. Force a specific outcome:
success, failed, or underpaid.Response
Unique identifier for the checkout session.
Your organization ID.
URL to redirect your customer to complete payment.
Initial checkout status. Typically
pending.ISO 8601 timestamp when the checkout expires.
ISO 8601 creation timestamp.
Error codes
| Status | Description |
|---|---|
400 | Invalid pricing, unsupported currency, validation failure, or simulated_outcome used outside test mode. |
401 | Invalid or missing API key. |