Request verification

A request verification URL can be configured as part of this API. If this is set, then when the API receives a transaction request, the details (not including the card information) will be set to the verification URL in order to confirm that the request is valid.

The transaction details will be sent as an XML request, directly from the payment gateway to the merchants systems. The verification request will not be sent via the mobile device. The verification request will contain the transaction details received by the mobile API.

Verification message from gateway to merchant systems:

<?xml version="1.0" encoding="UTF-8"?>
<verify>
  <store>Store ID</store>
  <key>Verification Key</key>
  <device>
    <type>Mobile device type</type>
    <id>Mobile device ID</id>
  </device>
  <app>
    <name>Application name</name>
    <version>Application version</version>
    <user>Application user ID</user>
    <id>Application installation ID</id>
  </app>
  <tran>
    <test>Test mode</test>
    <type>Transaction type</type>
    <class>Transaction class</class>
    <cartid>Transaction cart ID</cartid>
    <description>Transaction description</description>
    <currency>Transaction currency</currency>
    <amount>Transaction amount</amount>
    <ref>Previous transaction reference</ref>
  </tran>
</verify>

This provides the opportunity to either block the request, or allow it to continue for authorisation.

The verification response should consist simply of a Yes or No status

<?xml version="1.0" encoding="UTF-8"?>
<verify>
    <allow>Yes or No</allow>
</verify>

You should ensure that the verify process completes as quickly as possible. The transaction cannot be processed until this has been done. If the request to the verification URL cannot be completed (such as an error occurring whilst processing the request), the gateway will assume that verification has failed and will block the transaction request.

Update billing details

The verification response can also contain the billing details for the customer. This allows the initial mobile API request to omit the billing section. In this case, the verification response should be as follows:

<?xml version="1.0" encoding="UTF-8"?>
<verify>
  <allow>Yes or No</allow>
  <billing>
  <name>
    <title>Title</title>
    <first>Forenames</first>
    <last>Surname</last>
  </name>
  <address>
    <line1>Street address – line 1</line1>
    <line2>Street address – line 2</line2>
    <line3>Street address – line 3</line3>
    <city>City</city>
    <region>Region</region>
    <country>Country</country>
    <zip>Zip/Area/Postcode</zip>
  </address>
  <email>Email address</email>
  </billing>
</verify>

If the section is provided, then any billing details that were sent as part of the initial request will be replaced with the details here. These details must include all of the required information.