Payment Method Details
Indian-issued cards Advanced
Indian regulation requires an extra authentication step on every card payment where the customer is present, and a registered RBI e-mandate before a card can be charged on a recurring basis. Checkout handles both for eligible cards, so your integration code stays the same.First payment
The Web SDK shows the bank’s authentication step on the checkout page. The payment staysPENDING until the customer completes it.
- If authentication fails or the customer abandons it, the payment ends
INCOMPLETE. See Incomplete Payments for the decline codes. - If the card issuer declines the payment, it ends
DECLINED.
Subscriptions and e-mandates
The first payment of a subscription registers an RBI e-mandate with the customer’s bank. To register it, set 3D Secure to Processor 3DS (processor3ds) on the Authorize Payment node of your workflow. The e-mandate covers:
- Maximum amount: the plan’s recurring price plus a 5% buffer
- Frequency: the plan’s billing period
- Start date: the end of the trial, if the plan has one
Renewals
Renewals charge the card without the customer present. The bank notifies the customer before each debit, so a renewal staysSETTLING for up to about 26 hours before it moves to SETTLED. The subscription period advances when the renewal settles. See Lifecycle for status definitions.
If no e-mandate is registered
A card without an e-mandate can’t be renewed, so PayNext cancels the payment before any money moves:- The customer isn’t charged and sees an error at checkout.
- No subscription is created. A plan change leaves the subscription on its current plan.
- The payment ends
CANCELLEDwith this status reason: