Developer resources
Browser checkout reference
The separate public session surface used by the hosted page and checkout script.
Use the hosted client where possible
Base URL: https://api.veyqo.org/checkout/v1
Only browser session creation uses a publishable key. Session and active payment-link IDs address subsequent calls. Never send a Veyqo secret API key to these browser endpoints.
Browser-defined prices are untrusted for fulfilment. Prefer server-created sessions for actual orders. Methods and next_action are provider-dependent; use returned values and the Veyqo-hosted client instead of assuming every gateway offers the same flow.
Understand method and action fields
methods is the currently offered method list, with method identifiers and provider-dependent bank/network choices. Send a returned method identifier to charge; do not assume card, bank_transfer, ussd or mobile_money is enabled for every provider and currency.
next_action is null before an action is needed. A card action supplies provider plus config for the provider card client, or frame_url for a hosted form. Paystack config includes key, email, amount, currency, reference and channels; this key is intentionally public.
A bank_transfer action supplies account_number, bank_name, account_name, amount, currency, expires_at and possibly note. A ussd action supplies code and bank_name. An otp action asks for the customer OTP; send it to the session otp endpoint. approve_on_phone supplies a note while the customer approves the prompt. A none action requires no further customer input. Fields may be absent or null when the upstream gateway does not supply them.
Never collect raw card details on your own server. Use the hosted Veyqo page or checkout script to handle provider UI. A completed customer action still requires trusted payment verification before fulfilment.