4️⃣ Process your first transaction

Process test payment

Once you have updated your payment form and configured the library, you can process a test card payment through our sandbox. Using the form you configured earlier, fill out the form with the following test payment credentials and click “Pay” to perform a test transaction.

When testing, you can use the following test card details to simulate a “Successful” response:

• Visa card ‘4111 1111 1111 1111’ or Mastercard ‘5100 0000 0000 0511’
• Set expiry date to any valid date in the future
• Use security code “123”

After the form has been submitted, the “st.js” will open the overlay in the browser for authentication. The results of the authentication performed and the subsequent payment will be added to the form (with id=“st-form”), which will then be posted directly to the server specified in the action attribute of the form, in the format of an application/x-www-form-urlencoded POST.

Decode JWT response

The outcome of the request processed will be returned in the form of a new JWT. The following is an example of a response returned by Trust Payments:

(Decoded token)

{
  'jwt': 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJ3ZWJzZXJ2aWNlc0BtZXJjaGFudC5jb20iLCJpYXQiOjE2MDU3OTUyMTYsInBheWxvYWQiOnsiY3VycmVuY3lpc28zYSI6Ik9NUiIsImJhc2VhbW91bnQiOiIxMDAwIiwicGFyZW50dHJhbnNhY3Rpb25yZWZlcmVuY2UiOiI0Mi03MC0xMTMiLCJzaXRlcmVmZXJlbmNlIjoibGl2ZTIiLCJyZXF1ZXN0dHlwZWRlc2NyaXB0aW9ucyI6W10sImFjY291bnR0eXBlZGVzY3JpcHRpb24iOiJFQ09NIn19.uGc6ePF31K2QNmIWOh7XzvRQjk_tRPK4gOZv5-hfHDM',
  'requestreference': 'W12-3456abc',
  'response': [{
    'accounttypedescription': 'ECOM',
    'chargedescription': 'Descriptor',
    'dccenabled': '0',
    'enrolled': 'N',
    'errorcode': '0',
    'errormessage': 'Ok',
    'issuercountryiso2a': 'ZZ',
    'livestatus': '0',
    'maskedpan': '400000######1026',
    'merchantcategorycode': '0000',
    'merchantcity': 'Bangor',
    'merchantcountryiso2a': 'GB',
    'merchantname': 'Test merchant',
    'merchantnumber': '00000000',
    'merchantzipcode': 'TR45 6ST',
    'operatorname': 'webservices@example.com',
    'parenttransactionreference': '12-34-567',
    'paymenttypedescription': 'VISA',
    'requesttypedescription': 'THREEDQUERY',
    'settleduedate': '2020-11-19',
    'settlestatus': '0',
    'threedversion': '1.0.2',
    'transactionreference': '12-34-567',
    'transactionstartedtimestamp': '2020-11-19 14:13:36',
    'xid': 'bUZHNFVUQ2dSNk11WUFkdUx0d1o='
  }, {
    'accounttypedescription': 'ECOM',
    'acquirerresponsecode': '00',
    'acquirerresponsemessage': 'Approved or completed Successfully',
    'authcode': '000004',
    'baseamount': '1050',
    'chargedescription': 'Descriptor',
    'currencyiso3a': 'GBP',
    'customeroutput': 'RESULT',
    'dccenabled': '0',
    'enrolled': 'N',
    'errorcode': '0',
    'errormessage': 'Ok',
    'issuercountryiso2a': 'ZZ',
    'livestatus': '0',
    'maskedpan': '400000######1026',
    'merchantcategorycode': '0000',
    'merchantcity': 'Manchester',
    'merchantcountryiso2a': 'GB',
    'merchantname': 'Test merchant',
    'merchantnumber': '00000000',
    'merchantzipcode': 'TR45 6ST',
    'operatorname': 'webservices@example.com',
    'transactionreference': '12-34-567',
    'paymenttypedescription': 'VISA',
    'requesttypedescription': 'AUTH',
    'retrievalreferencenumber': '032414420113',
    'securityresponseaddress': '0',
    'securityresponsepostcode': '0',
    'securityresponsesecuritycode': '2',
    'settleduedate': '2020-11-19',
    'settlestatus': '0',
    'splitfinalnumber': '1',
    'stan': '420113',
    'threedversion': '1.0.2',
    'transactionreference': '12-34-568',
    'transactionstartedtimestamp': '2020-11-19 14:13:36'
  }],
  'secrand': 'ce3Z',
  'version': '1.00'
}

To view the full response, you will need to decode the JWT returned.

The response JWT consists of three parts separated by dots (“.”), in the following format:

Header.Payload.Signature

The signature is hashed using SHA-256, and as such, cannot be decoded. This means that to check the signature is correct, your system will need to re-calculate it using the header and payload returned.
Providing you use the same secret during this process, the recalculated signature should match that returned in the response JWT. In summary:

1. Base64URL decode JWT header
2. Base64URL decode JWT payload
3. Re-generate the signature by re-encoding the header, the payload and signing them with your secret.
   (as explained above)

Response fields

After you receive the response, we recommend you review the information below when handling the customer’s payment session:

Transaction reference

The transactionreference is a unique identifier for the transaction. You will need to record this reference in order to query or perform other actions on this transaction at a later time.

Request type

You will need to check the requesttypedescription returned in the response. Only values of “AUTH” indicate the authorisation of a payment. Click here for a full list of different request types supported by Trust Payments.

Order reference

The orderreference is a custom identifier for the transaction that we recommend you submit in the JWT payload of each transaction. If your system has been configured to assign orderreference values to your transactions, you can use these to ensure you are checking the correct response following a payment.

Error code

You will need to check the errorcode returned in the AUTH response to determine the outcome of the transaction:

Settle status

You will need to check the settlestatus returned in the response:

3-D enrolled

The enrolled field will inform you if the customer’s card is enrolled in 3-D Secure:

3-D status

The status field will inform you if the customer was successfully authenticated during the 3-D Secure process:

3-D version

The version field specifies the version of 3-D Secure used for the payment. The value will start with either “1.x.x” to denote 3-D Secure v1, or “2.x.x” to denote 3-D Secure v2.