Last Updated: 30 September 2024 | Change Log
Test your Exemptions integration on the Try environment using the magic values provided below. Send requests and see simulated responses.
You can test how the issuer responds to the exemption applied in the payment using these Access Payments test values.
Use different cardholder names to alter the exemption outcome.
Use the cardholder test names below when creating the tokens. When creating tokens containing test/dummy card numbers you must delete the token before creating another with the same PAN. You are prevented from creating another token using the same PAN. As an alternative you can also change the namespace used as part of the token creation.
| Magic value | Description | Outcome | Type | Placement |
|---|---|---|---|---|
ex-exemption-lowRisk-authorization | Apply a low risk exemption to the payment | exemption | lowRisk | authorization |
ex-exemption-lowValue-authorization | Apply a low value exemption to the payment | exemption | lowValue | authorization |
ex-exemption-lowRisk-authentication | Apply a low risk exemption to the authentication | exemption | lowRisk | authentication |
ex-noExemption | No exemption provided, proceed to 3DS or directly to payment | noExemption | N/A | N/A |
You can also use the exemption object within the request body to test your integration. The SCA Exemptions service returns a placement and type that matches the values provided in the request. In Try, optimized will always return the values in the below table:
Requested placement | Response |
|---|---|
authorization | authorization |
authentication | authentication |
optimized | authorization |
Requested type | Response |
|---|---|
lowRisk | lowRisk |
lowValue | lowValue |
optimized | lowRisk |
Providing both a cardholder name magic value and the exemption object results in the cardholder name magic value taking priority. The contents of the exemption object are applied in the assessment request.