/v2/transactions/details/{transactionNumber}Get Transaction Details
Returns details for a transaction by transaction number (from a payment or transfer response). This is the authoritative view of a transaction — use it to confirm state rather than relying on webhook arrival order.
**`Status` values:**
| Status | Meaning | | --- | --- | | `PENDING_AUTHORIZATION` | Created and awaiting authorization. Every payment starts here | | `AUTHORIZED` | Authorization granted; queued for execution | | `IN_PROCESS` | Submitted to the payment rail | | `COMPLETE` | Settled | | `COMPLIANCE_REVIEW` | Held for compliance review | | `DENIED_AUTHORIZATION` | Authorization refused | | `CANCELLED` | Cancelled before execution | | `EXPIRED` | Authorization window lapsed without a decision | | `FAILED` | Execution failed | | `CHARGED_BACK` | Funds returned or reversed after execution |
Treat only `COMPLETE` as settled. `DENIED_AUTHORIZATION`, `CANCELLED`, `EXPIRED`, `FAILED`, and `CHARGED_BACK` are terminal-negative.
Path variables
| Field | Type | Required | Possible values | Description |
|---|---|---|---|---|
transactionNumber | string | Required | {transactionNumber} | Transaction reference from a payment or transfer response (e.g. FV000006187, FVBTC000007938). |
Headers
| Field | Type | Required | Possible values | Description |
|---|---|---|---|---|
Authorization | string | Required | Bearer {SessionToken} | Session token from Get Session Token, sent as `Authorization: Bearer {SessionToken}`. Replace with the value from the `x-refresh-token` response header when present (typically within 2 minutes of expiry). Secured calls must use the same IP as the auth request. |
Response
| Field | Type | Possible values | Description |
|---|---|---|---|
ResponseCode | integer | 200 | 201 | 204 | 400 | 401 | 403 | 404 | 410 | 422 | 500 | 301 | 503 | 422 | API result code in the response envelope. Indicates success or the error category (e.g. 200 success, 400 bad request, 401 unauthorized). |
ResponseMessage | string | Success | Created | NoContent | BadRequest | Unauthorized | Forbidden | NotFound | Gone | UnprocessableContent | ServerError | ResourceMoved | ServiceUnAvailable | UnProcessableEntity | Human-readable label paired with ResponseCode (e.g. Success, BadRequest, Unauthorized). Use with ResponseCode to interpret the outcome. |
ResponseData | object | Please refer to below example for response body | Full transaction details (status, amount, parties, type, timestamps). |
Example response
{
"ResponseCode": 200,
"ResponseMessage": "Success",
"ResponseData": {
"TransactionNumber": "FV000006187",
"Status": "DENIED_AUTHORIZATION",
"CreatedAt": "2022-09-09T07:42:43.730-04:00",
"Amount": "1.00",
"From": "Rishav_Business - Rishav",
"To": "Rishav_test",
"Currency": "USD",
"Description": "Testing",
…Requires `Authorization: Bearer {SessionToken}` from Get Session Token. Refresh via `x-refresh-token` when supplied; use the same client IP as authentication.