What is Transaction Risk Analysis exemption?
Also: TRA
PSD2 exemption from SCA for low-fraud acquirers on transactions under EUR 500, calibrated to portfolio fraud rates measured quarterly.
The Transaction Risk Analysis (TRA) exemption is a provision within PSD2 that allows an acquiring bank to exempt a transaction from Strong Customer Authentication (SCA) based on the acquirer's real-time fraud analysis and a low cumulative fraud rate across its entire portfolio of card transactions for a given card scheme.
This exemption applies to transactions with values up to EUR 500, with the specific threshold determined by the acquirer's fraud rate, which is measured quarterly and reported to its national competent authority.
To request TRA, the acquirer sets the exemption indicator in the authorisation message sent to the issuer, typically by populating field 20 in an ISO 8583 message with a specific exemption reason code.
For a merchant, a successful TRA exemption means the cardholder is not presented with an SCA challenge, leading to a smoother checkout experience and potentially higher conversion rates.
The merchant indirectly benefits from their acquirer maintaining a low fraud rate; however, they have no direct control over the acquirer's portfolio-wide fraud performance or the decision to apply TRA.
A common misunderstanding arises when merchants assume TRA is applied automatically or universally for all low-value transactions, overlooking that the issuer ultimately retains the right to override the TRA exemption request and still decline the transaction or demand SCA,
which they communicate via a specific response code in the authorisation.
Worked example
A merchant reviews a €500 transaction where Transaction Risk Analysis exemption is the deciding factor. The merchant checks geography, payment type, customer status, and exemption criteria before deciding which compliance treatment applies.
The operational cost is modelled at non-compliance exposure that can exceed the processing margin on the sale, and the relevant action must complete at Checkout or onboarding.
Step 1 is to capture the original request data, including amount, currency, issuer country, MID, and response or status code. Step 2 is to apply the merchant's rule set, for example whether to retry, challenge, refund, release goods, or hold for review.
Step 3 is to reconcile the result against acquirer reporting so finance can see the cash impact. If the rule improves the outcome by even 50 basis points on 2,000 similar monthly transactions, the merchant protects roughly 10 extra orders from avoidable failure or loss.
Scheme notes
This is not wholly scheme-specific, because regulatory obligations come from legislation, regulators, and local payment-system rules rather than Visa or Mastercard alone. Scheme rules still matter operationally because they define message fields, liability allocation, evidence standards, and monitoring consequences.
UK and EEA treatment can diverge after Brexit, and domestic schemes or bank-transfer rails may apply separate rulebooks. Merchants should treat scheme compliance and legal compliance as overlapping controls, not substitutes.
Why it matters for merchants
Commercially, this affects compliance cost, payment acceptance, refund and dispute obligations, and the risk of regulatory or scheme enforcement.
For a merchant processing £500,000 per month, a 25 basis point movement is worth £1,250 before secondary effects such as disputes, reserves, support tickets, or failed delivery costs.
The impact is larger in high-risk, subscription, travel, digital-goods, and cross-border models because issuer decisions and scheme monitoring can compound quickly.
Cardflo can help by combining acquiring access, MID routing, orchestration rules, KYB review, and chargeback tooling where relevant, so the merchant is not dependent on one processor interpretation or one fixed transaction path.
Frequently asked
Which data should a merchant store for Transaction Risk Analysis exemption?
Store the transaction ID, MID, acquirer, amount, currency, issuer country, card scheme, response or status code, timestamp, and any 3DS, exemption, refund, or dispute reference. For card transactions, keep authorisation and Clearing identifiers because settlement or chargeback questions may arrive 30 to 120 days later.
For regulated flows, keep customer consent and evidence records for at least the period required by local law or scheme rules. Good records reduce investigation time from hours to minutes when acquirer reporting does not match the order system.
How often should Transaction Risk Analysis exemption be reviewed?
High-volume merchants should review exception rates weekly and trend the main metric monthly by scheme, acquirer, issuer country, MCC, and payment method. A movement of 20 to 50 basis points can be material if the merchant processes thousands of orders.
Finance should reconcile the cash impact at settlement level, while risk or payment operations should analyse the root cause. Reviewing only blended totals hides problems that appear on a single BIN range, region, or MID.
What threshold usually triggers action on Transaction Risk Analysis exemption?
The threshold depends on the category, but merchants should investigate any sudden change above 10% relative movement or 25 basis points absolute movement. For disputes and fraud, scheme thresholds such as 0.9% under Visa monitoring or 1.5% under Mastercard ECM can create immediate escalation risk.
For settlement or pricing items, even 5 to 15 basis points can justify routing or contract review. The key is to set thresholds before month-end, not after a processor invoice or scheme notice arrives.
Can Transaction Risk Analysis exemption differ between acquirers?
Yes. Acquirers can map response codes differently, apply different risk rules, support different data fields, and settle on different cycles.
One acquirer may return a generic decline while another exposes issuer advice that allows a safe retry. Fee treatment can also vary by contract, especially for cross-border, FX, premium cards, and alternative payment methods.
This is why merchants using orchestration should compare performance by acquirer and scheme rather than relying on a single blended approval or cost figure.
What is the first remediation step when Transaction Risk Analysis exemption creates losses?
Start with a 30-day sample and split it by scheme, issuer country, card product, payment method, MID, and response or dispute code. Quantify the value at risk in cash terms, not just percentage points.
Then decide whether the fix is operational, such as better evidence or customer communication, technical, such as richer data or 3DS indicators, or commercial, such as a different acquirer route.
Recheck the same metric after one full settlement or dispute cycle to confirm the change worked.
See how Transaction Risk Analysis exemption plays out in practice
Industries and regions where this term drives real acquiring, routing, or dispute decisions.
Related terms
PSD2 requirement that customer-initiated electronic payments in the EEA and UK be authenticated with two of: knowledge, possession, inherence.
The EU's Payment Services Directive 2, which mandates SCA, opens banking APIs, and reshapes payment liability.
PSD2 SCA exemption for transactions under EUR 30, capped at five consecutive or EUR 100 cumulative unauthenticated transactions per card.
Related guides.
Ready to improve your payments setup?
Tell us about your business. We'll match you with the right acquiring partners and the right route, typically inside a week.