Posteering
Reference

Register the terminal outcome for one of your in-flight sandbox outbound transfers.

Sandbox-only. Your transfer resolves through the real requery -> transition -> callback pipeline; your callbackUrl receives a real, signed terminal callback (transfer.confirmed or transfer.failed) within ~30 seconds. Target must be your own transfer, in state "submitted". Registering again before resolution replaces the pending outcome. To exercise the "unknown" deadline path, register nothing and let the requery schedule exhaust.

POST
/api/v1/bankrail/sandbox/simulate-outbound-settlement

Authorization

X-Bankrail-Key-Id<token>

Partner-visible credential identifier issued by bank-rail at credential provisioning time. Names which credential signed the request; the corresponding signing secret never appears in any request.

In: header

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

curl -X POST "https://example.com/api/v1/bankrail/sandbox/simulate-outbound-settlement" \  -H "Content-Type: application/json" \  -d '{    "outcome": "confirmed"  }'
{  "transferId": "string",  "clientReference": "string",  "registeredOutcome": "confirmed",  "message": "string"}
Empty
Empty
Empty
Empty
Empty
Empty