INTEGRATION

Connect the payment flow to your business

Choose a hosted payment page, direct API, or both. Every route requires a merchant backend, assigned project credentials, signed postback handling and test evidence before production activation.

Conceptual integration architecture

These labels are conceptual, not production API documentation. Exact endpoints, credentials, request formats, and status verification depend on the connected provider.

1WEBSITE OR APP

2MERCHANT SERVER

3PAYMENT REQUEST

4PAYMENT PROVIDER FLOW

5STATUS EVENT

6MERCHANT SERVER

7ORDER UPDATE

A browser redirect alone should not be treated as final proof of payment success. Merchant systems should follow the connected provider's documented status confirmation flow.

Hosted checkout

A customer is sent to a provider-managed payment flow and then returned to the merchant experience.

View hosted checkout

Hosted payment page

The merchant server creates the payment and redirects the customer to the returned page URL.

Review hosted flow

API-based setup

Authenticate with the assigned API key and project ID, create requests server-side, and keep secrets out of browser code.

Review API setup

Signed postbacks

Validate every server notification, make handlers idempotent, and reconcile uncertain transactions before fulfilment.

Review postback handling

Plan your payment gateway setup

Tell us about your business model, checkout flow, target customers, and integration needs.

Talk to Sales