Skip to main content
Learn about the components which are available with Transact bridge. The TB Drop-in SDK provides small, isolated iframe-based payment components such as:
  • Card Number
  • Card Holder
  • Expiry
  • CVV
  • UPI Intent
  • UPI QR
Each atom runs inside a secure sandboxed iframe and communicates with the parent page using a message-based architecture. The parent page interacts with all atoms using the TBDropin SDK. This overview explains:
  • How the SDK loads
  • What atoms are
  • How mounting works
  • How events & communication work
  • What happens during payment
  • Folder & architecture summary

Methods

1. Mount component

A component can be mounted in DOM container
Example

2. Unmount component

To unmount a component from DOM container. Use component.mount to mount again

3. Get component data

To get the data and state of a component

Return

Fields Explained

4. Clear component

Trigger clear on component to empty it. Can only be applied if kind of the component is input

Events

You can register a callback function to various events that occur with a component. The basic syntax is component.on(eventName, callBackFunction)

ready

Triggers when a component is ready for user interaction

change

Triggers on component kind input whenever change happens for the value

click

Triggers on component kind button when clicked

close

Triggered when the payment status screen is closed after the transaction finishes.