Use server-created checkout references
Create payment links through an authenticated merchant or developer-app context. Present only the opaque public reference to the customer; do not expose internal tenant or provider identifiers.
Developer preview API v1
Sandbox only. No real funds moved. No production access is granted here. Access requirements
Customer presentment
Keep customer UX separate from payment authority
Hosted checkout can present a payment, but verified server state and reconciliation control fulfilment.
Keep payment state authoritative
Browser redirects and customer-facing success pages are not proof of payment. Fulfil only from an authenticated status read or verified webhook after ambiguity controls pass.
Respect country and aggregator policy
Available currencies, rails, branding, expiry, consent, and customer instructions are constrained by the active country cell and aggregator programme.