Sports / Casino
Your debit card connects to your ok ko account wallet alongside Nagad, Upay and Bank Transfer — giving you a familiar payment path whether you're funding a cricket bet or heading into the slot lobby.
A debit card at ok ko is one route into your account wallet — the same wallet you draw from when you place a cricket market, open a slot session, or sit at a live table.
Adding funds via debit card moves through your account wallet in a small number of steps. Each step is shown on screen as you go — no guesswork about where the transaction sits.
From your signed-in account, go to the wallet or deposit section. The card option appears alongside Nagad, Upay and Bank Transfer. Select it and the entry form loads — card number, expiry and security code fields displayed in order.
Fill in the card fields shown on screen. The form displays the currency as BDT and shows the amount field with any minimum or maximum limits your account tier carries. Read those figures before confirming — they come from your account, not from a fixed published rate.
Some card issuers route the transaction through an additional verification screen — a one-time code to your registered mobile number or a bank app prompt. The page holds open while this step completes and then returns you to the confirmation screen.
Once the bank confirms, your account wallet reflects the deposit and a transaction record appears in your history. Open that record to see the timestamp, BDT amount and status. If a step fails, the status message tells you the reason the issuer returned.
Transparency on deposits means your account history is the source of truth — not estimates or averages. Every debit card transaction creates a line item in your wallet history: the amount in BDT, the date, the method used and the outcome status.
All debit card deposits are recorded in BDT inside your ok ko wallet. The conversion, if any, is handled at the point your bank processes the charge — the amount credited to your wallet is the figure shown on the confirmation screen.
Approved, pending and declined are the three status states visible in your transaction history. A declined status includes the reason code returned by your card issuer, which helps you identify whether the block is from the bank's side or requires a different step.
Any fee applied to a debit card deposit is shown before you confirm the transaction — not deducted silently after. The displayed amount is what leaves your card; the credited amount to your wallet reflects whatever the terms for your account specify.
Full deposit terms — including limits, supported card types and processing notes — are in the help or terms section of your signed-in account. We keep these accessible from the payment page itself so you can check them without leaving the deposit flow.
If a debit card deposit stalls, the first step is checking your transaction history for a status code — that single line of information resolves most questions before you need to contact us. For issues that go beyond what the status code explains, we have support routes published inside the platform.
The live chat icon is visible from your signed-in account pages. Use it to share your transaction reference number and the status code you see in your history. The team can look up the deposit entry and advise on next steps without asking for full card details.
For a written record of your query, email support is available from the contact section inside your account. Include the transaction reference, the BDT amount and the date. Email is useful when your bank has given you a reference number of their own to include alongside.
The help centre inside your account covers debit card deposit steps, common bank decline reasons and what to do when a transaction shows as pending. Check it first — many card-specific questions have a step-by-step answer there without needing to open a support ticket.
We built the debit card deposit flow so the information you need — limits, status, fees, terms — is visible at each step rather than buried in a separate document.
Minimum and maximum deposit amounts for your account tier are shown on the card entry form before you submit. You see the figures that apply to your account specifically — not a generic published range that may not match your current verification level or region status.
Every deposit attempt — successful or declined — creates a permanent line in your wallet history. The reference number, BDT amount, method and status are all stored there. This record is what our support team and your bank both use to investigate any dispute.
If a card transaction fails at the bank level, Nagad, Upay and Bank Transfer are in the same payment panel — you switch without leaving the deposit screen. This keeps your session running and your account funded without starting over from the lobby.
The link to deposit terms is present on the payment page itself, not only in a footer you have to hunt for. Check accepted card types, any applicable fee tiers and the verification requirements before you enter your card details for the first time.
These are the terms that appear most often when you are moving through the debit card deposit flow. Understanding each one helps you act on the status messages and account fields without needing to open a separate query.
A unique code assigned to each deposit attempt. Your account history displays it alongside the BDT amount and status. Use this number when contacting support or your card issuer so both sides can locate the exact transaction without sharing card details.
A short code your card issuer returns when they block a transaction. Common reasons include international transaction restrictions, daily card limits or insufficient funds. The code appears in your transaction history so you can identify the cause before retrying.
A status showing the transaction has left your card but has not yet completed processing. It can appear during bank verification steps or at high-traffic times. Check your history again after a short wait — the status updates to approved or declined once the bank responds.
A security layer where your bank asks you to confirm the transaction via a code sent to your registered mobile or through your bank's app. The deposit page holds the session open while this step runs, then returns you to the confirmation screen.
BDT is the currency code for the Bangladeshi Taka. The deposit form displays your entry and the credited amount in BDT so the figure in your account wallet matches what you entered, subject to any fee terms applicable to your account tier.
The running total of funds available inside your ok ko account, fed by card deposits, Nagad transfers, Upay and Bank Transfer entries. Your wallet balance is what you draw from across cricket markets, slot sessions and live casino tables without needing to re-enter payment details.
These questions come up most often when you are setting up or troubleshooting a debit card deposit at ok ko. Each answer points to the specific screen or account section where you can confirm the detail for your own account.
Go to the deposit or wallet section while signed in. Select the card option from the payment panel — it sits alongside Nagad, Upay and Bank Transfer.
Your card issuer — not ok ko — controls approval. Common reasons: international transaction restrictions set on your card, a daily limit reached, or insufficient funds.
We do not publish a fixed processing time because it depends on your bank's response speed. Once your bank confirms the transaction, the status in your history updates and the BDT amount appears in your wallet.
Yes. Your ok ko wallet accepts deposits from multiple payment methods. You can fund via debit card one session and via Nagad or Upay the next — all entries appear in the same wallet history with
The fee — if any applies to your account tier — is shown on the deposit form before you confirm. It is not deducted silently after the transaction.
Access depends on your local law and the eligible regions confirmed during your account registration. The deposit panel shows the payment methods available to your account specifically.