Rollback - Cancel Bet
Cancel or rollback executed transactions, typically used for game cancellations or system exceptions.
Request Parameters
Request Before Decryption
{
"cipherText": "G0ZMDELeJwx+7JcIfIFOLJjkSzANPu6krGM2uw==..."
}
info
For encryption description, please refer to [Operator API Implementation Guide](./overview.md#1-Security Requirements)
Request After Decryption
{
"action": "rollback",
"uid": "test123",
"roundId": "AAA123",
"transferId": "AAA123",
"betId": "AAA123",
"brand": "VP",
"gameCode": "VP_230036_1"
}
| Parameter | Type | Required | Description |
|---|---|---|---|
| action | string | Yes | Fixed as "rollback" |
| uid | string | Yes | Player Account |
| roundId | string | Yes | Games Round Number of the original transaction |
| transferId | string | Yes | Identifier of the original transaction (expected to be removed) |
| betId | string | Yes | Bet ID, unique VP value |
| brand | string | Yes | Brand code, fixed as VP |
| gameCode | string | Yes | Game Code |
Response Format
info
Response is plaintext JSON, no encryption required.
Success Response
{
"status": "0000",
"errText": "",
"balance": 12345.67,
"responseTime": "2024-12-11T01:23:38.271Z"
}
| Field | Type | Description |
|---|---|---|
| status | string | Status Code, see Status Code Description below |
| errText | string | Error message, empty string on Success |
| balance | number | Player Balance after rollback |
| responseTime | string | Response Time |
Response Status and Transaction Result
| Status | Determine Cancellation Status | Whether to Trigger Retry | Is Cancellation Established | Bet Slip Status |
|---|---|---|---|---|
| 0000 | Success | No | Established | Canceled |
| 9999 | Failed | Yes | Not Established | Canceled |
| 1006 | Failed | Yes | Not Established | Canceled |
| 2000 | Failed | Yes | Not Established | Canceled |
| 2001 | Success | No | Established | Canceled |
| 2002 | Failed | Yes | Not Established | Canceled |
| 2003 | Success | No | Not Established | Established |
| Timeout | Failed | Yes | Not Established | Canceled |
Important Notes
- Transaction Cancellation Trigger Timing: When Bet response times out, this API will be called to cancel the transaction
- Processing Requirements: Upon receiving this API request, the specified Bet must be canceled and the updated Balance returned, or the Bet must be confirmed as established
- Retry Mechanism: If no clear error is received, retries will continue for four hours
- First hour, 1-minute interval per retry
- Next three hours, 10-minute interval per retry
- Status Description:
- Canceled: Transaction cancellation Success, not included in settlement
- Canceled: Transaction Status unclear, defaulted to unsuccessful transaction, not included in settlement
- Parameter Adjustment: transferId will be removed and replaced by betId