Payment | Understanding The Payment Flow With Subotiz API

Payment flow

1. When your client-side application has collected the customer's payment information, it sends a payment request to your server. Your server then uses the Subotiz API to create a trade order and initiate the payment process.
2. Subotiz submits the payment request to the relevant payment provider using the provided payment information and returns the submission result to your server, including applicable trade order data.
3. Your server polls the created trade order via the Subotiz API to check its status and determines the final payment result based on the trade order's status.

Redirecting payment flow

1. When a customer is ready to pay for a subscription renewal, your client-side application sends a payment confirmation request to your server. Your server then calls the Subotiz API to create a trade order and initiate payment, passing the return_url parameter (the URL to redirect to after 3D Secure authentication is completed).
2. The Subotiz system submits the payment request to the relevant payment provider based on the trade order information and returns the processing result to your server.

Key note: For transactions requiring 3D Secure (3DS) authentication, the response will include a next_action object of type redirect, containing the next_action.redirect.urlfield (the URL to redirect the customer to for 3DS authentication). Your server must pass this URL to the client for redirection.

3. Your client-side application redirects the customer to the provided 3DS authentication URL to complete the verification process (e.g., entering an SMS code, confirming the transaction). After completion, the 3DS system notifies Subotiz of the result (success or failure). Subotiz then updates the trade order status and redirects the customer back to the return_url provided in Step 1.
4. Your server polls the created trade order via the Subotiz API to check its status and determines the final payment result based on the trade order's status.