Declare an earlier leg of a Pix Automático payment the calling engine holds
Before the Courier takes over Pix, each engine declares the payments in flight whose earlier leg it already answered yes: the debit block (block) of every payment whose debit or reversal is still to come, and the schedule (schedule) of every schedule whose cancellation status is still to come. Those later legs then reach the caller. A later leg that arrived first is retained and is released by the Courier’s re-check once its leg is declared. A leg the Courier itself dispatched outranks any declaration unless its engine answered other than yes. 201: the leg now follows the caller. 204: it already did. 409 JDC-0116: the Courier’s record gives the leg to another engine, or holds the caller’s answer to the block that was not a yes; stop and report it to an operator. 422 JDC-0104: the leg or the endToEndId is not usable. 503: nothing may have been recorded; send the same declaration again, it is idempotent. The holder is always the caller.
Autorizaciones
Engines authenticate with an Access Manager application token.
- Token URL
- https://access-manager.example.com/oauth2/token
Parámetros de ruta
The payment's endToEndId as JD sent it.
block: the debit block a debit and its reversal follow. schedule: the schedule its cancellation status follows.
block, schedule Respuesta
Created

