Versions Compared

Old Version 13

changes.mady.by.user Sainita Mukherjee

Saved on

compared with

New Version 14

changes.mady.by.user Sainita Mukherjee

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Process the payment and return to the user defined URL with encoded transaction IDthe 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

Anchor
ob-process
ob-process

Open Banking

POST /pay/v1/openbankings

Headers

Content-Typestring
Content type.

Authorizationstring
Access token generated from create token request.

Attributes

payment_intentstring
Payment intent token.

customer_emailstring
Customer email.

customer_namestring
Customer name.

customer_addressstring (optional)
User’s address details.

customer_postcodestring (optional)
User’s postcode.

transaction_uniquestring
Transaction unique.

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

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

Request

Code Block
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

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

{
    "redirect_url": "https://api-demo-php.blinkpayment.co.uk/return?res=BL-45SACNBTGfidelitygate.devandops.com/tobp-gateway/hppcallredirect/643f****************"
}