Use this endpoint to confirm and execute a previously initiated transfer. The system validates the initiationId, checks the sender’s balance, holds funds in Midaz, and routes the transfer to JD SPB (for TED OUT) or creates an internal Midaz transaction (for P2P). Submitting the same initiationId returns the same transferId.
JWT Bearer token authentication. The token must include a tenantId claim that matches the X-Organization-Id header.
Organization ID used as the tenant identifier. All data is scoped to this organization. Must match the JWT tenantId claim when authentication is enabled.
The initiation ID returned by the Initiate Transfer endpoint. Expires after 24 hours.
"019c96a0-aa10-7abc-d1e2-8c9d0e1f2a3b"
Indicates that the transfer was confirmed and processing has started.
The unique transfer ID. Use this value to track the transfer status.
"019c96a0-ab10-7cde-f1a2-0e1f2a3b4c5d"
A human-readable confirmation number in YYYYMMDD+sequence format.
20"20260201001"
The current status of the transfer. For TED OUT and P2P transfers, the flow is CREATED, PENDING, PROCESSING, and then COMPLETED, REJECTED, or FAILED. Transfers can be CANCELLED while in CREATED or PENDING status. For TED IN transfers, the flow is RECEIVED and then COMPLETED or REJECTED.
CREATED, PENDING, PROCESSING, COMPLETED, REJECTED, FAILED, CANCELLED, RECEIVED "COMPLETED"
The fee amount as calculated during initiation.
1.5
The total amount held or transferred, including the fee.
1002