This page allows you view detailed configuration information for the given Site Reference.
Required user roles
Developer 2, Site admin, Site user, Site user 2
How to access
Select your site from the “Sites” page and click the “Site settings” icon.
"Site details" section
The fields under this header relate to your site’s basic configuration.
| Name of field | Description |
| Site reference | Unique site identifier (e.g. “site12346”) |
| Live status | When processing requests, you can process to our sandbox for testing purposes. “Real” transactions can only occur when processing requests using a live site reference. This distinction is shown in the live status:
|
| Site status | Requests can only be processed using a site reference if it has been enabled.
|
| Merchant name | The name of your business / organisation. |
"Site settings" section
| Name of field | Description |
| Auth method | The authmethod value assigned to all transactions (defaults to “FINAL”), unless overridden manually. |
"Fraud" section
The fields under this header relate to the configuration of our internal fraud checks on this site. You can request changes by contacting our Support Team.
| Name of field | Description |
| Run fraud | Indicates if fraud checks are enabled for this site. |
| Confidence threshold | When fraud checks are performed on your site, transactions will be suspended if the final fraud rating assigned to them meets the confidence threshold. |
| Excess threshold | If there are multiple transactions in a short period of time with the same payment details, this will increment the fraud rating assigned to future transactions. |
"Duplicate check" section
The fields under this header relate to the configuration of our internal Duplicate checks on this site. You can request changes by contacting our Support Team.
| Name of field | Description |
| Duplicate check | Indicates if duplicate checks are enabled for this site. |
| Duplicate velocity | If checks are enabled, transactions will be assumed as duplicates if identical transactions are processed within the timeframe specified here. This defaults to 900 seconds (15 minutes), if enabled. |
