Endpoint
POST /v3/transfers/details
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
Supplytxn_id or settlement_id; at least one is required. Optional merchant_order_id is forwarded downstream but does not by itself satisfy local validation.
Success data
details with the mapper-populated IDs, numeric txn_status and source_type, decimal-string amount/fees, currency, parties, memo, and rejection reason. Declared fields not assigned by the mapper can remain zero/empty/null.
Behavior and validation
The query is constrained to outbound flow and the selected account. Party documents may be masked by merchant configuration.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:4000when both transaction and settlement IDs are absent.4003003when no accessible details exist;4003008missing account context.501query RPC failure and500nil internal response.