Scope of this guide
This guide explains Chicken Subway cash out terminology using general 100HP documentation. It does not confirm how a particular operator or client behaves. Visible controls, account rules and available options must be checked with the relevant operator. The provider documentation is an integration contract, not proof of a public play link, a Chicken Subway cash-out button, a payout method or a guaranteed result.
Three separate stages
A useful way to read a round is to separate in-game settlement, the account balance and a later cashier request. These stages may be related, but they are not the same record.
| Stage | What it means in the general documentation | What it does not prove |
|---|---|---|
| In-game settlement | A technical withdrawal debits the stake, while a technical deposit settles the round. A losing round can have a deposit amount of zero. | It does not prove that money was sent to a bank, card or e-wallet. |
| Account balance | The casino holds player balances and confirms transactions in the integration model. | A balance entry does not by itself confirm that a cashier request has been approved or paid. |
| Cashier withdrawal | A later request made through the operator's cashier is a separate transaction from the game result. | The documentation does not establish its method, eligibility, speed or outcome. |
Why the round record matters
Related round financial operations use a shared txID in the provider documentation. That identifier can help the operator connect the stake withdrawal and the later round settlement. A successful game result and a later cashier request should still be treated as different records rather than one automatic payout event.
A zero settlement amount can represent a losing round. It does not, on its own, demonstrate that a payment is missing. The general resolver flow looks for combinations such as a successful, non-demo stake withdrawal without a final deposit, while also considering repeated deposits, rollbacks and a configured age window. Those are reconciliation rules, not a promise of an automatic refund or a fixed resolution time.
Demo and free-bet records
The documentation distinguishes demo context from funded play. It also describes a free-bet mode in which bonus funds are used, the player's balance is not debited for the bet and only winnings are credited. That information does not establish whether a particular operator allows those winnings to be withdrawn.
Demo or mobile availability should not be assumed. The documentation lists unsupported demo, unsupported mobile version and hidden game settings among possible errors. Do not treat an integration flag or a technical session as proof of a public feature.
Evidence checklist for a disputed result
- Record the original round and txID, if the operator displays or can retrieve them.
- Note the date and time with the timezone, the stake, the play mode and the balance entries.
- Separate the game settlement from any later cashier withdrawal request.
- Ask the operator to reconcile the original round and transaction rather than requesting a new wager as a remedy.
- Keep messages and transaction references, but redact passwords, authentication codes and other private credentials.
- Do not assume that a rollback, retry or scheduled resolver stage guarantees a successful outcome.
Frequently asked questions
What does txID refer to?
In the general 100HP documentation, related round financial operations share a transaction identifier called txID.
Does a zero deposit always mean a technical error?
No. A zero deposit can be the settlement for a losing round and does not alone prove that a payment is missing.
Can free-bet winnings automatically be withdrawn?
The documentation does not establish withdrawability or promotional conditions for a particular operator, so the applicable operator rules must be checked.