Identify payments that fall below the low-value SCA exemption threshold defined in PSD2 RTS (check current regulatory guidance for the exact amount in EUR, as limits are periodically reviewed).
Signal the exemption preference to Stripe by setting the appropriate parameter in 'payment_method_options.card' when creating the PaymentIntent.
Be aware that issuers track a cumulative transaction count or cumulative value since the last SCA event per card; once the cumulative limit is reached, the issuer will require SCA regardless of individual transaction size.
If the issuer declines the exemption, catch the authentication_required decline code and re-invoke the payment with 3DS2 authentication.
Track the cardholder's exemption counter in your system (or accept that the issuer tracks it) so you can proactively trigger SCA before the issuer forces it.
For subscription contexts, apply the low-value exemption only on CIT (cardholder-initiated) legs; MIT renewals use the MIT framework, not the low-value SCA exemption.
Known gotchas
The cumulative counter resets only after a successful SCA event; if a customer makes many small purchases, they will eventually hit a mandatory SCA challenge mid-session at an unpredictable point.
Low-value exemptions cannot be stacked with TRA exemptions on the same transaction — choose one exemption strategy per transaction.
Liability for fraud on exempted transactions rests with the party (merchant or acquirer) that claimed the exemption — confirm this allocation with your PSP before relying on exemptions at scale.
Give your agent this knowledge — and 15,500+ 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?