Skip to main content
The Compliance Check is a secure iframe-based component that is displayed automatically whenever additional customer information is required before initiating a payment. Merchants do not need to manually create, mount, or manage this component. The SDK detects whether compliance is required and handles the complete flow automatically.

​
How Compliance Works

When the merchant calls TBDropin.pay():
  1. The SDK validates the payment components.
  2. The SDK decodes the provided Session Token.
  3. If compliance is not required, the payment flow continues immediately.
  4. If compliance is required, the SDK automatically opens a secure Compliance Checks popup.

​
How Compliance Requirements are Determined

The SDK derives the compliance configuration by decoding the Session Token provided to TBDropin.pay(). Based on the decoded configuration, the SDK determines which compliance fields should be displayed.

​
Field Availability

  • Customer Name
  • Email
  • Mobile Number
  • PAN
  • Mobile OTP Verification
The merchant does not need to configure or render these fields manually. The SDK automatically evaluates the configuration and displays only the required fields.

​
Automatic Flow

  1. Merchant calls pay().
  2. SDK validates payment components.
  3. SDK decodes the Session Token.
  4. SDK determines whether compliance is required.
  5. Compliance popup opens automatically.
  6. Customer submits the required information.
  7. SDK resumes the payment automatically.
  8. Payment Status popup is shown.

​
Security

The Compliance Form follows the same security model as the payment components.
  • Rendered inside a secure iframe.
  • Merchant never receives raw compliance data.
  • Data is encrypted before being sent to the SDK.

​
Merchant Responsibilities

The merchant only needs to provide:
The SDK automatically detects, displays, submits, and manages the Compliance workflow.

​
Notes

  • The Compliance Form appears only when required.
  • The popup closes automatically after successful submission.
  • If the customer closes the Compliance popup, the payment is cancelled.
  • The SDK reuses previously submitted compliance data only for the same payment session.