Authorise Payment

Each payment type requires a different payload, depending on the requirements of the scheme and currency. Check the examples on the right to see the different supported transfers

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
integer
required

YOUR_COUNTERPARTY_ID

string
required

YOUR_ACCOUNT_ID

string
required

ISO4217 currency code EG: GBP

string
required
string
required
string
required
string

This information is not relayed on the payment

string
enum
required
Defaults to AUTO

AUTO > for external payments BLINC > for payments inside BLINC network, must use BLINC accounts INTERNAL > for payments between BCB accounts of the same counterparty

Allowed:
string
required

Nonce field ensures that payment requests can only be processed once, If the nonce for a payment request is not unique for the account then it will be rejected.

integer
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string
string

Mandatory for CHAPS

string
string
string
intermediary_bank
object

Only valid for USD SWIFT

Headers
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
text/html