Payment Promises and Netting
Payment Promises and Netting
A payment between two banks can be held as a promise, then settled later together with the other promises between the same two banks, as one net transaction.
A promise is a transaction request of the type OPEN_CORRIDOR_PROMISE. It carries the payer's originator information, as FATF Recommendation 16 requires. It is held at the status PENDING, and no Transaction is posted when it is created. Evidence can be attached to it.
The settle step nets all the pending promises between a pair of banks and posts one net Transaction, which covers them. Fees are settled separately.
It is off unless open_corridor_enabled=true. Whether it is on shows in the bank's transaction request types. The caller is a User with access to the view, or an application acting as itself whose Consumer has access to the view (see here).
Endpoints
- Create Transaction Request (OPEN_CORRIDOR_PROMISE):
POST /obp/v7.0.0/banks/BANK_ID/accounts/ACCOUNT_ID/VIEW_ID/transaction-request-types/OPEN_CORRIDOR_PROMISE/transaction-requests - Attach Promise Evidence:
POST /obp/v7.0.0/banks/BANK_ID/accounts/ACCOUNT_ID/transaction-requests/TRANSACTION_REQUEST_ID/open-corridor/promise - Create Settlement:
POST /obp/v7.0.0/banks/BANK_ID/open-corridor/settlements - Get Settlement:
GET /obp/v7.0.0/banks/BANK_ID/open-corridor/settlements/SETTLEMENT_ID - Create Fee Settlement:
POST /obp/v7.0.0/banks/BANK_ID/open-corridor/fee-settlements