Credentials
To configure the connection, you will need to set the following credentials.| Credential | Description |
|---|---|
| API Key | This is not validated and can be set to any string |
Decision mapping
In order to test various anti-fraud decisions you must create a buyer with a specific email address (see table below). If you do not pass a buyer with email address the decision will beskipped.
| Buyer email | Decision | Description |
|---|---|---|
[email protected] | accept | Simulates a low risk transaction |
[email protected] | reject | Simulates a high risk transaction |
[email protected] | review | Simulates a transaction which needs manual review |
[email protected] | error | Simulates a bad request |
[email protected] | exception | Simulates a server timeout/bad response |
Errors
To simulate a network error, i.e. unable to connect to the anti-fraud provider you can use[email protected]. This will result in the decision being skipped and create
an anti-fraud-decision-error transaction event.
Webhooks
In order to test thereview status you can manually send a POST request to the
anti-fraud service webhook URL. You can find this value from our dashboard or via
the API when fetching the anti-fraud service.
POST body for the webhook URL must contain the UUID of the transaction and
a decision of ACCEPT or REJECT: