## TL;DR
lowValue exemptions only apply under the scheme threshold (commonly 30 EUR or equivalent). Above that, the issuer will not honor the exemption, so the rejection is correct. Either let the transaction go through SCA or switch to a different exemption basis like transaction risk analysis if you qualify.

```text
exemption lowValue rejected amount over scheme limit
```

## Use this when
- An Adyen payment with a lowValue exemption request is rejected.
- You are applying lowValue exemptions to amounts above the threshold.
- You need to pick the right exemption type per transaction.

## Not for this skill when
- The exemption type is trustedBeneficiary or TRA. Those have different limits.
- SCA itself is failing. That is an authentication problem, not an exemption problem.

## Steps
1. ('Read the transaction amount and the scheme threshold for the card region. Verify: the amount is above the low-value limit.', 'Remove the lowValue exemption request for over-threshold transactions. Verify: the payment request no longer claims the exemption.', 'Decide per transaction: route through SCA, or request TRA exemption if your fraud rates qualify. Verify: the chosen path matches the amount band.', 'Add amount-band logic to your exemption code: lowValue only under the threshold. Verify: no over-threshold request carries the flag.', 'Monitor exemption acceptance rates by type. Verify: rejections drop after the fix.')

## Variant phrasings
### adyen lowValue exemption rejected
Short search.

### sca exemption amount too high adyen
Symptom search.

### adyen exemption scheme limit low value
Limit search.


Compatibility: Adyen Checkout API with SCA exemptions, PSD2 regions.

## Why it happens
PSD2 lets issuers skip strong authentication for low-value transactions, but the schemes cap what counts as low value. The exemption is a request, not a right: the issuer checks the amount against the scheme limit and rejects exemptions that exceed it. Requesting lowValue above the threshold is asking the issuer to break scheme rules, so the rejection is the correct behavior, not a bug.

## Edge cases / pitfalls
- Thresholds differ by region and scheme. Do not hardcode one global number.
- Cumulative low-value limits also exist: several small transactions can exhaust the allowance.
- TRA exemption needs qualifying fraud rates. Do not claim it without the numbers.
- Log exemption requests and outcomes per transaction. Exemption strategy is tuned on that data.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_STTRDl-iXCX1_CtCbmEYtw