Skip to main content
TBDropin is a JavaScript-based Drop-in Payments SDK that allows merchants to easily embed secure, PCI-compliant payment components into their web applications. It provides pre-built payment elements (UPI, Cards, T&C, etc.) that are rendered inside secure iframes, ensuring sensitive payment data never touches the merchant’s servers.

​
Subscription Drop-in Flow for website

  1. Merchant injects TBdropin SDK and initializes it with Publish key and mode(environemnt).
  2. Merchant can now use the SDK on their checkout page.
  3. Once the user clicks on buy now/Proceed to pay button at merchants website, now the merchant renders checkout page hosted by them. Where Transact Bridge components are mounted.
  4. Merchant calls the Create Subscription API to generate a session. Which in return gives a unique subscription ID and a session token which is used to complete the payment.
Merchant can generate a session at the time of opening their checkout page or at the time when user clicks on pay button of merchant hosted checkout page.
  1. Merchant collects the payment details from the customer on their checkout page.
  2. Once the user clicks on Pay button. Merchant needs to calls the pay() method(Triggering a Payment) at the checkout with the payment details entered by the user and the session token.
  3. Payment is completed, TB shares the status of the txn which merchant can show that on their own customized page.
  4. TB triggers a Webhook on the configured server URL provided by the merchant. And also the transaction status is also provided in the pay method response.
  5. Subsequently, an invoice based on the subscription (prepaid/postpaid) is generated and sent to the customer.
  6. In case the user does not completes the txn on the page. Merchant can rely on the pendingExpire param passed in the create subs api bases on which the status of the subscription can be traced in case of merchant inactivity.
pendingExpire: Number of minutes after which, if the status of the subscription is PENDING (Customer did not pay), it becomes PENDING_EXPIRED, which is a terminal state, and now customers cannot pay on the same subscription.By default that subs will be marked as expired by the system after 24 hrs. However, with the help of the pendingExpire param, this time can be reduced to a minimum: 10 mins to a max of 7 days.

​
Payment Flow

​
Workflow for Android SDK

  1. Merchant adds the AAR file in their project and the required dependencies in app/build.gradle .
  2. Now initialize the TransactBridge PaymentSDK at onCreate() method in the main activity file.
  3. Merchant can now use the SDK on their checkout screen.
  4. Once the user clicks on buy now/Proceed to pay button at checkout screen , where Transact Bridge components are mounted.
  5. Merchant calls the Create Subscription API to generate a session. Which in return gives a unique subscription ID and a session token which is used to complete the payment.
Merchant can generate a session at the time of opening their checkout screen or at the time when user clicks on pay button of merchant checkout screen.
  1. Merchant collects the payment details from the customer on their checkout screen.
  2. Once the user clicks on Pay button. Merchant needs to calls the payUpi() method.
  3. Payment is completed, TB shares the status of the txn which merchant can show that on their own customized screen.
  4. TB triggers a Webhook on the configured server URL provided by the merchant. And also the transaction status is also provided in the PaymentResultListener
  5. Subsequently, an invoice based on the subscription (prepaid/postpaid) is generated and sent to the customer.
  6. In case the user does not completes the txn on the page. Merchant can rely on the pendingExpire param passed in the create subs api bases on which the status of the subscription can be traced in case of merchant inactivity.