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-Tenant-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.
Required idempotency key for safe retries. Use a UUID v4 or unique business identifier. If the same key is sent again and the original request was already processed, the cached response is returned.
See Retries and idempotency for details.
255The 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 response includes the X-Idempotency-Replayed header.
If the value is false, the transaction was just processed. If the value is true, the response is a replay of a previously processed request.
See Retries and idempotency for more details.
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 transfer status. For TED_OUT transfers, the status immediately after processing is always PROCESSING.
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
ID of the fee package applied to this transfer, if any.
"019c96a0-ad10-7fab-c1d2-3b4c5d6e7f8a"