adyen 3DS2 exemption "trustedBeneficiary" rejected by the issuer

TL;DR

trustedBeneficiary only works if the shopper added you to their trusted list during a previous SCA. If they did not, the issuer rejects the exemption and you must run full SCA. Request the exemption only for returning shoppers you have seen complete SCA before, and always handle the rejection by falling back to challenge.

trustedBeneficiary exemption rejected issuer

Use this when

• A 3DS2 trustedBeneficiary exemption is rejected by the issuer.
• You are requesting the exemption for first-time shoppers.
• Your exemption logic needs a fallback path.

Not for this skill when

• The exemption is lowValue or TRA. Those do not need shopper whitelisting.
• SCA is failing after the challenge. That is an authentication problem.

Steps

1. ('Check whether the shopper previously completed SCA with you and whitelisted the merchant. Verify: you have a record of a prior successful SCA.', 'Only request trustedBeneficiary for shoppers with that history. Verify: first-time shoppers go straight to SCA.', 'Handle the rejection gracefully: on exemption refusal, run the 3DS2 challenge flow. Verify: the shopper sees the challenge, not an error.', 'After a successful challenge, the issuer may offer whitelisting. Verify: your flow surfaces the option where supported.', 'Track exemption acceptance per shopper cohort. Verify: the data shows which shoppers actually whitelist.')

Variant phrasings

adyen trustedBeneficiary rejected

Short search.

trusted beneficiary exemption issuer declined

Reordered search.

adyen 3ds2 exemption fallback challenge

Fallback search.

Compatibility: Adyen Checkout API 3D Secure 2 with SCA exemptions, PSD2 regions.

Why it happens

Trusted beneficiary is the one exemption the shopper controls: during SCA the issuer can ask "trust this merchant?" and only then honor future exemption requests. The issuer rejects the exemption for anyone who never opted in, because skipping authentication for a stranger merchant would defeat SCA. Requesting it blindly for every shopper is why the rejection rate looks broken.

Edge cases / pitfalls

• Never treat an exemption rejection as a payment failure. It is a routing signal: run SCA.
• Whitelisting is per issuer and per shopper. One shopper whitelisting you does not cover others.
• Some issuers do not support whitelisting at all. Your fallback must be solid.
• Requesting exemptions for ineligible shoppers adds latency for zero benefit. Gate it on history.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_uYrmUHmlMt3hBpJKJgR1ww