Skip to main content
The Add Payment Mandate flow allows an existing customer to securely add or replace the payment mandate associated with a subscription. This is commonly used when the customer wants to change their payment mandate or when the existing payment mandate has expired or become invalid. After the payment mandate is successfully authorized, future recurring payments are collected using the newly saved payment mandate.

​
Common Use Cases

​
Workflow

​
How It Works

  1. The merchant calls Add Mandate API and generates an Add Payment Mandate session.
  2. Transact Bridge returns a payURL.
  3. The customer is redirected to the hosted checkout.
  4. The customer selects a payment mandate (for example, UPI AutoPay or Card).
  5. The customer completes the mandate authorization.
  6. Once authorization is successful, the payment mandate is securely stored.
  7. All future recurring payments use the newly added payment mandate.

​
State Transition

​
Notes

  • Adding a payment mandate does not change the subscription status.
  • The subscription remains ACTIVE throughout the process.
  • The customer must successfully complete the hosted checkout and mandate authorization.
  • Future recurring invoices are collected using the updated payment mandate.
  • If the authorization fails or is abandoned, the existing payment mandate remains unchanged.