Content
Dragon Tiger on kinich is a single-deal face-off between two hands labelled Dragon and Tiger. Each round uses one card per side, and the higher card wins according to standard rank rules. We explain the practical steps for joining a live table, how wagers and settles are presented in the live stream, and how we handle session visibility on mobile screens.
Step-by-step flow we recommend for a first session with kinich:
- Account creation: provide basic contact details and set a secure password.
- Identity verification: upload accepted ID documents and a selfie as part of KYC. We review submissions for compliance before live sessions are permitted.
- Funding: choose a local payment rail such as DANAe-walletor mobile banking where supported by law.
- Join a live table: select a Dragon Tiger studio in the live-casino lobby and tune mobile stream settings for bandwidth.
- Withdrawal request: submit required documents and await manual review as part of the withdrawal workflow.
We show how the table UI maps to each step. The table area includes a live video feed, current round ID, last-round history, and quick-bet options. On mobile, we provide low-data stream presets and a compact bet slip so the essential controls remain visible on smaller screens.
Core rules and common wagers explained in plain terms:
- Dragon vs Tiger — highest single card wins; card ranks follow standard order with Ace as low unless otherwise noted by the dealer.
- Tie — a third outcome; ties have distinct settlement treatment depending on the studio rules visible in the table information panel.
- Side bets and pairs — some tables offer side markets; we outline how they are displayed and how payouts are resolved in the studio info.
While the game is minimal in action, the security and verification layers are not. For kinich accounts we enforce electronic KYC, optional two-factor authenticator setup, and a documented password-reset process. The verification step is necessary before withdrawals are processed; we describe the typical documentation and the reviewer checklist below.
We prioritise clear verification paths and mobile-friendly streams so a single-card game remains transparent and auditable.
Verification checklist used by our review team for kinich withdrawal clearance:
- Photographic ID: national ID, passport, or driver licence.
- Selfie with timestamp matching the account holder.
- Bank account proof or e-wallet screenshot showing account name, used for settlement with rails such as local payment and online payment
Advantages
- Simple round structure for fast play
- Mobile-optimised streams and low-data presets
- Local payment support and common e-wallet rails
Limitations
- Outcome visibility depends on the live feed; connectivity may affect replay
- Withdrawals require completed verification and manual review
Local context: kinich users in Medan or Semarang often choose the nearest studio language stream where available and prefer e-wallet rails during public holidays such as Idul Fitri or Idul Adha when branch banking is limited. During major football events like Liga 1 or Piala AFF weekends, mobile traffic patterns change and we advise checking stream presets before joining a table.
On the operational side, our support pages document password reset flows, two-factor setup, and data-handling summaries. For users who need to verify an account after a deposit, we outline the documents required in the account area and provide in-app messaging to track a verification request.
Feature tour
The kinich live-casino lobby groups tables by game type and camera angle. Dragon Tiger rooms are presented with labels for speed tables, VIP tables, and multi-camera studios. Our mobile client reduces overlay elements for single-hand games to keep the video feed central and the bet slip accessible. We list supported payment rails in the funding section and display accepted methods prominently before a deposit attempt.
We link to related editorial pages about table etiquette, studio procedures, and how to read the round history. For users in Jakarta who prefer desktop checks, the same verification logic applies in the browser as on mobile; both paths use the same document-upload endpoints and reviewer queues.
We do not provide legal advice. Access and availability are governed by local regulation, and features appear only where permitted.