Overview
The Payment API allows you to securely and efficiently process e-commerce (ECOM) card transactions, where customers enter their payment details to complete payments. This method is commonly used for online checkouts, shopping carts, and paying invoices. To maintain security, all transactions are processed through 3DS, a required security feature designed to prevent card fraud.
Features
3D Secure (3DS)
All ECOM card transactions processed through Blink must pass 3DS checks. During this process, the API collects additional customer data (e.g., IP address, device, browser information) in the background and sends it, along with payment details, to the 3DS Access Control Server (ACS) for verification. The ACS will either approve the transaction or prompt the customer for further authentication (e.g., an SMS code or confirmation via a banking app). This extra step ensures a high level of security and helps significantly reduce the risk of fraud-related chargebacks.
Transaction information
To make each transaction unique and easily identifiable, the API provides several tracking methods for both pre- and post-processing stages.
Payment Intent: Every transaction must have an associated payment intent. This allows you to monitor the entire payment journey from the moment the transaction is initiated.
Transaction Unique Reference: Transactions require a
transaction_uniquereference. This can be used to reconcile transactions or track them. You can generate this reference manually or use thetransaction_uniqueprovided by the Intents API.Transaction ID: After the transaction is processed, a
transaction IDis included in the result. This ID is used to track the transaction as it moves through various states.
Customer Information
It is mandatory to provide the customer’s name and email with each transaction. This information helps identify the transaction, whether it's linked to an invoice, an order, or in the case of a refund. If email receipts are enabled, the customer will receive a receipt via email. Additionally, you can include the billing address and postcode. Although these fields are optional, they may be required for Address Verification Service (AVS) security checks.
Additional Information
You can add extra data to the transaction using a JSON-encoded string called merchant_data. This feature is useful for integrating with third-party systems that require additional transaction-related information, such as order details, inventory, or multiple invoices.
Repeat Payments
As well as single payments, it is possible to create subscription payment cycles from a ECOM transaction. Click here for more details.
Endpoints Overview
POST creditcards: This endpoint is to charge customers via card either by MOTO or ECOM transactions