What is Merchant-Initiated Transaction?
A merchant-initiated transaction, or MIT, is an off-session charge the merchant starts after the customer has already authenticated and agreed to future billing. In subscription billing, the MIT exemption allows many renewals to proceed without a new SCA or 3D Secure challenge. The exemption is typically established when a SetupIntent or initial payment flow captures customer authentication and stores the mandate for future off-session charges.
How does the MIT exemption work for subscriptions?
The customer first completes an on-session authentication step during signup or payment method setup. Stripe records that authentication through a SetupIntent or PaymentIntent configured for future off-session use, which establishes the basis for later merchant-initiated renewals.
When a later subscription renewal runs, the merchant can charge off-session under that prior authorization. Issuers may still challenge some transactions, but the MIT setup sharply reduces unnecessary requires_action outcomes on recurring charges compared with renewals that were never properly authorized for off-session use.
Why do merchants care about MIT when debugging failed renewals?
Many recurring payment failures that look random are really setup failures from the initial subscription flow. If the original payment method was not prepared for off-session use, future renewals can repeatedly hit authentication_required or requires_action because the issuer sees them as untrusted off-session charges.
Understanding MIT helps merchants separate one-time payment issues from structural billing issues. The fix is often not another retry; it is updating the subscription signup flow so the original SetupIntent correctly captures off-session consent and reduces future SCA friction.
Frequently asked questions
Does the MIT exemption guarantee that every subscription renewal avoids 3DS?
No. MIT treatment reduces the chance of a new challenge, but issuers can still request authentication for risk, geography, or card-specific reasons. The point of the exemption is not certainty; it is materially lowering the rate of off-session renewals that get blocked by avoidable SCA or 3DS prompts.
What setup mistake usually prevents MIT from working?
The common mistake is failing to authenticate and store the payment method for future off-session use during signup. In Stripe terms, that usually means a missing or incorrect SetupIntent or initial payment flow. Without that setup, future subscription renewals are more likely to trigger requires_action or authentication-required failures.
Related guides
Detect subscription failures automatically
Free cross-stack scan. Find revenue leaks in 60 seconds.
Run Free Scan →