Endpoint
GET{{baseURL}}/v1/transaction/{transactionId}
Request headers
| Header | Description | Required | Example |
|---|---|---|---|
x-api-key | Workspace API key for authentication. | ✅ Yes | YOUR_API_KEY |
Content-Type | Media type of the request. | ✅ Yes | application/json |
Request examples
Successful response
copy
Field reference
| Field | Type | Description |
|---|---|---|
data.id | String | Unique transaction identifier. |
data.state | String | Current processing state (e.g. PENDING, COMPLETED, FAILED). |
data.referenceNumber | String | meCash-generated reference for reconciliation. |
data.quote | Object | Quote snapshot used to execute the payout. |
data.recipient | Object | Beneficiary information used during disbursement. |
data.created | String | Timestamp (ISO 8601) when the transaction was created. |
data.processed | String | Timestamp for the latest state change. |
Error responses
| Status | Meaning | Example message | Next steps |
|---|---|---|---|
| 400 | Transaction not found or invalid ID. | Transaction does not exist | Confirm the identifier and ensure the payout was created successfully. |
| 401 | Authentication failed. | Invalid API key | Verify the x-api-key header. |
| 403 | IP not whitelisted. | Access denied: IP address not whitelisted | Add your server IP under Developers → IP Whitelisting. |
| 422 | Invalid parameter. | Invalid parameter | Check that the transactionId is a valid UUID. |
| 429 | Too many requests. | Too many requests | Add exponential backoff before retrying. |
| 500 | Server error. | Internal server error | Retry later or contact support if persistent. |
Usage tips
- Call this endpoint after receiving payout webhooks to verify the final state and amounts.
- Persist transaction responses for audit trails; they include the original quote snapshot.
- If the transaction remains
PROCESSINGfor longer than expected, reach out to support with thereferenceNumberfor investigation.

