...
Variable | Description | Example |
|---|---|---|
Response Code | Code indicating whether transaction was successful (0) or if there is an issue with the transaction (error code) | Successful transactions = 0 3ds Authentication Required = 65802 |
Response Message | Message indicating the transaction was successful or Error message. | AUTHCODE:121590 |
responseStatus | A numeric code providing the outcome category | 0 – Authorisation Approved / No reason to decline. 1 – Authorisation Declined. 2 – Authorisation Error / Transaction malformed. |
state | State of the transaction | Captured or Declined |
authorisationCode | Code given by the acquirer, indicating a successful transaction | 121590 |
merchantID | Your unique Gateway ID which processed the transaction | 138791 |
customerName | Name of customer | Fred Bloggs |
customerEmail | Email of customer | f.bloggs@example.com |
customerAddress | Billing address of customer (required for AVS checking) | 76 Roseby Avenue Manchester |
customerPostcode | Post Code of customer (required for AVS checking) | M63X 7TH |
amount | Amount customer was charged (Is given in the smallest value currency e.g. pennies) | 1000 (10.00) |
currencyCode | ISO 4217 of the currency which was charged with | 826 (for GBP) |
currencySymbol | Symbol of the currency which was charged with | £ (for GBP) |
transactionUnique | Reference | InvoiceNumber1 |
orderRef | Description | Blink - BP |
transactionID | Unique ID of Transaction | 198662389 |
xref | Unique reference of transaction. (Used for rerunning/ refunding transactions outside of Blink) | 22102410HV18ZT13VQ68NFP |
cardScheme | Card scheme of the customer’s card | Visa |
cardType | Card type of the customer’s card | Visa Credit |
cardNumberMask | First 5 and last 4 digits of the customers PAN number | 454305******9982 |
cardExpiryDate | Date the card expires | 1222 (MMYY) |
cardExpiryMonth | Month the card expires | 12 |
cardExpiryYear | Year the card expires | 22 |
cardIssuer | Bank associated with customer’s card | THE ROYAL BANK OF SCOTLAND PLC |
cardIssuerCountry | Country of the customer’s bank | United Kingdom |
Recommended Formatting
Format amount
format expire date
3ds
...
Ecom Transactions & 3ds
When a customer completes a transaction on a Blink Page, Paylink or online integration, the transaction goes through 3ds authentication. This means that for one Ecom transaction, the CallbackURL will receive two consecutive responses: the first response is the customer’s card going through 3ds checks. The responseCode is 65802, the responseStatus is 2, the responseMessage is 3DS authentication required, and the state is received.
The second response is when 3ds checks have been completed. If it has passed the 3ds checks then the responseCode is 0, the responseStatus is 0, the responseMessage will indicate the transactions was successful, and the state is captured.
Amount field
The amount is given the smallest value of the currency, so for GBP, £1.00 will be 100. To convert it to £, please divide the amount by 100. The amount is also stored as a string, so you would also need to convert it to a number. Alternatively, you can place a “.” before the last 2 digits.
Expiry date
The cardExpiryDate is sent in MMYY format, without a slash to separate the month and year. You may want to add in the slash or you can represent using the other expiry fields: cardExpiryMonth+"/"+cardExpiryYear.