Frequently asked questions
Visit our FAQ section to find clear answers quickly. If your question isn’t covered, please reach out to us at integrationsupport@blinkpayment.co.uk.
How do I load the card PAN, CVV, and expiration date?
When you create a payment intent, you will receive a parameter called elements. These elements consist of various HTML codes that you need to render on the page within a submission form. For the card element (ccElement or ccMotoElement), you need to add our custom jQuery to the head of your HTML document. Once you have successfully done this, you will see a black card icon next to the card input.
What does a developer need to develop an integration?
To integrate the Blink payment API, you must first obtain your API Key and Secret Key to create an integration. These can be found in your Blink payment account. To generate your keys, select the option to Enable the API next to your profile. Find a how-to guide here.
What is the payment flow?
Blink offers card (MOTO), Card (ECOM), open banking and Direct Debit. Discover diagrams showcasing all of the steps involved in processing each type of payment method, as well as whether the action is on your server, the client, or through a redirect URL. Find more details on the payment flows here.
Transaction statuses
For developers integrating a payment API, familiarizing yourself with transaction statuses is key to effective error handling, improving user experience, and maintaining reliable transaction management within your application.
Learn more about Blink payment transaction statuses.
Status details
Status | Details |
|---|---|
Pending | Gateway received the transaction; awaits final state response. |
Successful | Transaction captured, will settle soon (typically overnight). |
Pre-Auth | Card verified, amount available. Card details encrypted for capture within 30 days. |
Verified | Card's authenticity confirmed; encrypted details allow future transaction. |
Capture in "x" days | Shows days left until delayed capture amount is taken. |
Declined | Transaction was declined. |
Referred | Transaction requires manual approval by acquiring bank. Merchants may need to contact Support for the authorization code. |
Cancelled | Merchant cancelled the transaction (only possible for captured transactions). |
Transaction Notes
Transaction notes |
|---|
(DC): Delay capture now captured. |
(PA): Captured Pre-Auth. |
(RF): Refund. |
(RR): Rerun from a prior transaction. |
(V): Transaction from a Verified card. |
Selecting a transaction reveals more information and available actions. Card verification responses (like 3DS, AVS, CV2), acquiring bank, card type, authorization code, and the Blink Unique Reference are also displayed here.
Should you require further assistance, please contact our integration team at integrationsupport@blinkpayment.co.uk.