The following documentation explains how to manually submit an AUTH request using our Webservices API.
If you are already processing e-commerce payments using our JavaScript Library (using 3-D Secure v2), you no longer need to manually perform the AUTH request described herein (as the JavaScript Library will automatically perform the authorisation).
Requirements

The following content assumes you have obtained the necessary PCI certification to process and submit sensitive cardholder data in the request to our Webservices API.
If you are unsure, please contact our Support Team for assistance.

All businesses within the EEA (European Economic Area) are mandated to use 3-D Secure when processing e-commerce transactions, as part of the PSD2 mandate.
To process an e-commerce transaction that is authenticated with 3-D Secure, you will need to utilise our JavaScript Library instead of the solution described below. Click here to get started.
The following content should only be utilised by merchants processing Mail or Telephone Order (MOTO) payments, Merchant Initiated Transactions (MIT), or other workflows that are exempt from the PSD2 mandate.

ECOM (e-Commerce) Maestro transactions require the implementation of 3-D Secure in order to be processed successfully.
To perform 3-D Secure, you will need to utilise our JavaScript Library. Click here to get started.

In order to reduce fraud, Visa has mandated that all UK-based merchants with a
Merchant Category Code (MCC) of 6012 are required to send additional fields in AUTH and ACCOUNTCHECK requests.
Failure to submit these fields may prevent the transaction from being processed successfully, with a “60025” errorcode being returned in the response.
Click here for further information.
AUTH request
Example
To successfully process an AUTH request, you must follow the specification below:
#!/usr/bin/python
import securetrading
stconfig = securetrading.Config()
stconfig.username = "[email protected]"
stconfig.password = "Password1^"
st = securetrading.Api(stconfig)
auth = {
"sitereference": "test_site12345",
"requesttypedescriptions": ["AUTH"],
"accounttypedescription": "ECOM",
"currencyiso3a": "GBP",
"baseamount": "1050",
"orderreference": "My_Order_123",
"pan": "4111111111111111",
"expirydate": "12/2020",
"securitycode": "123"
}
strequest = securetrading.Request()
strequest.update(auth)
stresponse = st.process(strequest) #stresponse contains the transaction response
<?php
if (!($autoload = realpath(__DIR__ . '/../../../autoload.php')) && !($autoload = realpath(__DIR__ . '/../vendor/autoload.php'))) {
throw new Exception('Composer autoloader file could not be found.');
}
require_once($autoload);
$configData = array(
'username' => '[email protected]',
'password' => 'Password1^',
);
$requestData = array(
'sitereference' => 'test_site12345',
'requesttypedescriptions' => array('AUTH'),
'accounttypedescription' => 'ECOM',
'currencyiso3a' => 'GBP',
'baseamount' => '1050',
'orderreference' => 'My_Order_123',
'pan' => '4111111111111111',
'expirydate' => '12/2020',
'securitycode' => '123'
);
$api = \Securetrading\api($configData);
$response = $api->process($requestData);
var_dump($response->toArray());
?>
curl --user [email protected]:Password1^ <DOMAIN>/json/ -H "Content-type: application/json" -H "Accept: application/json" -X POST -d '{
"alias":"[email protected]",
"version": "1.00",
"request": [{
"currencyiso3a": "GBP",
"requesttypedescriptions": ["AUTH"],
"sitereference": "test_site12345",
"baseamount": "1050",
"orderreference": "My_Order_123",
"accounttypedescription": "ECOM",
"pan": "4111111111111111",
"expirydate": "12/2020",
"securitycode": "123"
}]}'
{"alias":"[email protected]","version":"1.00","request":[{"currencyiso3a":"GBP","requesttypedescriptions":["AUTH"],"sitereference":"test_site12345","baseamount":"1050","orderreference":"My_Order_123","accounttypedescription":"ECOM","pan":"4111111111111111","expirydate":"12\/2020","securitycode":"123"}]}
<requestblock version="3.67">
<alias>[email protected]</alias>
<request type="AUTH">
<merchant>
<orderreference>My_Order_123</orderreference>
</merchant>
<billing>
<payment>
<expirydate>12/2020</expirydate>
<pan>4111111111111111</pan>
<securitycode>123</securitycode>
</payment>
<amount currencycode="GBP">1050</amount>
</billing>
<operation>
<sitereference>test_site12345</sitereference>
<accounttypedescription>ECOM</accounttypedescription>
</operation>
</request>
</requestblock>
Replace <DOMAIN> with a supported domain. Click here for a full list.
Field specification
Operation
The following fields relate to the type of request submitted:
|
Field |
Format |
Description |
 |
accounttypedescription
XPath: /operation/accounttypedescription |
Alpha (20) |
The type of account to be used:
- “ECOM” – E-commerce
- “MOTO” – Mail or Telephone Order
- “RECUR” – Recurring transactions
|
 |
authmethod
XPath: /operation/authmethod |
Alpha (11) |
Auth methods are used to specify how a transaction is to be processed by the card issuer. Each authmethod has a different set of requirements.
Click here for further information. |
|
credentialsonfile
XPath: /operation/credentialsonfile |
Numeric (1) |
The allowed values for this field are 0, 1 and 2.
- “0” – Not eligible for CoF, or no intention of re-using credentials at a later time.
- “1” – Transaction credentials flagged as available for future use.
- “2” – Payment using previously-stored credentials.
|
|
initiationreason
XPath: /operation/initiationreason |
Char (1) |
Allows you to assign a reason for a Merchant Initiated Transaction (MIT).
Do not submit when processing a Customer Initiated Transaction (CIT).The allowed values for this field are “A”, “C”, “D”, “S” and “X”.
- “A” – Reauthorisation
- “C” – Unscheduled payment
- “D” – Delayed Charges
- “S” – Resubmission
- “X” – No-show (for a hotel booking)
Click here for further information on the different initiationreason values.
Note: You must ensure the initiationreason submitted in the request correctly represents the reason for the new payment. Visa may introduce new values to this list in the future. Please refer to Visa’s own documentation for further information. |
 |
parenttransactionreference
XPath: /operation/parenttransactionreference |
Alphanumeric
& hyphens (25) |
Allows you to specify the transactionreference of a previous request. Key details are inherited from this request. |
 |
requesttypedescriptions
XPath: /@type |
Alpha (20) |
You must submit “AUTH”, as shown in the request example. |
 |
sitereference
XPath: /operation/sitereference |
Alphanumeric
& underscore (50) |
Identifies your site on the Trust Payments system.
If you do not know your site reference, please contact our Support Team. |
Payment
The following fields contain the customer’s payment details:
|
Field |
Format |
Description |
 |
baseamount
XPath: /billing/amount |
Numeric (13) |
The amount of the transaction in base units, with no commas or decimal points, so £10 is submitted as 1000. This value must be greater than zero. (Max length may vary depending on your acquiring bank – Contact your bank for further info) |
 |
currencyiso3a
XPath: /billing/amount/@currencycode |
Alpha (3) |
The currency of the transaction. Click here for a full list of available currencies.
If the currency is submitted in a child request, it must be the same value as the parent transaction. |
 |
expirydate
XPath: /billing/payment/expirydate |
Date MM/YYYY |
The expiry date printed on the card. |
 |
pan
XPath: /billing/payment/pan |
Numeric (12-19) |
This is the long number printed on the front of the customer’s card. |
 |
paymenttypedescription
XPath: /billing/payment/@type |
Alpha (20) |
Payment method (e.g. “VISA” or “MASTERCARD”). |
 |
securitycode
XPath: /billing/payment/securitycode |
Numeric (3-4) |
This is the three digit security code printed on the back of the card.
(For AMEX cards, this is a 4 digit code found on the front of the card)
This field is not strictly required by Trust Payments, but it is highly recommended for the processing of security code checks.
Additionally, some banks may decline the payment if the security code is not present. |
Merchant
The following fields relate to your account configuration and allow you to configure custom unique references for your request:
|
Field |
Format |
Description |
 |
chargedescription
XPath: /merchant/chargedescription |
Alphanumeric including
symbols (25) |
This is a description of the payment that appears on the customer’s bank statement. Only supported by certain acquiring banks.
Specification of this field will depend on your acquiring bank. Click here for further information.
Valid characters:
- Uppercase/lowercase A-Z
- Numbers 0-9
- Spaces
- Punctuation: + – _ . @ ( )
|
 |
merchantemail
XPath: /merchant/email |
Email (255) |
The merchant’s email address. Maximum length of 255 (maximum of 64 characters before the ”@” symbol). |
 |
operatorname
XPath: /merchant/operatorname |
Alphanumeric (255) |
The value of this field contains the name of the user that processed the request. By default, this is the Web Services username included in the request. This can be overridden with a custom value by passing through this field in the request (optional). |
 |
orderreference
XPath: /merchant/orderreference |
Alphanumeric including
symbols (255) |
Your unique order reference that can be stored on the Trust Payments system.
Note: This can be updated at a later time (only if transaction is pending settlement). |
Billing
The following fields contain the customer’s billing details:
Customer and delivery
The following fields contain the customer’s delivery details:
Settlement
The following fields contain the Settlement details:
|
Field |
Format |
Description |
 |
settleduedate
XPath: /settlement/settleduedate |
Date YYYY-MM-DD |
You can submit this field in the request to specify the date you would like your transaction to settle. This must be within 7 days of the authorisation date. |
 |
settlestatus
XPath: /settlement/settlestatus |
Numeric (3) |
A numeric value used to define the settlement instruction. If you do not submit a value here, the settlestatus defaults to “0”.
Click here for a full list of settlestatus values. |
AUTH response
The following is an example of an AUTH response indicating the request was processed successfully.
{
u 'requestreference': u 'A0bxh87wt',
u 'version': u '1.00',
u 'response': [{
u 'transactionstartedtimestamp': u '2016-12-07 11:32:44',
u 'livestatus': u '0',
u 'issuer': u 'Test Issuer',
u 'splitfinalnumber': u '1',
u 'dccenabled': u '0',
u 'settleduedate': u '2016-12-07',
u 'errorcode': u '0',
u 'orderreference': u 'My_Order_123',
u 'tid': u '27882788',
u 'merchantnumber': u '00000000',
u 'merchantcountryiso2a': u 'GB',
u 'transactionreference': u '23-9-80001',
u 'merchantname': u 'Test Merchant',
u 'paymenttypedescription': u 'VISA',
u 'baseamount': u '1050',
u 'accounttypedescription': u 'ECOM',
u 'acquirerresponsecode': u '00',
u 'requesttypedescription': u 'AUTH',
u 'securityresponsesecuritycode': u '2',
u 'currencyiso3a': u 'GBP',
u 'authcode': u 'TEST36',
u 'errormessage': u 'Ok',
u 'operatorname': u '[email protected]',
u 'securityresponsepostcode': u '0',
u 'maskedpan': u '411111######1111',
u 'securityresponseaddress': u '0',
u 'issuercountryiso2a': u 'US',
u 'settlestatus': u '0'
}]
}
array(3) {
["requestreference"] => string(9) "A3579dkvx"
["version"] => string(4) "1.00"
["response"] => array(1) {
[0] => array(28) {
["transactionstartedtimestamp"] => string(19) "2016-12-09 09:52:19"
["livestatus"] => string(1) "0"
["issuer"] => string(26) "Test Issuer"
["splitfinalnumber"] => string(1) "1"
["dccenabled"] => string(1) "0"
["settleduedate"] => string(10) "2016-12-09"
["errorcode"] => string(1) "0"
["orderreference"] => string(12) "My_Order_123"
["tid"] => string(8) "27882788"
["merchantnumber"] => string(8) "00000000"
["securityresponsepostcode"] => string(1) "0"
["transactionreference"] => string(10) "72-9-80003"
["merchantname"] => string(13) "Test Merchant"
["paymenttypedescription"] => string(4) "VISA"
["baseamount"] => string(4) "1050"
["accounttypedescription"] => string(4) "ECOM"
["acquirerresponsecode"] => string(2) "00"
["requesttypedescription"] => string(4) "AUTH"
["securityresponsesecuritycode"] => string(1) "2"
["currencyiso3a"] => string(3) "GBP"
["authcode"] => string(6) "TEST31"
["errormessage"] => string(2) "Ok"
["operatorname"] => string(23) "[email protected]"
["merchantcountryiso2a"] => string(2) "GB"
["maskedpan"] => string(16) "411111######1111"
["securityresponseaddress"] => string(1) "0"
["issuercountryiso2a"] => string(2) "US"
["settlestatus"] => string(1) "0"
}
}
}
{"requestreference":"W23-fjgvn3d8","version":"1.00","response":[{"transactionstartedtimestamp":"2016-12-07 15:08:47","livestatus":"0","issuer":"Test Issuer","splitfinalnumber":"1","dccenabled":"0","settleduedate":"2016-12-07","errorcode":"0","baseamount":"1050","tid":"27882788","merchantnumber":"00000000","merchantcountryiso2a":"GB","transactionreference":"23-9-80006","merchantname":"Test Merchant","paymenttypedescription":"VISA","orderreference":"My_Order_123","accounttypedescription":"ECOM","acquirerresponsecode":"00","requesttypedescription":"AUTH","securityresponsesecuritycode":"2","currencyiso3a":"GBP","authcode":"TEST96","errormessage":"Ok","operatorname":"[email protected]","securityresponsepostcode":"0","maskedpan":"411111######1111","securityresponseaddress":"0","issuercountryiso2a":"US","settlestatus":"0"}],"secrand":"zO9"}
<responseblock version="3.67">
<requestreference>A3579dkvx</requestreference>
<response type="AUTH">
<merchant>
<merchantname>Test Merchant</merchantname>
<orderreference>MyOrder123</orderreference>
<tid>27882788</tid>
<merchantnumber>00000000</merchantnumber>
<merchantcountryiso2a>GB</merchantcountryiso2a>
<operatorname>[email protected]</operatorname>
</merchant>
<transactionreference>23-9-80006</transactionreference>
<security>
<postcode>2</postcode>
<securitycode>2</securitycode>
<address>2</address>
</security>
<billing>
<amount currencycode="GBP">1050</amount>
<payment type="VISA">
<issuer>Test Issuer</issuer>
<issuercountry>ZZ</issuercountry>
<pan>411111######1111</pan>
</payment>
<dcc enabled="0"/>
</billing>
<authcode>TEST96</authcode>
<timestamp>2012-10-08 12:46:02</timestamp>
<settlement>
<settleduedate>2012-10-08</settleduedate>
<settlestatus>0</settlestatus>
</settlement>
<live>0</live>
<error>
<message>Ok</message>
<code>0</code>
</error>
<acquirerresponsecode>00</acquirerresponsecode>
<operation>
<splitfinalnumber>1</splitfinalnumber>
<authmethod>PRE</authmethod>
<accounttypedescription>ECOM</accounttypedescription>
</operation>
</response>
<secrand>hYWFMkiiAZ0wKHFZ</secrand>
</responseblock>
When you receive an AUTH response, you must check the field values, to ensure the request was processed successfully.
Please refer to our “Best practices” for further information.
Field specification
Operation
Billing
Merchant
The following fields relate to your account configuration:
|
Field |
Format |
Description |
 |
chargedescription
XPath: /merchant/chargedescription |
Alphanumeric including
symbols (25) |
This is a description of the payment that appears on the customer’s bank statement.
Only supported by certain acquiring banks.
Specification of this field will depend on your acquiring bank. Click here for further information.
Valid characters:
- Uppercase/lowercase A-Z
- Numbers 0-9
- Spaces
- Punctuation: + – _ . @ ( )
|
 |
merchantnumber
XPath: /merchant/merchantnumber |
Alphanumeric (32) |
The merchant number that was used to process the transaction. Provided by the acquiring bank. |
 |
merchantcategorycode
XPath: /merchant/merchantcategorycode |
Alphanumeric (255) |
These are details associated with the account used to process the transaction.To amend these fields, please contact our Support Team.
|
merchantcity
XPath: /merchant/merchantcity |
Alphanumeric (127) |
merchantcountryiso2a
XPath: /merchant/merchantcountryiso2a |
Alpha (2) |
merchantname
XPath: /merchant/merchantname |
Alphanumeric (255) |
merchantstatecode
XPath: /merchant/merchantstatecode |
Alphanumeric (127) |
merchantzipcode
XPath: /merchant/merchantzipcode |
Alphanumeric (10) |
 |
operatorname
XPath: /merchant/operatorname |
Alphanumeric (255) |
The value of this field contains the name of the user that processed the request. |
 |
orderreference
XPath: /merchant/orderreference |
Alphanumeric including
symbols (255) |
Your unique order reference that can be stored on the Trust Payments system.
Note: This can be updated at a later time (only if transaction is pending settlement). |
 |
tid
XPath: /merchant/tid |
Alphanumeric (255) |
The terminal ID used to process the transaction. This is accredited to your merchant number when we setup your account in our systems. |
Settlement
The following fields contain the Settlement details:
|
Field |
Format |
Description |
 |
settleduedate
XPath: /settlement/settleduedate |
Date YYYY-MM-DD |
The date on which the transaction will be settled. |
 |
settlestatus
XPath: /settlement/settlestatus |
Numeric (3) |
A numeric value used to indicate the progress of settlement regarding this transaction.
Click here for a full list of settlestatus values. |
Transaction status
The following fields returned in the response indicate the outcome of the request:
In addition to the
response object, two additional fields are also returned in the response:
|
Field |
Format |
Description |
 |
requestreference |
Alphanumeric (25) |
This is an internal field generated by Trust Payments. It must not be validated. If problems are experienced with the request this field may be requested by Trust Payments support to aid in determining the cause. |
 |
secrand |
Alphanumeric (16) |
Random string of characters, returned in the response of non-API-based libraries developed by Trust Payments. |
Use the credentials provided on this page to test your solution.
When you sign up, you will be provided with a “live” account and a “test” account (the latter is prefixed with “test_”).
When testing, ensure requests submitted to Trust Payments reference your test sitereference.

It is important to thoroughly test your integration using your test sitereference before processing live payments.

Before you begin testing…
Please be aware of the following notes:
- Most fields submitted to our test system will be accepted. Any data breaching its defined specification will return an error message.
- Any test data that generates a successful response when submitted while a merchant is in test mode, will produce a declined response when a merchant is switched into live mode. In some cases, the test data may return an error response.
- Our test system attempts to simulate responses in a similar fashion to the live system. However, depending on your acquirer you may find some responses differ slightly from those given by the test system.
- In the interest of security, we recommend against using real payment details when using your test account.
- We recommend specifying the main amount “10.50” when testing. Other amounts can be used but may return unexpected responses.
- For those using Payment Pages, if you’re unsure where to start with your testing, you may find this resource helpful.
Test card details
The table below lists test card numbers and customer information that can be submitted to our test bank, along with the responses that should be expected in return.

Do not use these credentials when processing transactions on your live site reference.

While testing, all card types are supported, but when using your live account, you will receive an error if you do not have a valid merchant number for the payment type submitted.
- A baseamount of 70000 (£700.00) will always return a declined response from the test bank.
- A baseamount of 60010 (£600.10) will always return a bank system error from the test bank.
- Using baseamount 1050 (£10.50) will not generate an error.
3-D Secure v2
The following payment credentials can be used for testing 3-D Secure v2 (a form of SCA):
(3DSv2) Test Case 1: Successful Frictionless 3-D Secure Authentication & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001007 |
THREEDQUERY
Enrolled: Y
Status: Y
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001002 |
JCB |
3337000000000008 |
MASTERCARD |
5200000000001005 |
VISA (3-D Secure v2.1.0) |
4000000000001000 |
VISA (3-D Secure v2.2.0) |
4000000000002701 |
(3DSv2) Test Case 2: Failed Frictionless 3-D Secure Authentication & Failed Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001015 |
THREEDQUERY
Enrolled: Y
Status: N
AUTH
Error code: 60022 – Unauthenticated |
DINERS / DISCOVER |
6011000000001010 |
JCB |
3337000000000990 |
MASTERCARD |
5200000000001013 |
VISA (3-D Secure v2.1.0) |
4000000000001018 |
VISA (3-D Secure v2.2.0) |
4000000000002925 |
(3DSv2) Test Case 3: Attempts Stand-In Frictionless 3-D Secure Authentication & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001023 |
THREEDQUERY
Enrolled: Y
Status: A
AUTH
Error code: 0 -Ok |
DINERS / DISCOVER |
6011000000001028 |
JCB |
3337000000007045 |
MASTERCARD |
5200000000001021 |
VISA (3-D Secure v2.1.0) |
4000000000001026 |
VISA (3-D Secure v2.2.0) |
4000000000002719 |
(3DSv2) Test Case 4: Unavailable Frictionless 3-D Secure Authentication from the Issuer & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001031 |
THREEDQUERY
Enrolled: Y
Status: U
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001036 |
JCB |
3337000000000735 |
MASTERCARD |
5200000000001039 |
VISA (3-D Secure v2.1.0) |
4000000000001034 |
VISA (3-D Secure v2.2.0) |
4000000000002313 |
(3DSv2) Test Case 5: Rejected Frictionless 3-D Secure Authentication by the Issuer & Failed Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001049 |
THREEDQUERY
Enrolled: Y
Status: R
AUTH
Error code: 60022 – Unauthenticated |
DINERS / DISCOVER |
6011000000001044 |
JCB |
3337000000000321 |
MASTERCARD |
5200000000001047 |
VISA (3-D Secure v2.1.0) |
4000000000001042 |
VISA (3-D Secure v2.2.0) |
4000000000002537 |
(3DSv2) Test Case 6: 3-D Secure Authentication Not Available on Lookup & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001056 |
THREEDQUERY
Enrolled: U
Status: None
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001051 |
JCB |
3337000000006765 |
MASTERCARD |
5200000000001054 |
VISA (3-D Secure v2.1.0) |
4000000000001059 |
VISA (3-D Secure v2.2.0) |
4000000000002990 |
(3DSv2) Test Case 7: Error on Lookup & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001064 |
THREEDQUERY
Enrolled: U
Status: None
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001069 |
JCB |
3337000000000016 |
MASTERCARD |
5200000000001062 |
VISA (3-D Secure v2.1.0) |
4000000000001067 |
VISA (3-D Secure v2.2.0) |
4000000000002446 |
(3DSv2) Test Case 8: Timeout on cmpi_lookup Transaction & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001072 |
THREEDQUERY
Enrolled: U
Status: None
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001077 |
JCB |
3337000000000081 |
MASTERCARD |
5200000000001070 |
VISA (3-D Secure v2.1.0) |
4000000000001075 |
VISA (3-D Secure v2.2.0) |
4000000000002354 |
(3DSv2) Test Case 9: Successful Step Up 3-D Secure Authentication & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001098 |
THREEDQUERY
Enrolled: Y
Status: C
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001093 |
JCB |
3337000000200004 |
MASTERCARD |
5200000000001096 |
VISA (3-D Secure v2.1.0) |
4000000000001091 |
VISA (3-D Secure v2.2.0) |
4000000000002503 |
(3DSv2) Test Case 10: Failed Step Up 3-D Secure Authentication & No Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001106 |
THREEDQUERY
Enrolled: Y
Status: C
AUTH
Not performed |
DINERS / DISCOVER |
6011000000001101 |
JCB |
3337000000200087 |
MASTERCARD |
5200000000001104 |
VISA (3-D Secure v2.1.0) |
4000000000001109 |
VISA (3-D Secure v2.2.0) |
4000000000002370 |
(3DSv2) Test Case 11: Step Up 3-D Secure Authentication is Unavailable & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001114 |
THREEDQUERY
Enrolled: Y
Status: C
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001119 |
JCB |
3337000000200079 |
MASTERCARD |
5200000000001112 |
VISA (3-D Secure v2.1.0) |
4000000000001117 |
VISA (3-D Secure v2.2.0) |
4000000000002420 |
(3DSv2) Test Case 12: Error on 3-D Secure Authentication & No Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001122 |
THREEDQUERY
Enrolled: Y
Status: C
AUTH
Not performed |
DINERS / DISCOVER |
6011000000001127 |
JCB |
3337000000200046 |
MASTERCARD |
5200000000001120 |
VISA (3-D Secure v2.1.0) |
4000000000001125 |
VISA (3-D Secure v2.2.0) |
4000000000002644 |
(3DSv2) Test Case 13: Bypassed 3-D Secure Authentication & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000001080 |
THREEDQUERY
Enrolled: B
Status: None
AUTH
Error code: 0 – Ok |
DINERS / DISCOVER |
6011000000001085 |
JCB |
3337000000000537 |
MASTERCARD |
5200000000001088 |
VISA (3-D Secure v2.1.0) |
4000000000001083 |
VISA (3-D Secure v2.2.0) |
4000000000002560 |
3-D Secure v1
The following payment credentials can be used for testing 3-D Secure v1 (a form of SCA):
(3DSv1) Test Case 1: Successful 3-D Secure Authentication & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000003961 |
THREEDQUERY
Enrolled: Y
Status: None
AUTH
Error code: 0 – Ok |
DINERS |
3005000000006246 |
DISCOVER |
6011000000000004 |
JCB |
3520000000000922 |
MASTERCARD |
5200000000000007 |
VISA |
4000000000000002 |
(3DSv1) Test Case 2: Failed Signature & No Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000006022 |
THREEDQUERY
Enrolled: Y
Status: None
AUTH
Not performed |
DINERS |
3005000000004373 |
DISCOVER |
6011000000000012 |
JCB |
3520000000002811 |
MASTERCARD |
5200000000000015 |
VISA |
4000000000000010 |
(3DSv1) Test Case 3: Failed Authentication & No Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000000033 |
THREEDQUERY
Enrolled: Y
Status: None
AUTH
Not performed |
DINERS |
3005000000005925 |
DISCOVER |
6011000000000020 |
JCB |
3520000000009931 |
MASTERCARD |
5200000000000023 |
VISA |
4000000000000028 |
(3DSv1) Test Case 4: Attempts/Non-Participating & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000003391 |
THREEDQUERY
Enrolled: Y
Status: A
AUTH
Error code: 0 – Ok |
DINERS |
3005000000005271 |
DISCOVER |
6011000000000038 |
JCB |
3520000000004767 |
MASTERCARD |
5200000000000908 |
VISA |
4000000000000101 |
(3DSv1) Test Case 6: Not Enrolled & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000008135 |
THREEDQUERY
Enrolled: N
Status: None
AUTH
Error code: 0 – Ok |
DINERS |
3005000000007269 |
DISCOVER |
6011000000000053 |
JCB |
3520000000006903 |
MASTERCARD |
5200000000000056 |
VISA |
4000000000000051 |
(3DSv1) Test Case 7: Unavailable & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000007780 |
THREEDQUERY
Enrolled: U
Status: None
AUTH
Error code: 0 – Ok |
DINERS |
3005000000006030 |
DISCOVER |
6011000000000061 |
JCB |
3520000000002423 |
MASTERCARD |
5200000000000064 |
VISA |
4000000000000069 |
(3DSv1) Test Case 8: Merchant Not Active & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000008416 |
THREEDQUERY
Enrolled: U
Status: None
AUTH
Error code: 0 – Ok |
DINERS |
3005000000004837 |
DISCOVER |
6011000000000079 |
JCB |
3520000000006549 |
MASTERCARD |
5200000000000072 |
VISA |
4000000000000077 |
(3DSv1) Test Case 9: cmpi_lookup error & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000006337 |
THREEDQUERY
Enrolled: U
Status: None
AUTH
Error code: 0 – Ok |
DINERS |
3005000000009877 |
DISCOVER |
6011000000000087 |
JCB |
3520000000002175 |
MASTERCARD |
5200000000000080 |
VISA |
4000000000000085 |
(3DSv1) Test Case 10: cmpi_authenticate error & No Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000009299 |
THREEDQUERY
Enrolled: Y
Status: None
AUTH
Not performed |
DINERS |
3005000000005602 |
DISCOVER |
6011000000000095 |
JCB |
3520000000006861 |
MASTERCARD |
5200000000000098 |
VISA |
4000000000000093 |
(3DSv1) Test Case 11: Authentication Unavailable & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340000000000116 |
THREEDQUERY
Enrolled: Y
Status: None
AUTH
Error code: 0 – Ok |
DINERS |
3005000000007376 |
DISCOVER |
6011000000000103 |
JCB |
3520000000005780 |
MASTERCARD |
5200000000000031 |
VISA |
4000000000000036 |
(3DSv1) Test Case 12: Bypassed Authentication & Successful Authorisation
|
Card type |
PAN |
Handling the response |
AMEX |
340099000000001 |
THREEDQUERY
Enrolled: B
Status: None
AUTH
Error code: 0 – Ok |
DINERS |
3000990000000006 |
DISCOVER |
6011990000000006 |
JCB |
3500990000000001 |
MASTERCARD |
5200990000000009 |
VISA |
4000990000000004 |
3-D Secure status testing
To test for different 3-D Secure status values, follow the instructions displayed in the authentication prompt shown on the page (an example is shown below). In the textbox provided, you can enter different PIN values to test for different cases.

Displaying the test ACS page
For Payment Pages:
With 3-D Secure enabled on your site reference, process a payment using one of the card numbers listed above and your browser will display an authentication prompt with instructions.
For JavaScript Library implementations:
After your payment form has been updated to reference our JavaScript library, process a payment using one of the card numbers listed above and your browser will display an authentication prompt with instructions.
For Mobile SDK implementations:
After your Android or iOS app has been updated to utilise our Mobile SDK, process a payment using one of the card numbers listed above and your app will display an authentication prompt with instructions.
The authentication prompt will only be displayed for non-frictionless test card details.
Frictionless cards will bypass authentication. In this case, the payment will be processed immediately (without being prompted by the browser for information).
Follow the instructions displayed within the authentication prompt to complete the payment:


When the status is “N”, indicating the customer failed authentication, the errorcode “60022” will be returned.
Testing AVS and security code checks
If you haven’t already, please read our AVS and Security code documentation before testing:
Link to Payment Pages docs / Link to API docs
The following tables list test details that can be submitted to obtain different responses from the AVS and Security Code Checks. These details can be used with most major payment types.

Only the billing premise, billing postcode and security code field values dictate the outcome of the AVS and security code checks performed. As such, entering any details into the other address fields will not affect the outcome of these checks.
Premise
Billing premise |
Security response |
Security response caption |
No 789 |
2 |
Matched |
No 123 |
4 |
Not Matched |
No 333 |
1 |
Not Checked |
Leave blank |
0 |
Not Given |
Postcode / ZIP code
Billing postcode |
Security response |
Security response caption |
UK |
US |
TE45 6ST |
55555 |
2 |
Matched |
TE12 3ST |
12345 |
4 |
Not Matched |
TE33 3ST |
33333 |
1 |
Not Checked |
Leave blank |
Leave blank |
0 |
Not Given |
Security code
Security code |
AMEX security code |
Security response |
Security response
|
123 |
1234 |
2 |
Matched |
214 |
2144 |
4 |
Not Matched |
333 |
3333 |
1 |
Not Checked |
Leave blank |
Leave blank |
0 |
Not Given |
Testing non-card payment methods
Testing recurring payments
Testing for the acquirer advice code
When processing recurring payments, some acquirers may return an acquirer advice code in the response. The acquirer advice code is a numeric value used to indicate if further recurring payments can be processed for the given card.
Code |
Description |
Action |
0 |
N/A |
No action required |
1 |
New account information available (Mastercard only) |
Query customer for updated payment details |
2 |
Cannot approve at this time |
Try again later. If you are continuing to have difficulties, please contact your acquiring bank |
4 |
Do not try again |
Do not process further recurring transactions |
8 |
Payment blocked by card scheme |
Where to find the acquirer advice code
- This code is returned in your daily subscription email report.
- It’s viewable within MyST by selecting the additional field to be displayed on the transaction search page. It can also be viewed on the single transaction view.
- Additionally, for those who have processed a recurring AUTH transaction using the API, the code is returned in the acquireradvicecode field in the response.
How to test for different acquirer advice codes
You can test that your system responds appropriately to different acquirer advice codes by processing transactions with the following attributes:
Visa |
Acquirer advice code returned |
Card number |
Base amount |
0 |
4111111111111111 |
1050 |
2 |
4000000000000671 |
1002 |
4 |
4000000000000671 |
1004 |
8 |
4000000000000671 |
1008 |

Acquirer advice code ‘1’ can only be returned for recurring Mastercard transactions.
Mastercard |
Acquirer advice code returned |
Card number |
Base amount |
0 |
5100000000000511 |
1050 |
1 |
5100000000000271 |
1001 |
2 |
5100000000000271 |
1002 |
4 |
5100000000000271 |
1004 |
8 |
5100000000000271 |
1008 |
Testing Protect Plus
Please refer to the following resources when testing Protect Plus:
Testing DCC
Please refer to the following resources when testing DCC:

The following content assumes you have obtained the necessary PCI certification to process and submit sensitive cardholder data in the request to our Webservices API.
If you are unsure, please contact our Support Team for assistance.
If you would like to retrieve information on requests and transactions you have previously submitted, you can submit a TRANSACTIONQUERY request.
Process overview
Your system will need to submit a TRANSACTIONQUERY request to Trust Payments. Trust Payments will then return a response containing the requested information, if a matching request has been found.
For example, you can request information on all transactions processed on your Site Reference between 6pm and 9pm, or find out whether or not a transaction has been settled.
Filters
The TRANSACTIONQUERY request consists primarily of filters. Think of filters as search criteria; the response returned will contain information meeting the specified filters.
For example, a filter with orderreference “100100” would return details of all matching requests with that reference (if any exist and have been processed on your site reference).
And specifying a starttimestamp and endtimestamp will return details of all requests processed on your account between the specified times.

Multiple records can be returned in a single response
We recommend being as specific as reasonably possible in your request, by submitting as many filters as required, in order to avoid returning an excessive number of records in the response.
You can also submit multiple values for each given filter. e.g. You can submit a filter for transactionreference values “23-9-1” and “23-9-2”, and any requests matching these values will be returned in the response. (We include an example of this case below)
TRANSACTIONQUERY request
For the TRANSACTIONQUERY request to be processed successfully, you need to submit at least one valid filter.
Request example
#!/usr/bin/python
import securetrading
stconfig = securetrading.Config()
stconfig.username = "[email protected]"
stconfig.password = "Password1^"
st = securetrading.Api(stconfig)
query = {
"requesttypedescriptions": ["TRANSACTIONQUERY"],
"filter":{
"sitereference": [{"value":"test_site12345"}],
"currencyiso3a": [{"value":"GBP"}],
"transactionreference": [{"value":"23-9-1"},{"value":"23-9-2"}]
}
}
strequest = securetrading.Request()
strequest.update(query)
stresponse = st.process(strequest) #stresponse contains the transaction response
<?php
if (!($autoload = realpath(__DIR__ . '/../../../autoload.php')) && !($autoload = realpath(__DIR__ . '/../vendor/autoload.php'))) {
throw new Exception('Composer autoloader file could not be found.');
}
require_once($autoload);
$configData = array(
'username' => '[email protected]',
'password' => 'Password1^',
);
$requestData = array(
'requesttypedescriptions' => array('TRANSACTIONQUERY'),
'filter' => array(
'sitereference' => array(array('value' => 'test_site12345')),
'currencyiso3a' => array(array('value' => 'GBP')),
'transactionreference' => array(array('value' => '23-9-1'),array('value' => '23-9-2'))
)
);
$api = \Securetrading\api($configData);
$response = $api->process($requestData);
var_dump($response->toArray());
?>
curl --user [email protected]:Password1^ <DOMAIN>/json/ -H "Content-type: application/json" -H "Accept: application/json" -X POST -d '{
"alias": "[email protected]",
"version": "1.00",
"request": [{
"requesttypedescriptions": ["TRANSACTIONQUERY"],
"filter":{
"sitereference": [{"value":"test_site12345"}],
"currencyiso3a": [{"value":"GBP"}],
"transactionreference": [{"value":"23-9-1"},{"value":"23-9-2"}]
}
}]}'
{"alias":"[email protected]","version":"1.00","request":[{"requesttypedescriptions":["TRANSACTIONQUERY"],"filter":{"sitereference":[{"value":"test_site12345"}],"currencyiso3a":[{"value":"GBP"}],"transactionreference":[{"value":"23-9-1"},{"value":"23-9-2"}]}}]}
<?xml version="1.0" encoding="utf-8"?>
<requestblock version="3.67">
<alias>[email protected]</alias>
<request type="TRANSACTIONQUERY">
<filter>
<sitereference>test_site12345</sitereference>
<currencyiso3a>GBP</currencyiso3a>
<transactionreference>23-9-1</transactionreference>
<transactionreference>23-9-2</transactionreference>
</filter>
</request>
</requestblock>
Replace <DOMAIN> with a supported domain. Click here for a full list.
Field specification
The following table lists all fields that you can include in the filter when processing a TRANSACTIONQUERY request.
Note that although none of the following filter fields are required, at least one filter must be submitted for the request to be processed successfully. For this reason, all fields have been marked below as conditional.
TRANSACTIONQUERY response
Once you have successfully submitted a TRANSACTIONQUERY request, you will be returned a response that is divided into separate records.
Each record will contain a varying number of response fields, which depend on the request type indicated in the record. For example, if the record has a requesttypedescription of “AUTH“, then you would need to refer to the field specification in the Authorisation document.
Additionally, the response contains a field called found, which indicates the number of records that match the filters specified in the request. If found has a value of “0”, no records have been found using your specified filters.
For example, here is a simplified example of the structure of the response, consisting of 2 records (both are type “AUTH”):
{
u 'requestreference': u 'W72-pg3q2he9',
u 'version': u '1.00',
u 'response': [{
u 'transactionstartedtimestamp': u '2019-12-17 09:36:21',
u 'errormessage': u 'Ok',
u 'errorcode': u '0',
u 'records': [{
u 'transactionstartedtimestamp': u '2019-12-17 09:35:03',
u 'sitereference': u 'test_site12345',
u 'interface': u 'PASS-JSON-JSON',
u 'livestatus': u '0',
u 'issuer': u 'SecureTrading Test Issuer1',
u 'dccenabled': u '0',
u 'settleduedate': u '2019-12-17',
u 'errorcode': u '0',
u 'baseamount': u '1050',
u 'tid': u '27882788',
u 'securityresponsepostcode': u '0',
u 'transactionreference': u '72-9-80005',
u 'merchantname': u 'Test Merchant',
u 'paymenttypedescription': u 'VISA',
u 'accounttypedescription': u 'ECOM',
u 'fraudrating': u '0',
u 'splitfinalnumber': u '1',
u 'acquirerresponsecode': u '00',
u 'requesttypedescription': u 'AUTH',
u 'expirydate': u '10/2022',
u 'securityresponsesecuritycode': u '2',
u 'currencyiso3a': u 'GBP',
u 'authcode': u 'TEST22',
u 'settlebaseamount': u '1050',
u 'errormessage': u 'Ok',
u 'issuercountryiso2a': u 'US',
u 'merchantcountryiso2a': u 'GB',
u 'maskedpan': u '411111######1111',
u 'securityresponseaddress': u '0',
u 'operatorname': u '[email protected]',
u 'settlestatus': u '0'
}, {
u 'transactionstartedtimestamp': u '2019-12-17 09:35:10',
u 'sitereference': u 'test_site12345',
u 'interface': u 'PASS-JSON-JSON',
u 'livestatus': u '0',
u 'issuer': u 'SecureTrading Test Issuer1',
u 'dccenabled': u '0',
u 'settleduedate': u '2019-12-17',
u 'errorcode': u '0',
u 'baseamount': u '1050',
u 'tid': u '27882788',
u 'securityresponsepostcode': u '0',
u 'transactionreference': u '72-9-80006',
u 'merchantname': u 'Test Merchant',
u 'paymenttypedescription': u 'VISA',
u 'accounttypedescription': u 'ECOM',
u 'fraudrating': u '0',
u 'splitfinalnumber': u '1',
u 'acquirerresponsecode': u '00',
u 'requesttypedescription': u 'AUTH',
u 'expirydate': u '10/2022',
u 'securityresponsesecuritycode': u '2',
u 'currencyiso3a': u 'GBP',
u 'authcode': u 'TEST03',
u 'settlebaseamount': u '1050',
u 'errormessage': u 'Ok',
u 'issuercountryiso2a': u 'US',
u 'merchantcountryiso2a': u 'GB',
u 'maskedpan': u '411111######1111',
u 'securityresponseaddress': u '0',
u 'operatorname': u '[email protected]',
u 'settlestatus': u '0'
}],
u 'found': u '2',
u 'requesttypedescription': u 'TRANSACTIONQUERY'
}]
}
array(3) {
["requestreference"] => string(9) "W72-pg3q2he9"
["version"] => string(4) "1.00"
["response"] => array(1) {
[0] => array(6) {
["transactionstartedtimestamp"] => string(19) "2019-12-17 09:36:21"
["errormessage"] => string(2) "Ok"
["errorcode"] => string(1) "0"
["records"] => array(2) {
[0] => array(31) {
["transactionstartedtimestamp"] => string(19) "2019-12-17 09:35:03"
["sitereference"] => string(14) "test_site12345"
["interface"] => string(14) "PASS-JSON-JSON"
["livestatus"] => string(1) "0"
["issuer"] => string(26) "SecureTrading Test Issuer1"
["dccenabled"] => string(1) "0"
["settleduedate"] => string(10) "2019-12-17"
["errorcode"] => string(1) "0"
["baseamount"] => string(4) "1050"
["tid"] => string(8) "27882788"
["securityresponsepostcode"] => string(1) "0"
["transactionreference"] => string(10) "72-9-80005"
["merchantname"] => string(13) "Test Merchant"
["paymenttypedescription"] => string(4) "VISA"
["accounttypedescription"] => string(4) "ECOM"
["fraudrating"] => string(1) "0"
["splitfinalnumber"] => string(1) "1"
["acquirerresponsecode"] => string(2) "00"
["requesttypedescription"] => string(4) "AUTH"
["expirydate"] => string(7) "10/2022"
["securityresponsesecuritycode"] => string(1) "2"
["currencyiso3a"] => string(3) "GBP"
["authcode"] => string(6) "TEST22"
["settlebaseamount"] => string(4) "1050"
["errormessage"] => string(2) "Ok"
["issuercountryiso2a"] => string(2) "US"
["merchantcountryiso2a"] => string(2) "GB"
["maskedpan"] => string(16) "411111######1111"
["securityresponseaddress"] => string(1) "0"
["operatorname"] => string(23) "[email protected]"
["settlestatus"] => string(1) "0"
}
[1] => array(31) {
["transactionstartedtimestamp"] => string(19) "2019-12-17 09:35:10"
["sitereference"] => string(14) "test_site12345"
["interface"] => string(14) "PASS-JSON-JSON"
["livestatus"] => string(1) "0"
["issuer"] => string(26) "SecureTrading Test Issuer1"
["dccenabled"] => string(1) "0"
["settleduedate"] => string(10) "2019-12-17"
["errorcode"] => string(1) "0"
["baseamount"] => string(4) "1050"
["tid"] => string(8) "27882788"
["securityresponsepostcode"] => string(1) "0"
["transactionreference"] => string(10) "72-9-80006"
["merchantname"] => string(13) "Test Merchant"
["paymenttypedescription"] => string(4) "VISA"
["accounttypedescription"] => string(4) "ECOM"
["fraudrating"] => string(1) "0"
["splitfinalnumber"] => string(1) "1"
["acquirerresponsecode"] => string(2) "00"
["requesttypedescription"] => string(4) "AUTH"
["expirydate"] => string(7) "10/2022"
["securityresponsesecuritycode"] => string(1) "2"
["currencyiso3a"] => string(3) "GBP"
["authcode"] => string(6) "TEST03"
["settlebaseamount"] => string(4) "1050"
["errormessage"] => string(2) "Ok"
["issuercountryiso2a"] => string(2) "US"
["merchantcountryiso2a"] => string(2) "GB"
["maskedpan"] => string(16) "411111######1111"
["securityresponseaddress"] => string(1) "0"
["operatorname"] => string(23) "[email protected]"
["settlestatus"] => string(1) "0"
}
}
["found"] => string(1) "2"
["requesttypedescription"] => string(16) "TRANSACTIONQUERY"
}
}
}
{"requestreference":"W72-pg3q2he9","version":"1.00","response":[{"transactionstartedtimestamp":"2019-12-17 09:36:21","errormessage":"Ok","errorcode":"0","records":[{"transactionstartedtimestamp":"2019-12-17 09:35:03","sitereference":"test_site12345","interface":"PASS-JSON-JSON","livestatus":"0","issuer":"SecureTrading Test Issuer1","dccenabled":"0","settleduedate":"2019-12-17","errorcode":"0","baseamount":"1050","tid":"27882788","securityresponsepostcode":"0","transactionreference":"72-9-80005","merchantname":"Test Merchant","paymenttypedescription":"VISA","accounttypedescription":"ECOM","fraudrating":"0","splitfinalnumber":"1","acquirerresponsecode":"00","requesttypedescription":"AUTH","expirydate":"10\/2022","securityresponsesecuritycode":"2","currencyiso3a":"GBP","authcode":"TEST22","settlebaseamount":"1050","errormessage":"Ok","issuercountryiso2a":"US","merchantcountryiso2a":"GB","maskedpan":"411111######1111","securityresponseaddress":"0","operatorname":"[email protected]","settlestatus":"0"},{"transactionstartedtimestamp":"2019-12-17 09:35:10","sitereference":"test_site12345","interface":"PASS-JSON-JSON","livestatus":"0","issuer":"SecureTrading Test Issuer1","dccenabled":"0","settleduedate":"2019-12-17","errorcode":"0","baseamount":"1050","tid":"27882788","securityresponsepostcode":"0","transactionreference":"72-9-80006","merchantname":"Test Merchant","paymenttypedescription":"VISA","accounttypedescription":"ECOM","fraudrating":"0","splitfinalnumber":"1","acquirerresponsecode":"00","requesttypedescription":"AUTH","expirydate":"10\/2022","securityresponsesecuritycode":"2","currencyiso3a":"GBP","authcode":"TEST03","settlebaseamount":"1050","errormessage":"Ok","issuercountryiso2a":"US","merchantcountryiso2a":"GB","maskedpan":"411111######1111","securityresponseaddress":"0","operatorname":"[email protected]","settlestatus":"0"}],"found":"2","requesttypedescription":"TRANSACTIONQUERY"}],"secrand":"uISZfw8wKWR"}
<?xml version='1.0' encoding='utf-8'?>
<responseblock version="3.67">
<requestreference>Xv18xwv52</requestreference>
<response type="TRANSACTIONQUERY">
<record type="AUTH">
<acquirerresponsecode>00</acquirerresponsecode>
<operation>
<splitfinalnumber>1</splitfinalnumber>
<sitereference>test_site12345</sitereference>
<interface>CERT-XML-XML</interface>
<accounttypedescription>ECOM</accounttypedescription>
</operation>
<settlement>
<settleduedate>2019-12-17</settleduedate>
<settlebaseamount>1050</settlebaseamount>
<settlestatus>0</settlestatus>
</settlement>
<billing>
<dcc enabled="0"/>
<amount currencycode="GBP">1050</amount>
<payment type="VISA">
<issuer>SecureTrading Test Issuer1</issuer>
<expirydate>10/2022</expirydate>
<pan>411111######1111</pan>
<issuercountry>US</issuercountry>
</payment>
</billing>
<live>0</live>
<merchant>
<tid>27882788</tid>
<merchantcountryiso2a>GB</merchantcountryiso2a>
<merchantname>Test Merchant</merchantname>
<operatorname>[email protected]</operatorname>
</merchant>
<transactionreference>72-9-80003</transactionreference>
<timestamp>2019-12-17 09:17:58</timestamp>
<error>
<message>Ok</message>
<code>0</code>
</error>
<fraud>
<rating>0</rating>
</fraud>
<authcode>TEST35</authcode>
<security>
<postcode>0</postcode>
<securitycode>2</securitycode>
<address>0</address>
</security>
</record>
<record type="AUTH">
<acquirerresponsecode>00</acquirerresponsecode>
<operation>
<splitfinalnumber>1</splitfinalnumber>
<sitereference>test_site12345</sitereference>
<interface>CERT-XML-XML</interface>
<accounttypedescription>ECOM</accounttypedescription>
</operation>
<settlement>
<settleduedate>2019-12-17</settleduedate>
<settlebaseamount>1050</settlebaseamount>
<settlestatus>0</settlestatus>
</settlement>
<billing>
<dcc enabled="0"/>
<amount currencycode="GBP">1050</amount>
<payment type="VISA">
<issuer>SecureTrading Test Issuer1</issuer>
<expirydate>10/2022</expirydate>
<pan>411111######1111</pan>
<issuercountry>US</issuercountry>
</payment>
</billing>
<live>0</live>
<merchant>
<tid>27882788</tid>
<merchantcountryiso2a>GB</merchantcountryiso2a>
<merchantname>Test Merchant</merchantname>
<operatorname>[email protected]</operatorname>
</merchant>
<transactionreference>72-9-80004</transactionreference>
<timestamp>2019-12-17 09:18:00</timestamp>
<error>
<message>Ok</message>
<code>0</code>
</error>
<fraud>
<rating>0</rating>
</fraud>
<authcode>TEST06</authcode>
<security>
<postcode>0</postcode>
<securitycode>2</securitycode>
<address>0</address>
</security>
</record>
<found>2</found>
<error>
<message>Ok</message>
<code>0</code>
</error>
<timestamp>2019-12-17 09:19:00</timestamp>
</response>
<secrand>IDBpVj</secrand>
</responseblock>

A maximum of 500 records can be returned per response.
The found field will never return a value higher than 500, even if more than 500 requests meet the specified criteria.
Understanding errors
Please ensure you understand the Error Codes returned in the response:
- At the highest level of the response, along with transactionstartedtimestamp and found, there is an errorcode. This indicates whether or not the TRANSACTIONQUERY request was successful. If the error code here is not “0”, the TRANSACTIONQUERY request was not successful. You must address the problem and try again.
- In addition to this, each record will contain their own errorcode. This indicates whether or not the request represented in the record was successful.
- For a full list of error codes used by Trust Payments please click here.
Additional resources