Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Process the payment and return to the user defined URL with encoded transaction ID.



Open Banking

POST /pay/v1/openbankings

Headers

Content-Type string
Content type.

Authorization string
Access token generated from create token request.

Attributes

merchant_id integer
Merchant id.

payment_intent string
Payment intent token.

paymentToken string
Payment 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...

{
    "merchant_id": "123456",
    "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

{
    "url": "https://api-demo-php.blinkpayment.co.uk/return?res=BL-45SACNBTG"
}

  • No labels