Skip to main content

Payment Flows & UX Models

Tradex World supports two distinct integration flows depending on the payment method capabilities and merchant preference. The API response will indicate which flow applies via specific fields (redirect_url vs qr_code_data).

A. Redirect Flow (Hosted Checkout)​

In this flow, the user is securely redirected to a Tradex World hosted payment page to complete the authentication with their bank/wallet provider. Upon completion, the user is automatically returned to the Merchant site.

  • Use Case: Web-based merchants who prefer not to handle sensitive banking UIs directly or for specific APM methods requiring browser redirection (e.g., certain Net Banking flows).
  • Mechanism:
    1. Merchant initiates payment via API and provides a return_url.
    2. Tradex World returns a redirect_url in the response.
    3. User is sent to redirect_url, authenticates with their bank/wallet, and confirms payment.
    4. Upon success/failure, the user's browser is redirected back to Merchant's return_url.
    5. Merchant receives confirmation via Webhook simultaneously.
  • Key Fields:
    • redirect_url: Present in response for redirection methods.
    • return_url: Required in request body to redirect the user after payment processing.

B. Host-to-Host (H2H) / Embedded Flow with Confirmation​

In this flow, the user remains within the Merchant's application or website interface. The transaction is handled without leaving the merchant's domain. This flow includes a manual confirmation step for specific APMs.

  • Use Case: Mobile Apps, Progressive Web Apps (PWA), or when a seamless UX is required without redirecting users to external pages.
  • Mechanism:
    1. Merchant initiates payment via API.
    2. Tradex World returns a pay_data which contains params needed to display to customer to proceed payment. 2a. Out system can ask for additional customer data need to be clarified before pay_data can be obtained. In such case we send clarify param with list of required fields. Please collect them from the customer and send them with POST /payments/{transaction_id}/clarify request to continue payment
    3. User scans the QR code or clicks to open their banking app within the merchant's UI.
    4. User Action: User completes transfer in their bank/wallet and presses "I have paid" on the Merchant UI.
    5. Confirmation Request: Merchant collects the Transfer Reference/ID from the user (visible in their bank app) and sends a POST /payments/{transaction_id}/confirm request to Tradex World with this ID. 5a. Sometimes we need additional information upon confirm (for example UTR from customers bank app). List of confirm required params will be provided in confirm param
    6. Tradex World validates the reference against the provider.
    7. Status updates are received via Webhooks upon validation completion.
  • Key Fields:
    • redirect_url: Not provided or ignored.
    • Confirmation Step: Required for specific APMs to finalize the transaction state after user action.