Set up merchant-initiated transactions (MIT) with stored-credential framework indicators for subscription renewals

In-depth guide

Steps

1. On the initial cardholder-present transaction (CIT), include the stored credential usage indicator set to initial and the agreement type (recurring, installment, or unscheduled) in your payment request; capture the network transaction ID returned in the authorization response.
2. Store the network transaction ID alongside the customer's payment method token in your vault — this reference is mandatory for subsequent MIT authorizations.
3. For each subsequent MIT (off-session, no cardholder present), include the stored credential usage indicator set to subsequent, reference the original network transaction ID, and specify the same agreement type used at enrollment.
4. Set the off_session flag and confirm: true in Stripe's PaymentIntent or equivalent fields in your processor's API to signal that the cardholder is not present for this transaction.
5. Handle soft declines (e.g., authentication required): for MITs, issuers should not request 3DS; if you receive an authentication_required decline, review whether the initial CIT included proper SCA and stored credential framing.
6. Retain the network transaction ID chain for every renewed MIT — some processors require the most recent successful MIT network ID, not the original enrollment ID.