Result sources

Each of your own tables needs one result source (Results source in the Console) that sends round openings, the close of betting, the cards and the result to the platform; the platform checks the result against the cards and drawing rules and then settles. Choose it in Table → Table management → My tables when you add or edit a table. A table is linked to one source; if you are not ready yet, choose Not linked yet.

Source	Games	Set up first	Corrections and voids after settlement
Dealer tablet (card-reading shoe)	Baccarat, dragon tiger, Niu Niu, Texas Hold'em	Nothing; pair a tablet and set a supervisor PIN after creating the table	Applied automatically once the supervisor PIN is accepted
AI card vision (EWIN AI VISION)	Baccarat, dragon tiger	Enter your API key under AI card vision	Corrections (complete and passing the rules) and voids that arrive within 30 minutes of settlement are applied automatically; later ones leave the original result in place and mark the round disputed
RoadMapServer	Baccarat	Turn it on in System → Advanced features, then enter your API key under Signal sources	Same as above
elite API (your own pushes)	Baccarat, dragon tiger, Niu Niu	Turn on Accept pushes under Signal sources	Same as above

• The dealer tablet is a trusted source (trusted); the other three are standard. See Source trust levels in the GFI section.
• When a result source goes down the table stops taking bets immediately; a round that gets no result within 10 minutes of betting closing is voided and refunded automatically (see Round lifecycle).

Dealer tablet

The dealer tablet is a web app (a PWA you install to the home screen) provided by elite and shared by baccarat, dragon tiger, Niu Niu and Texas Hold'em. Pairing decides which table a tablet belongs to, and the tablet switches to that table's game by itself. It shows where the next card goes (for baccarat, whether the player or banker draws a third card or stands; for Niu Niu, which hand is dealt first once the first card is turned over). When the cards are out, the dealer checks that the table matches the screen and taps Confirm result. The platform works out the winner from the cards; the dealer never enters it. The tablet screens are available in Traditional Chinese, Simplified Chinese and English.

Installing

There is nothing to download from an app store: Table → Dealer tablet download in the Console lists the install URL and a QR code (one card per game; the app is the same). Use the URL the Console shows, for example:

https://elite.ewin888.com/Dealer/?install=1&game=baccarat

Device	How to install
Android tablet	Open the URL in Chrome or Edge (or scan the QR code) → tap Install on this device; if it is missing, open the ⋮ menu → Install app → from then on open the app from the home screen (full screen, landscape)
iPad	Open the URL in Safari → Share → Add to Home Screen → open the app from the home screen and pair inside the app (pairing done in Safari is not carried over)
Computer (serial card reader)	Open the URL in desktop Chrome or Edge → click Install on this device or the install icon in the address bar

• Recommended tablet setup: set auto-lock to "Never"; keep the tablet in the app with Guided Access (iPad) or screen pinning (Android); keep it on power and on a stable network.
• Dealer tablet download also has a Demo for each game: no pairing, a simulated shoe and card reader in the browser. It is useful for training dealers and does not affect any real table.

Pairing

1. In My tables, add or edit the table and set Results source to Dealer tablet (card-reading shoe). Texas Hold'em tables have no choice to make: they always use the dealer tablet.
2. Click the table's Tablet button → enter a name under Add tablet (for example "Studio A tablet 1") → Generate pairing code. The code has 8 characters, is shown only once and is valid for 10 minutes.
3. Enter the code in the app on the tablet, or scan the QR code in the pairing window with the tablet's camera (the code is filled in; then tap Pair).
4. The tablet remembers the table and connects straight away from then on.
5. If a tablet is lost or retired, click Revoke in the same window: that tablet can no longer control the table. Re-pair signs the tablet out and needs a new pairing code.

• Control and read-only: only one tablet controls a table at a time; other tablets are read-only. If the controlling tablet disconnects, the read-only tablet that connected first takes over; the same tablet reopening takes control back straight away.
• Tablet offline: no new round starts while no dealer tablet is online. On baccarat, dragon tiger and Niu Niu tables, 20 seconds without a controlling tablet stops betting and the lobby shows the signal as down; everything resumes when the tablet is back.
• Short outages (baccarat, dragon tiger, Niu Niu): scanned cards are queued on the tablet (up to 12 cards, for 2 minutes) and sent in order when it reconnects; for anything older the tablet asks the dealer to check the table and enter the cards manually.

Card readers

• Keyboard mode (HID, USB or Bluetooth): the reader types the card code followed by Enter, for example AS, 10H or KD. Works on Android, iPad and computers. The tablet also accepts common variants such as TH and Ah.
• Serial (Web Serial): desktop Chrome/Edge only. On the tablet, open Scanner → Connect scanner and choose the baud rate (9600–115200). iPads do not support serial readers.
• Cut card (baccarat, dragon tiger): a reader that reads the cut card sends CUT and the tablet records it; you can also use Shoe → Cut card out.
• While the tablet's Scanner window is open, scans are only tested, not sent — a simple way to check a reader.
• If scans do nothing: check that the reader is in keyboard mode and ends each code with Enter, and tap an empty area of the tablet screen so no input field has the focus.

Incidents and manual entry

These are the tablet actions for baccarat, dragon tiger and Niu Niu (Texas Hold'em is below):

Situation	On the tablet
No card reader	Enter every card with Enter card; it goes to the next position by default
The reader missed a card, so the next one landed in the wrong position	Undo last card → Enter card to add the actual cards in order
The reader misread a card	Undo last card → scan again or Enter card
A card is drawn while betting is open	Betting closes immediately and the tablet shows "Card drawn early: betting closed now"
One card too many is drawn	Put it on the discard pile; the round is not affected. If the camera showed it in a way that affects the round, use Void
A card is dropped, exposed or dealt to the wrong hand and cannot be fixed	Void: choose a reason and enter the supervisor PIN → every bet of the round is refunded in full
A misread is found after settlement	Correct → pick the round in Recent rounds → change the cards position by position and give a reason → supervisor PIN; the platform settles again from the new cards
A settled round must be voided	Correct → Void on that round in Recent rounds → reason and supervisor PIN; payouts are reversed and stakes returned

• Void reasons: extra card pulled, card dropped or exposed, scanner failure, misdeal, other (with optional details).
• Recent rounds covers the last 20 rounds on the tablet.
• Corrected bets come through with a new revision (rev); see Bet sync.

Supervisor PIN

• Set it with the table's PIN button in My tables. You can also set it when adding a baccarat, dragon tiger or Niu Niu table; it is required when adding a Texas Hold'em table. Use 4–8 digits and avoid repeated or sequential digits.
• The platform stores only a hash: if the PIN is forgotten, set a new one; you can also Clear PIN.
• Baccarat, dragon tiger, Niu Niu: voids and corrections need the supervisor PIN, and 5 wrong entries within 10 minutes lock it for 5 minutes. Texas Hold'em: Void hand needs the supervisor PIN.
• Without a PIN the tablet cannot void or correct, and the Results feed column in My tables shows No PIN set.

Tablet settings for the table

When a baccarat, dragon tiger or Niu Niu table uses the dealer tablet, the add/edit form has a Dealer tablet settings section:

Setting	Range (default)	Notes
Shortest / longest betting time (s)	5–120 (5, 60)	The dealer can pick a betting time within this range when starting a round; the table's betting time must fall inside it
Decks in shoe (baccarat, dragon tiger)	1–8 (8)	Lets the tablet check how many cards a shoe has produced
Burn cards (baccarat, dragon tiger)	On	After a new shoe, turn over the first card and burn as many more as its value (A = 1; 10, J, Q, K = 10)
Auto-confirm result (s)	0–30 (0)	Confirms automatically this many seconds after the last card (for Niu Niu, after all four hands are open); 0 = the dealer taps Confirm result
Auto-open hands (s, Niu Niu)	0–10 (0)	Opens the next hand automatically every so many seconds; 0 = one tap per hand
Auto-start next round (s)	0–60 (0)	Starts the next round this many seconds after confirming (the dealer can switch it off on the tablet); 0 = off

Status and log

In My tables, click the table's Tablet button:

• Tablets & status: the signal (normal or down), the current step, the shoe or session, the current and last round, whether a supervisor PIN is set, delivery of round events, and the tablets connected (controlling or read-only).
• Tablet log: every tablet action (raw scanner reads, manual entries, undos, reasons for voids and corrections, connections and takeovers) is kept for 30 days and can be filtered by round, for dispute reviews.

Both apply to baccarat, dragon tiger and Niu Niu; for Texas Hold'em, see whether the tablet is online and the current hand under Live in the Table workbench.

Texas Hold'em

• Texas Hold'em always uses the dealer tablet; there is no result source to choose. Every hand uses a new deck, and the tablet shows the seats in the hand, how many cards to deal, and what the next card is for (a seat, a burn card, the board, the dealer's cards).
• Hole cards of online seats are pushed into the lower collection tray and players see them as an animation. If the table allows on-site seats, the hole cards of guests at the table go straight to them, and the dealer registers their seating, bets and actions on the tablet.
• Void hand: choose a reason and enter the supervisor PIN. Player-vs-dealer tables refund in full; player-vs-player tables return everything put into the hand (blinds included).
• If the reader fails, use Pick card to enter the card.
• Pause: no new hand starts after the current one; Resume carries on.

AI card vision (EWIN AI VISION)

EWIN AI VISION reads the cards with IP cameras. It is a separate service: applications, pricing, camera and tablet setup and technical support are all handled by the AI VISION site (ai-gambling.ewin888.com). elite takes only AI VISION baccarat and dragon tiger tables.

1. Set up your tables in AI VISION and get an API key (it starts with sk_).
2. At the bottom of the Console menu, open AI card vision → Connect AI card vision: turn on Receive AI results, enter the API key and save. The key is verified with AI VISION when you save; only its last 4 characters are shown, and the AI tables in the account are listed.
3. In My tables, add or edit a baccarat or dragon tiger table, set Results source to AI card vision and pick an AI table under Source table. Each AI table can be linked to one elite table only.

• elite works out the result from the cards (in dragon tiger the ace is the lowest card).
• The countdown players see is the table's betting time; betting actually closes when AI VISION reports that betting has closed, or at once when the AI sees the first card. Keep the betting time the same as the countdown on the AI VISION dealer tablet (both default to 30 seconds).
• Use an AI VISION mode that has a betting countdown: detection-only mode has none, which leaves the table with no betting time.

RoadMapServer

RoadMapServer is an advanced feature, off by default, for operators who already have a RoadMapServer merchant account. It currently carries baccarat only.

1. System → Advanced features: turn RoadMapServer on (this needs back-office admin permission).
2. Table → Signal sources → RoadMapServer: turn on Receive round events, paste your RoadMapServer merchant API key and save. The key is verified when you save; only its last 4 characters are shown, and the tables it is authorised for are listed.
3. In My tables, add or edit a baccarat table, set Results source to RoadMapServer and pick the source table.

elite API push (GFI)

Studios that already run their own results system can push round openings, the close of betting, cards, results, corrections and voids through elite's standard data source interface, GFI. For your own tables you do not need to apply to the platform for a source; turn it on yourself in the Console:

1. Table → Signal sources → elite API (your own pushes): turn on Accept pushes. The first time, this creates a source ID (X-Source-Id, of the form api-<number>) and an HMAC key (starting with gfi_).
2. Only the Administrator role can show, copy or rotate (Generate new) the HMAC key, and only after two-factor verification within the last 30 minutes. After rotating, the old key stops working immediately and your pusher must sign with the new one.
3. In My tables, add or edit the table and set Results source to elite API (your own pushes). In your events, table is the table ID (for example B01, without the company code).
4. Push to the endpoints the Console lists (production shown below):

Purpose	Endpoint
WebSocket connection (recommended)	wss://elite-ingest.ewin888.com/ingest/v1/stream
HTTPS batch push	POST https://elite-ingest.ewin888.com/ingest/v1/events
Format check (not applied)	POST https://elite-ingest.ewin888.com/ingest/v1/validate

• For signing, event formats, reliability and error codes see Data source interface (GFI), Events & data model and Reliability, health & errors; before going live you can check your events with the GFI event validator.
• Supports baccarat, dragon tiger and Niu Niu (GFI v1 has no Texas Hold'em).
• Signal sources shows the status of this source and when it Last received an event.
• With Accept pushes turned off, every push is rejected (SOURCE_DISABLED).

Abnormal rounds on your own tables

The Abnormal round panel at the top of My tables lists problems on your own tables: rounds without a result, results that fail the checks, corrections or voids after settlement that fall outside the guardrails (disputed rounds), and different results for the same revision. The platform does not handle abnormal rounds on your own tables; you decide:

• Void and refund now: only for rounds that have not been settled; every bet of the round is refunded.
• Mark handled: a disputed round keeps its original result.

Nothing gets stuck if you do nothing: rounds without a result or with failed checks are voided and refunded automatically when they time out, corrections outside the guardrails leave the original result in place, and everything is closed automatically after 24 hours.