Why does Stripe show a mandate error after 3D Secure on INR checkout?
Problem Statement
On a Multi Business Entity site, a card payment for one business entity can still process through another entity's Stripe account or the site-level Stripe account. INR Hosted Pages checkout can also fail after 3D Secure (3DS) with a Stripe error such as "The parameter mandate is not provided or invalid".
Related Scenarios
- Payments for one business entity route to the site-level Stripe gateway instead of the entity Stripe account.
- Checkout starts succeeding after you update Smart Routing, then the payment fails immediately after the customer completes 3D Secure.
Solution
Work through these checks in order.
Confirm which Stripe account processes the payment
Multi Business Entity Smart Routing picks the gateway account when a customer adds or updates a payment method. Saved cards stay linked to the Stripe account where they were first vaulted. Changing Smart Routing rules does not move existing payment methods to a new gateway.
By default, a business entity uses the site-level Smart Routing rules, which can route to the site-level Stripe account. Before you collect a new card, confirm that the entity's Smart Routing rule for cards in INR selects the intended Stripe account, and customize it for that entity if it does not. See Multi Business Entity Gateway Configuration.
Once the rule selects the right account, have the customer add a new payment method from checkout or an update flow while you are working in that entity, so later charges route through that entity's Stripe account.
Enable the Stripe e-mandate workflow and 3D Secure
Indian-issued cards in INR follow RBI e-Mandate rules. See Stripe RBI e-Mandate Impacts.
- Contact Chargebee Support to enable the e-mandate workflow for your Stripe and Chargebee accounts.
- Switch to the business entity. Click Settings > Configure Chargebee > Payment Gateways > Stripe, and enable 3D Secure. See Stripe gateway configuration.
- On the customer, check Auto collection before you retry checkout. See Auto Collection Status. For what happens to Auto collection when you remove a card from the customer page, see Removing card details.
- Ask the customer to complete Hosted Pages checkout again, or click Request Payment Method Update, so the card is collected under that entity's Smart Routing rules with 3D Secure enabled. Request Payment Method Update updates the saved card; it does not retry the failed payment on its own.
- Confirm that the new payment method appears on the customer under the intended Stripe account. Then retry the payment and confirm the retry succeeds.
Important Notes
- Until checkout completes and the card is saved, the customer has no new card on file.
- Direct Debit mandate errors on Stripe are a separate case. See How do I resolve a mandate error for Direct Debit payments via Stripe?.