Use this endpoint to initiate a transfer by validating sender data, checking operating hours and usage limits, detecting duplicates, and calculating the fee. No funds are held at this step. The returned initiationId is valid for 24 hours and must be confirmed via the Process Transfer endpoint. Use the X-Idempotency-Key header for guaranteed deduplication.
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.
Client-provided idempotency key for guaranteed deduplication. Submitting the same key within 24 hours returns the cached response. UUID v4 format is recommended. When omitted, an automatic 60-second duplicate detection window is applied.
255The Midaz account ID of the sender.
"019c96a0-0c0c-7221-8cf3-13313fb60081"
The transfer amount in BRL.
0.01 <= x <= 999999.991000.5
A description of the transfer purpose.
140"Payment for services"
Custom metadata as key-value pairs.
{
"invoiceId": "INV-2024-001",
"orderId": "ORD-2024-123"
}Indicates that the transfer was initiated successfully and is awaiting confirmation.
The unique initiation ID. Use this value in the Process Transfer endpoint to confirm the transfer.
"019c96a0-aa10-7abc-d1e2-8c9d0e1f2a3b"
The calculated fee amount. Returns 0.00 if fees are disabled for this organization.
1.5
The total amount, calculated as the transfer amount plus the fee.
1002
The estimated time when the transfer will be completed.
"2026-02-01T18:00:00-03:00"
The time when this initiation expires, 24 hours after creation.
"2026-02-02T15:30:00-03:00"
The status of the initiation. PENDING_CONFIRMATION indicates the initiation is awaiting confirmation via the Process Transfer endpoint. PROCESSED indicates a transfer was created. EXPIRED indicates the initiation expired after 24 hours.
PENDING_CONFIRMATION, PROCESSED, EXPIRED "PENDING_CONFIRMATION"