Retrieves the current status and details of a transaction.
Returns the real-time status, financial details, compliance information, and tracking data for a specific transaction.
Use this endpoint to:
- Check the current processing status of a transaction
- Retrieve hold information and compliance requirements
- Get the transaction tracking URL
- Monitor transaction lifecycle (creation, confirmation, payment, cancellation)
- Check which required documents have been fulfilled or are still pending
- Validates the transaction exists
- Retrieves real-time transaction status
- Checks fulfillment status of each required document
- Returns status, holds, compliance requirements with fulfillment status, and financial details
Requires x-client-id and x-secret-key headers.
- The
required_document_listfield indicates what compliance documents are needed (e.g., KYC, ID, SSN). - The
document_requirementsfield provides the detailed fulfillment status for each required document, showing whether it has been completed or is still pending. - Hold information includes active holds that may be blocking the transaction.
400Missing or invalid UUID401Invalid credentials404Transaction not found500Internal error
Unique identifier assigned to the integrating client. It determines the validation rules, allowed values, compliance policies, and operational limits applied to the request.
Error codes: required=400001, type=400002, minLength=400003, maxLength=400004
curl -i -X GET \
'https://sandbox-viablocks.viamericas.io/transaction/status?uuid=string' \
-H 'x-client-id: string' \
-H 'x-secret-key: string'Response success
Internal transaction identifier in the format {branchId}-{receiverId} (e.g., I00123-456789).
Date and time when the transaction was created. Format: MM/DD/YYYY HH:MM:SS AM/PM (US Eastern time).
Transaction status
| Status | Description |
|---|---|
| VOID | The transaction has been voided and is no longer valid. |
| CANCEL | The transaction was cancelled before completion. |
| EXPIRED | The transaction was not completed within the allowed time window and has expired. |
| HOLD | The transaction is temporarily on hold due to compliance or operational review. |
| DONE | The transaction has completed its internal processing flow successfully. |
| SENDTOBANK | The transaction has been sent to the bank for processing. |
| PAID | The funds have been paid out to the beneficiary. |
| TRANSFERED | The funds have been transferred to the payout network or external institution. |
ISO currency code of the source (sending) amount. Represents the currency in which the sender funds the transaction.
Total amount in destination currency that the customer is sending (including fees applied to delivery).
ISO currency code of the destination (receiving) amount. Represents the currency in which the beneficiary will receive the funds.
List of compliance or operational holds applied to the transaction.
Each hold represents a restriction or review requirement that must be resolved before the transaction can proceed.
List of documents required to resolve compliance or regulatory requirements for the transaction.
This list is typically populated when the transaction requires additional verification or is placed on hold.
Detailed real-time status of each required document. Use this field to:
- Show the user which requirements are complete and which need action
- Determine if a document is under review (no action needed, wait)
- Detect rejections or expirations that require re-submission
Each object contains:
type: The compliance requirement code (matches items inrequired_document_list)fulfilled:trueif no further action is needed for this requirement,falseif action is requiredstatus: Detailed lifecycle status of the requirement
Possible status values:
| Status | Meaning | User Action |
|---|---|---|
completed | Requirement fully satisfied and approved | None |
pending | Not yet submitted — upload/submit required | Submit via PUT /transaction/update |
in_review | Document uploaded, awaiting approval | Wait — do not re-submit |
rejected | Document was reviewed and rejected | Re-submit with corrected document |
expired | Document was valid but has expired | Re-submit with current document |
Payment rail used for the transaction (e.g., ACH, RTP, FEDNOW). Null if not applicable or not yet determined.
Estimated date when the funds will be available to the beneficiary. Null if not applicable or not yet determined. Format: MM/DD/YYYY or ISO 8601 depending on the payout network.
Date when the transaction was paid out to the beneficiary. Null if the transaction has not been paid yet. Format: MM/DD/YYYY HH:MM:SS AM/PM (US Eastern time).
Date when the funds were transferred to the payout network or external institution. Null if the transaction has not been transferred yet. Format: MM/DD/YYYY HH:MM:SS AM/PM (US Eastern time).
- HOLD — Transaction on hold with pending compliance documents
- Transaction with rejected ID — re-upload needed
- Transaction with all required documents fulfilled
- SENDTOBANK — Transaction sent to bank for processing
- TRANSFERED — Funds transferred to payout network
- PAID — Funds paid out to the beneficiary
- ID uploaded and under review — no action needed
- ID expired — re-upload needed
- New transaction — all documents pending
- CANCEL — Transaction cancelled before completion
- VOID — Transaction voided and no longer valid
- EXPIRED — Transaction expired due to time limit
{ "transaction_uuid": "xxxxx-xxxx-xxxx-xxxx-xxxxx", "transaction_id": "I00123-456789", "status_track_url": "https://status-track.viamericas.io/?token=xxxxx-xxxx-xxxx-xxxx-xxxxx", "date_created": "07/27/2026 01:45:19 PM", "status": "HOLD", "folio": "1234567890", "source_currency_amount": 84000, "source_currency_iso": "MXN", "total_receiver": 84000, "total_pay_receiver": 4662, "currency_receiver_iso": "USD", "rate": 0.0555, "holds": [ { … }, { … } ], "required_document_list": [ "Copy1ID", "DOB", "ID", "KYC" ], "document_requirements": [ { … }, { … }, { … }, { … } ], "payment_rail": null, "date_available": null, "date_payment": null, "date_transfer": null, "date_cancel": null }