Workflow for Website
- The merchant will create a session by calling the Create Session API at the backend.
- The API will return a redirect URL and a unique ID for subscription.
-
The redirect URL is used to render the checkout page by passing the URL in the
init()method of theTBIframeinstance. Navigate to TBIframe Quickstart - This will open an iframe within the merchant’s page, from where the customer can make the payment.
- TB will display the transaction status in the iframe. However, the merchant can also display the payment status page based on the status/data received through the Handler reference.
- TB triggers a Webhook on the configured server URL provided by the merchant. The transaction status is also provided through the Handler references.
- Subsequently, an invoice is generated for a sucessful transaction and sent to the customer.
- In case the payment fails, TB does not mark the session as FAILED OR CLOSED and allows multiple transactions until there is a successful transaction on that session. The customer can retry the transaction within the same session.
- After a successful transaction, the iframe automatically closes within 10 seconds.
- In case there is no activity on the iframe by the customer, or the customer closes the page, the session remains active by default for 24 hours. However, this timeframe can be customized and reduced to 10 minutes through backend configuration. To enable this configuration, you need to raise a request with us.
Payment Flow
Workflow for Android SDK
- The merchant will create a session by calling the Create Session API at the backend.
- The API will return a redirect URL and a unique ID for the session.
- Initialize the SDK onCreate() in your main activity file.
- The redirect URL is used to render the checkout page by passing the URL in the open() method of the TransactBridge Instance
- This will open a webview within the merchant app screen. Where merchant can complete the payment process.
- TB will display the transaction status in the webview. However, the merchant can also display the payment status screen based on the status/data received through the EVENT HANDLING REFERENCE
- TB triggers a Webhook on the configured server URL provided by the merchant.
- Subsequently, an invoice is generated for a succesfull transaction and sent to the customer.