You can test your transaction optimisation integration either by:
paymentMethod.cardBin field set to a special test value.customer.email field set to a special test value.These requests will always produce the same corresponding recommendation. You can then ensure your system handles the response accordingly.
The test card BINs and email addresses are shown in the table below:
| Field Name | Field Value | Recommendation | Example Response |
|---|---|---|---|
| Card BIN | "000001" |
Authenticate with no SCA exemption |
"action": "AUTHENTICATE" |
"qa-force-txopt-authenticate@ravelin.com" |
|||
| Card BIN | "000002" |
Authorise with no SCA exemption |
"action": "AUTHORISE" |
"qa-force-txopt-authorise@ravelin.com" |
|||
| Card BIN | "000005" |
Authenticate with Transaction Risk Analysis exemption |
"action": "AUTHENTICATE""exemption": "TRANSACTION_RISK_ANALYSIS" |
"qa-force-txopt-authenticate-tra@ravelin.com" |
|||
| Card BIN | "000006" |
Authorise with Transaction Risk Analysis exemption |
"action": "AUTHORISE""exemption": "TRANSACTION_RISK_ANALYSIS" |
"qa-force-txopt-authorise-tra@ravelin.com" |
|||
| Card BIN | "000007" |
Authorise with Low Value exemption |
"action": "AUTHORISE""exemption": "LOW_VALUE" |
"qa-force-txopt-authorise-lowvalue@ravelin.com" |
|||
Learn how to correctly handle transaction optimisation errors
Was this page helpful?