Identify transactions eligible for Transaction Risk Analysis (TRA) exemption: your acquirer's fraud rate must be below the relevant threshold for the transaction amount tier, and you must request the exemption explicitly
For low-value transactions below the relevant EUR threshold, request the low-value exemption in the authentication request and track cumulative usage against the per-cardholder limit
For merchant-initiated transactions, apply the MIT exemption by including the stored-credential reference from the original SCA-authenticated CIT; no new authentication is required
Set the exemption request indicator in the PaymentIntent or payment method options; Stripe will include it in the authentication request to the issuer ACS
Handle the case where the issuer overrides the exemption request and demands a challenge; gracefully step up to 3DS challenge flow without failing the transaction
Log which exemption was applied and its outcome for regulatory record-keeping purposes
Known gotchas
Exemptions are requests, not guarantees; the issuer always has final say and may require SCA even when an exemption is requested, especially for high-risk transactions
Low-value exemptions have a per-card cumulative limit (a transaction count and a total amount limit); exceeding these limits means subsequent low-value transactions will require SCA
TRA exemptions require your acquirer to have achieved and maintained the qualifying fraud rate; if your acquirer's rate rises above the threshold, all TRA exemption requests will be rejected without warning
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?