Credit a beneficiary

post

https://sandbox.examplebank.com/blinc/credit-instructions

Blinc asks the acquiring institution to send money to one beneficiary. The institution validates the account, amount, fees, and references before crediting it once. If Blinc does not receive a response, it may deliver the same Credit Instruction again; return the earlier outcome without crediting the account twice. Read how to send money to a beneficiary.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Signed and encrypted request body. The JSON body contains the Base64 data envelope. Content-Type must be application/json, and the signature is supplied in the x-signature header.

The complete HTTP body. The data value is the Base64-encoded encrypted envelope. The institutional ECDSA signature is supplied in the x-signature header, not in the JSON body.

data

string

required

Base64-encoded bytes joined in this order: the one-use P-256 public key (65 bytes), the 12-byte nonce, the AES-256-GCM ciphertext, and the 16-byte authentication tag. Derive the AES key with ECDH and HKDF-SHA256 using the info value blinc-e2ee.

Headers

x-timestamp

string

required

UTC time when this protected HTTP delivery was created. Use yyyy-MM-dd'T'HH:mm:ss.fff'Z' and reject stale or future deliveries outside the agreed clock-skew window.

x-signature

string

required

Base64 of the 64-byte IEEE P1363 P-256 ECDSA signature over the exact compact plaintext UTF-8 bytes.

Responses

400

Malformed outer JSON. Standard validation response.

Language

Loading…

Response

Choose an example:

application/json

200The institution received the protected request and returned a protected business result. Decrypt the body to read whether the business action was accepted or rejected.