During the initial cardholder-initiated transaction (CIT), collect consent for future merchant-initiated charges and store the network transaction ID returned in the authorization response.
Store the stored-credential indicator and the original network transaction ID in your payment method record alongside the tokenized card.
For each subsequent MIT, include the stored-credential usage type (recurring, installment, or unscheduled), the original network transaction ID from the CIT, and the MIT indicator in your authorization request.
Set the initiation type field to merchant-initiated and the previous transaction reference field to the network transaction ID from the most recent successful authorization in the chain.
Handle declines specific to MIT flows such as 'R0' or 'R1' stop-payment requests, which indicate the cardholder has revoked authorization; cease retries and notify the cardholder.
Keep a complete audit log of the CIT consent event and each subsequent MIT attempt with timestamps for chargeback defense.
Known gotchas
Using MIT indicators without a valid prior CIT consent event is a violation of network rules and increases chargeback liability under reason code categories for unauthorized transactions.
The network transaction ID chain must be maintained correctly; breaking the chain (e.g., by switching PSPs without migrating the transaction reference) can cause MITs to fail or downgrade.
Some issuers enforce stop-payment flags aggressively; receiving an R0/R1 decline means you must not retry the charge, even if the cardholder later claims it was a mistake.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp