...
Field Name | Description | |
|---|---|---|
| 1 | transactionUnique | You can supply a unique identifier for this transaction. This is an added security feature to combat transaction spoofing. |
| 2 | customerName | Name of Customer |
| 3 | customerEmail | Email Address of customer |
| 4 | customerAddress | Address of customer - may be required depending on AVS checks |
| 5 | customerPostCode | Post code of customer - may be required depending on AVS checks |
| 6 | orderRef | Free format text field to store order details, reference numbers, etc. for the Merchant’s records. Essentially, an additional identifier. |
| 7 | redirectURL | URL to which the hosted form will redirect the Customer’s browser after the transaction has been completed. The URL must be fully qualified and include at least the scheme and host components. (Only relevant to Hosted integration) |
Advanced Fields
Field Name | Description | |
|---|---|---|
| 1 | orderDate | Record Date of the transaction |
| 2 | xref | Refers to s pervious transaction, this is used to rerun previous transactions. |
| 3 | captureDelay | Number of days to wait between authorisation of a payment and subsequent settlement. |
Response
Field Name | Always Returned? | Description |
|---|---|---|
respnseCode | Yes | A numeric code providing the specific outcome. Common values are: 0 - Successful / authorised transaction. 1 - Card referred – Refer to card issuer. 2 - Card referred – Special condition. 4 - Card declined – Keep card. 5 - Card declined |
responseStatus | Yes | A numeric code providing the outcome category. Possible values are: 0 – Authorisation Approved / No reason to decline 1 – Authorisation Declined. 2 – Authorisation Error / Transaction malformed. |
responseMessage | Yes | Message received from the Acquiring bank, or any error message. |
transactionID | Yes | A unique ID assigned by the Gateway. |
xref | Yes | Used to rerun transactions at a later point. |
state | Yes | Transaction state |
timestamp | Yes | The time when the transaction was last modified |
transactionUnique | If sent in request | Any value supplied in the initial request. |
authorisationCode | If transaction was successful | Authorisation code received from Acquirer. |
Test Accounts
If you would like to test an integration, please be in touch with our integrations team, who will send you Blink test account credentials. The merchant will be able to see the test transactions on their Blink account.
...