Open Bankings

Process the payment and return the banking server redirect url as response. After completion of the transaction, user will be redirected to the return url with url encoded transaction response.

Resources

POST /pay/v1/openbankings

Open Banking

POST /pay/v1/openbankings

Headers

Content-Type string
Content type.

Authorization string
Access token generated from create token request.

Attributes

payment_intent string
Payment intent token.

customer_email string
Customer email.

customer_name string
Customer name.

customer_address string (optional)
User’s address details.

customer_postcode string (optional)
User’s postcode.

transaction_unique string
Transaction unique.

merchant_data json (optional)
The merchant can add custom key value pairs in JSON format, for example:

{
  "my_order_id": 123,
  "fancy_note": "Order complete",
  "card_discount": false
}

Request

POST https://secure.blinkpayment.co.uk/api/pay/v1/openbankings HTTP/1.1
Content-Type: application/json
Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbG...

{
    "payment_intent": "pi_Swhc84aSLtUGppvPARX...",
    "customer_email": "random@email.com",
    "customer_name": "A Smith",
    "transaction_unique": "syuryui",
    "merchant_data": "{\"my_order_id\": \"ob-12345678\"}"
}

Response

HTTP/1.1 200 OK
Content-Type: application/json

{
    "redirect_url": "https://fidelitygate.devandops.com/tobp-gateway/hppcallredirect/643f****************"
}

Response codes

Code	Status	Title	Message	Notes
200	Success	Success	Payment successful	If payment is successful, then this status will be returned
400	Failed	Validation error	Customer name is required	If customer name is not present, this status will be returned
400	Failed	Validation error	Customer email is required	If customer email is not present, this status will be returned
500	Failed	Failed	Payment Failed	If payment is not successful, then this status will be returned