Prepare for onboarding
Share your website, business model, expected payment volumes and preferred support contact through the merchant enquiry form. Before implementation, agree the enabled payment methods, limits, settlement terms and environment with the onboarding team.
Create a checkout from your server
- Store your own order reference, currency and expected amount. Create a separate attempt record so that retries can be traced independently.
- Request a hosted payment page from your backend using the credentials and API details supplied during onboarding. Include a merchant transaction reference and a customer return URL.
- Save the gateway order identifier before redirecting the customer to the hosted payment URL.
- Display the current order state on the return page. Confirm payment from a verified server-side notification or transaction status lookup.
Test the outcomes before going live
Test a completed payment, a declined or abandoned payment, a delayed result and repeat delivery of the same notification. Confirm that each outcome updates the order once, that fulfilment begins after confirmed payment, and that operations can locate an attempt using either identifier.
Prepare for daily operations
Keep merchant order references available to finance and support. Agree who will review unresolved payments, how often reports will be downloaded, and how collections will be reconciled with settlements.