Endpoint
POST /v3/charges/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
At least one identifier is required.Success data
details with txn_id, numeric txn_status, string amount and currency, payer/payee, merchant_order_id, numeric source_type, memo, credit_fee, and settlement_id. Only these mapper-populated fields are promised here.
Behavior and validation
This lookup remains POST and is bound to inbound flow plus the selected bank account. Party documents can be masked. A missing payment detail is returned as business code4003003.
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 identifiers are absent.4003003when no accessible transaction detail exists.500for a nil internal response,501for RPC transport failure, and4003008for missing account context.