Response Handling
The endpoint always returns 200 with anOversightResponse. The outcome field determines whether the payment is accepted or rejected.
Fallback behavior — If the oversight endpoint returns a non-200 response or times out, the system applies a fallback based on payment direction:
- Outbound payments are rejected.
- Inbound payments are accepted with no additional postings.
Decision outcome. Either
ACCEPTED or REJECTED.Accepting a payment
Returnoutcome: "ACCEPTED" with an optional array of additional postings to execute alongside the payment.
Additional postings to execute alongside the payment
destination needs to be specified.
Accept with additional postings:
200
200
Rejecting a payment
Returnoutcome: "REJECTED" with an optional rejection code. If the code is not provided or unrecognized, it defaults to MS03.
Rejection reason code. Optional — defaults to
MS03 if omitted. Supported values:| Code | Description |
|---|---|
AG01 | Credit transfer forbidden on this type of account |
AG02 | Invalid operation code or transaction format |
AM05 | Duplicate payment |
BE04 | Invalid account address |
MD07 | Beneficiary deceased |
MS02 | By order of the beneficiary |
MS03 | Reason not specified (default) |
RR01 | Missing debtor account or identification |
RR02 | Missing debtor name or address |
RR03 | Missing creditor name or address |
RR04 | Other regulatory reason (AML, sanctions screening, etc.) |
200