Determine eligibility: TRA exemption applies when the PSP's fraud rate for the relevant card range is below the thresholds defined in PSD2 RTS (0.13% for transactions up to €100, 0.06% up to €250, 0.01% up to €500); low-value exemption applies to transactions below €30 with a cumulative cap of 5 consecutive uses or €100 total
Request the exemption by setting the appropriate payment_method_options parameter in your PaymentIntent creation call; the specific parameter name varies by integration — consult your PSP's current documentation
Handle the case where the issuer overrides your exemption request and mandates a challenge; your PaymentIntent will move to a requires_action state requiring 3DS
Implement a fallback path that initiates 3DS authentication when an exemption is declined; never hard-block on exemption acceptance
Log exemption outcomes per transaction to track your fraud rate; exceeding PSD2 fraud thresholds removes your eligibility to claim TRA exemptions
Known gotchas
TRA exemptions can only be claimed by the PSP (acquirer), not by the merchant directly; your PSP must support and enable TRA on your account
Low-value exemptions reset after an SCA-authenticated transaction; the consecutive-use counter is tracked by the issuer, not by you — you cannot reliably know the current count
Recurring transactions after an initial SCA-authenticated setup fall under merchant-initiated transaction (MIT) rules, not SCA exemptions; conflating these leads to incorrect authentication requests
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?