...
1.00Introduction
This is a simple guide in how to integrate your website with the Blink gateway so that you can accept payments straight from your website. If you require a more advanced integration, please contact our Integrations Team.
...
The request is made using the URL: https://gateway2.blinkpayment.co.uk/hosted/modal, with the merchant credentials (MID and signature key), amount, reference and customer details.
...
Once the customer has completed the payment, they can be redirected back to the merchant site, the . The response fields can be collected on the merchant website.
...
sent to the merchant site.
Benefits
Easy set up
Secure (Payment journey is handled completely by Blink)
...
Redirects - Customer has to leave merchant site ( using the lightbox overlay the gateway can be opened in an iframe, overlaying the merchant site, which mitigates this issue).
Takes longer for customer to go through payment journey.
Customisation is difficult and limited.
Direct
| Note |
|---|
The IP address of the merchant site must be whitelisted by Blink. The merchant site must have a valid SSL (for 3DS transactions). |
The request is made using the URL: https://gateway2.blinkpayment.co.uk/direct. It is made directly from the merchant site. All payment details (including card details) must be sent in one requestunlike the hosted integration, all the required fields (amount, name, card number…) can be sent in one form, making the payment journey quicker and easier.
When initiated, the transaction request details are sent to the gateway from the site.
Once the payment is complete, the response is sent immediately to the merchant site.
Benefits
...
More venerable to security issues/ attacks.
Troubleshooting can be more difficult.
Set up is more complicated as it requires IP whitelisting and implementing 3DS checking code.
Direct with hosted fields
Request
Required Fields
Field Name | Description | |
|---|---|---|
| 1 | Merchant ID | Your Merchant Gateway ID (Can be found on Take a Payment and Request a Payment) |
| 2 | signature | Unique key related to your merchant ID, the signature key is encrypted before the request is sent. Please contact our support team to find out your signature key. |
| 3 | action | The Action requested. Typically, SALE |
| 4 | amount | Transaction Amount |
| 5 | type | 1 - E-commerce (ECOM) - standard online payments. 2 - Mail Order Telephone Order (MOTO) - the merchant is inputting inputs the customer’s card details. 9 - Continuous Authority (CA) - for recurring and rerunning transactions. |
| 6 | countryCode | Merchant’s Location (for UK 826) |
| 7 | currencyCode | Transaction currency code (for UK 826) |
| 8 | cardNumber | The primary account number (PAN). Digits and spaces only - Direct Integration Only |
| 9 | cardExpiryMonth | The card’s expiry month from 1 to 12. - Direct Integration Only |
| 10 | cardExpiryYear | The card’s expiry year from 00 to 99. - Direct Integration Only |
| 11 | cardCVV | Payment card’s security number. The 3 or 4 digit number printed on the signature strip. - Direct Integration Only |
...
Field Name | Description | |
|---|---|---|
| 1 | orderDate | Recorded date of the transaction |
| 2 | xref | Refers to a pervious transaction, this is used to rerun or refund previous transactions. |
| 3 | captureDelay | Number of days to wait between authorisation of a payment and subsequent settlementDelay the actual money transfer by an amount of days. |
| 4 | merchantPwd | Additional password to increase authentication security. |
...
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. |
acquirerResponseXXXX | Depends on the acquirer | Additional Response sent by acquirer |
xref | Yes | Used to rerun or refund transactions at a later point. |
state | Yes | Transaction state |
timestamp | Yes | The time when the transaction was last modified |
cardNumberMask | Yes | Masked card numberThe first 4 digits and last 4 digits of the customer’s PAN card number. The rest of the digits are encrypted. |
transactionUnique | If sent in request | Any value supplied in the initial request. |
orderRef | If sent in request | Any value supplied in the initial request. |
authorisationCode | If transaction was successful | Authorisation code (Auth Code) received from Acquirer. |
amountReceived | If transaction was successful | Amount the Acquirer authorised. This should always be the full amount in the request. |
cardTypeCode | Yes | Code identifying the type of card used. |
cardType | Yes | Description of the type of card used. |
cardSchemeCode | Yes | Code identifying the Card Scheme used. |
cardScheme | Yes | Description of the Card Scheme used. |
cardIssuer | Yes | Card Issues name |
cardIssuerCountry | Yes | Card issuing country’s name |
cardIssuerCountryCode | Yes | Card issuing country’s ISO-3166 2-letter code |
amountRefunded | If it is a refund | Total amount of original SALE that has so far been refunded. Returned when action is REFUND_SALE |
...
Transactions are limited from £1.00 01 to £24.99. If they not in this range, the transaction will fail.
...