Resolve Timed Out TX
โ Command 31 โ Mark a Timed-Out Transaction as Resolved
This endpoint is used to manually mark a timed-out or reattempted transaction as resolved, ensuring that RGS-CWS does not retry or cancel it again.
Use this function when your system has already processed a transaction outside the standard flow, and you want to prevent additional retries from our server.
๐ Sample JSON Request (from your server to the RGS-CWS server)
{ "command": "resolvetx", "original_uniqid": "TX123456abcdef" , "apiusername": "aaaaaa" , "apipass": "qwrqwrq" }๐ Note: All field names and values are case-sensitive.
๐ฅ Input Parameters
You must send either
loginoruserid, not both.
๐ Sample JSON Responses (from RGS-CWS)
โ Success:
{ "status": "OK" }โ Failure (e.g., invalid input):
{ "status": "ERROR", "message": "You cannot cancel" }๐ค Output Parameters
โ Operator Notes
This is a manual override tool โ only use it after your platform has confirmed that the transaction is finalized.
Particularly useful when your system processed a transaction late (e.g., via cronjob) and you want to avoid retry or cancellation from RGS-CWS.
Always retrieve the original
uniqidvia Command 27 (List TimedOut Bets) or Command 28 (List TimedOut Wins).Use this command if you are not relying on automatic cancel mechanisms (cronjobs set by RGS-CWS) and want to take full control of transaction finalization.