BlockAndReleaseFunds
POST
https://test.api.neotek.sa/b2b-unified/va/v1/remitters/{remitterId}/funds/blockSandbox URL · in Production call https://api.neotek.sa
POST
https://test.api.neotek.sa/b2b-unified/va/v1/remitters/{remitterId}/funds/releaseSandbox URL · in Production call https://api.neotek.sa
Blocking reserves an amount in a VA: it reduces availableBalance but the money stays in the account, showing as blockedBalance. Releasing returns it to available. The two calls take the same request and return the same response — only the path differs.
Path parameters:
| Parameter | Required | Description |
|---|---|---|
remitterId | Required | the VA identifier |
Body:
| Parameter | Required | Description |
|---|---|---|
bankCode | Required | always RJHISARI |
remitterIban | Required | the VA IBAN from the create response, 24 characters |
amount | Required | decimal, minimum 0.01 |
schemeId | Optional | required only if you have several schemes |
msgReference | Optional | generated if omitted |
Headers:
| Parameter | Required | Description |
|---|---|---|
authorization | Required | Bearer <ACCESS_TOKEN> |
content-type | Required | application/json |
cURL
curl -X POST 'https://test.api.neotek.sa/b2b-unified/va/v1/remitters/{remitterId}/funds/block' \ --header 'authorization: Bearer <ACCESS_TOKEN>' \ --header 'content-type: application/json' \ --data '{ "bankCode": "RJHISARI", "remitterIban": "SA4580000204000010006087", "amount": "10000.00" }'Response
JSON
{ "success": true, "code": "SUCCESS", "message": "Funds blocked successfully", "remitterId": "CUST001", "remitterIban": "SA4580000204000010006087", "amount": "10000.00", "schemeId": "SCHEME001", "msgReference": "FBK001"}Errors — every B2B failure carries a category that determines the HTTP status; see Statements → Errors.