Low-value transaction
What is a low-value transaction?
Low-value transaction is a payment that falls below a set monetary threshold, which lets it qualify for an exemption from at checkout. Under , the threshold for remote electronic payments in the EEA is EUR 30, defined in Article 16 of the SCA regulatory technical standards.
The exemption exists so small, routine purchases don't push a cardholder through a full authentication challenge. A EUR 4 subscription renewal or a EUR 12 in-app purchase carries limited fraud exposure, and a 3-D Secure step on every one of them costs more in abandoned checkouts than it recovers in blocked fraud. The EUR 30 figure covers remote payments in the EEA. at a physical terminal fall under a separate rule, Article 11 of the same standards, with a higher EUR 50 per-transaction limit.
Key facts
- Threshold: EUR 30 per remote electronic payment in the EEA (SCA-RTS Article 16)
- Cumulative amount counter: EUR 100 of exempted transactions since the last SCA
- Transaction count counter: five consecutive exempted transactions since the last SCA
- Counter choice: the applies either the amount counter or the count counter, not both
- Scope: remote electronic payments where both the payer's and the payee's payment providers are located in the EEA
- Decided by: the issuer, based on the exemption flag the merchant sends in the authentication request
- Contactless equivalent: EUR 50 per transaction, EUR 150 cumulative or five consecutive transactions (Article 11)
- Also known as: low-value payment exemption, LVP exemption
How it works
- Merchant flags eligibility. At checkout the merchant or its compares the amount against the EUR 30 limit and, if it qualifies, sends the transaction into 3-D Secure with the low-value exemption flag set in the authentication request.
- Issuer checks the running counters. The issuer looks up how much the cardholder has spent on exempted transactions since the last successful SCA, or how many such transactions there have been, depending on which counter it maintains.
- Issuer approves or challenges. If the amount is under EUR 30 and the counter still has room, the issuer clears the transaction frictionlessly. If either limit is breached, it returns a challenge instead and the cardholder authenticates.
- Counters reset on SCA. Once the cardholder completes an authentication challenge, the cumulative amount and the transaction count both reset to zero, and the next small payment can be exempted again.
- Authorization proceeds. After authentication or its exemption, the transaction moves to , where the issuer makes a separate approve-or-decline decision on funds and risk.
Why it matters
Authentication friction is where card-not-present conversion leaks. Every 3-D Secure challenge adds a redirect, a one-time code, and a step the cardholder can abandon, and on a EUR 9 renewal that step is most of the effort of buying. The low-value exemption removes it from the transactions where it costs the most relative to their value.
- Subscription and low-ticket digital businesses gain the most. Recurring charges under EUR 30 are the exact shape the exemption was written for, so a merchant with a base of small renewals can keep the majority of them out of a challenge flow.
- The counters make the benefit uneven across a card base. A cardholder who makes several small purchases in a row hits the EUR 100 or five-transaction limit and gets challenged, so the exemption can't be treated as a permanent state for any given card.
- It removes a dependency on fraud-rate-gated exemptions. The is only available while the payment provider's fraud rate stays under a regulated ceiling. The low-value flag carries no such ceiling, so it stays available even when a TRA allowance is withdrawn.
Common issues
- The issuer ignores the flag. The exemption is a request, not an instruction. An issuer that sees elevated risk on the card or the merchant will challenge a EUR 5 transaction anyway, and the merchant has no way to force frictionless processing.
- No liability shift on exempted transactions. A payment authenticated through 3-D Secure moves fraud liability to the issuer. An exempted payment skips authentication, so that liability stays with the merchant.
- The counters are invisible to the merchant. Only the issuer knows how close a card sits to the EUR 100 or five-transaction limit, so an identical EUR 12 payment can clear frictionlessly for one cardholder and get challenged for the next.
- Soft declines after a skipped challenge. When an issuer wants SCA on a transaction that arrived without it, it returns a signalling that authentication is required, and the merchant re-submits the payment through a full 3-D Secure flow.
- Scope confusion outside the EEA. The EUR 30 threshold is an EEA rule tied to PSD2. Issuers in other markets set their own thresholds for skipping step-up authentication, so a merchant selling globally can't assume the same limit applies everywhere.
