On the initial customer-initiated transaction (CIT), set the stored-credential setup usage flag to indicate that the payment method is being saved for future use
Capture the network transaction ID returned in the authorization response and store it as the initial transaction reference (agreement ID)
For subsequent merchant-initiated transactions (MIT), include the stored credential indicator, the original network transaction ID, and the MIT subcategory (recurring, installment, or unscheduled card on file)
Set the off-session flag appropriately so that 3DS and authentication challenges are suppressed for MIT flows
Handle soft declines (authentication required) on MIT by surfacing a CIT re-authentication prompt to the cardholder rather than retrying blindly
Maintain an audit log mapping each MIT charge to its originating CIT network transaction ID for dispute and compliance purposes
Known gotchas
Using the wrong MIT subcategory (e.g., marking an unscheduled charge as recurring) violates network rules and can result in fines or increased dispute rates
The network transaction ID from the original CIT must be passed on every subsequent MIT; losing this reference forces a new CIT setup and breaks the stored-credential chain
Some issuers will soft-decline MIT transactions that lack a valid stored-credential reference even if they previously approved the initial CIT
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?