Endpoint
POST /v3/transfers/ted/bank-account
Authentication and target
Use an account credential for its bound account, or a user credential with bothX-ISPB and X-Account-Number. If an account credential sends those headers, both must be present and must match its bound account. Platform credentials are not accepted. All requests require the standard HMAC-SHA256 headers.
The curl example below uses an ACCOUNT credential bound to the operated account, so it omits X-ISPB and X-Account-Number. If X-Client-ID identifies a USER credential, add both target headers and include their exact trimmed values in the canonical header set before calculating X-Signature.
Request body
Use the same amount and payee fields as manual PIX. Optional numericpurpose is present in the HTTP contract but the current service does not copy it downstream. Optional currency is ignored; memo and merchant_order_id have no local format check on this route.
Success data
merchant_order_id, txn_id, and numeric txn_status; declared payer/payee fields are not populated.
Behavior and validation
The service sends a manual TED payment in BRL. Same-bank transfers are rejected after bank-code normalization. No endpoint-specific idempotency key exists.Errors
Every call can fail for missing or invalid signature headers, an expired timestamp, nonce replay, an invalid body hash or signature, insufficient permission, or a downstream service error. Endpoint-specific errors include:- Manual-transfer required-field, amount, and bank-code errors.
4001for a same-bank payee;4003014payment failure plus mapped provider errors.