The API will respond with a JSON object containing the transaction details and status.
Successful Response
{"requestSuccess":true,"transaction": {"id":"67299f9f617d20cb18b37640","status":"Pending","type":"Direct","fromChain":"8453","toChain":"8453","fromToken":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","toToken":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","fromAmount":"9992999","usdAmount":10,"sourceTransactionHash":"0x123...","destinationTransactionHash":"0x456...",// Relevant for Cross-chain transfers"createdAt":"2024-11-05T04:31:27.751Z","updatedAt":"2024-11-05T04:31:27.751Z" }}
Transaction Status Types
Status
Description
Pending
Transaction is being processed
Completed
Transaction has been successfully completed
Failed
Transaction has failed
Error Codes
Status Code
Error Type
Description
400
Bad Request
Missing required parameters
404
Not Found
Transaction not found
500
Internal Server Error
Server error
Example Error Response
{"success":false,"error":"error message"}
Error Handling
All timestamps are in ISO 8601 format
Transaction hashes are only present after the transaction is processed
The API uses rate limiting (100 requests per 15 minutes per IP)
For cross-chain transfers, both source and destination hashes may be present
For direct transfers, only sourceTransactionHash will be present when completed
For more information on error handling and response codes, please refer to our Error Handling documentation or get in contact with support@bindpay.xyz.