If a prediction market deposit is missing, first identify the funding method and the last event you can prove. A bank debit, card authorization, or blockchain confirmation shows progress on one rail; none alone proves that the prediction-market ledger credited your account.

Key Takeaways

Separate initiation, authorization, settlement, platform credit, failure, and return.

Read the status for the exact bank, card, or crypto method you used.

Preserve the request ID, time zone, amount, currency, destination, and rail reference.

Do not repeat an unresolved deposit or pay an off-platform recovery fee.

Escalate with redacted evidence, never passwords, codes, or wallet secrets.

Which deposit event can you prove?

Start with the platform's Transfers or Funding page rather than the total balance. Reconcile the external payment record with the venue ledger and use one time zone throughout.

Stage	Evidence to preserve	What it does not prove
Initiated	Request ID, amount, method, timestamp	The provider accepted it
Authorized	Card or bank pending entry	Money finally moved
Sent	Bank reference or transaction hash	The venue credited it
Settled	Final rail status	The correct account ledger updated
Credited	Venue ledger entry	Funds are immediately withdrawable
Failed or returned	Reason, reversal, return credit	The original cause is fixed

Kalshi's named bank-deposit documentation distinguishes an initiated transfer, partial provisional credit, bank settlement, and later withdrawal availability. It also warns that a failed or returned transfer can remove provisional credit and create a negative balance.［1］ Those states illustrate why a balance shown early is not the same as final settlement.

How should you check a prediction market bank deposit?

Confirm that the funding request exists in the authenticated account. Compare its amount, currency, originating bank suffix, legal account name, initiation time, and status with the bank record. Do not infer a final debit from a pending bank entry.

Bank transfers operate on method- and region-specific schedules. Kalshi describes ACH partners, same-name account requirements, settlement before full availability, and returned-transfer behavior for its service.［1］ Apply only the instructions displayed for your venue, country, and account.

If the bank shows a final debit but the venue has no matching credit, ask venue support whether it accepted the request and which processor or bank reference identifies it. Ask the bank whether the debit settled, reversed, or remains pending. Keep each institution's case number in one chronology.

What should you check for a prediction market card deposit?

A card authorization can appear even when the deposit was declined. Kalshi explains that a failed card attempt may leave a temporary pending or refunded entry at the bank without moving funds into the prediction account.［2］ Treat the final card posting and the venue ledger as separate records.

Verify the cardholder name, billing details, amount, card suffix, authentication result, and platform status. Never send a full card number, security code, password, or one-time code to support. Use screenshots with unrelated balances and personal details redacted.

Do not retry merely because the bank app shows a pending authorization. A duplicate attempt can create another hold or a second successful deposit. Wait for the documented state or obtain a clear response from the bank or venue before deciding whether a new request is safe.

How is a crypto deposit different?

For a crypto-funded prediction account, record the asset, network, destination address, memo or tag where required, transaction hash, sent amount, fee, and confirmation state. A confirmed blockchain transaction proves delivery to an address on a network, not necessarily conversion or credit to the correct venue profile.

Kalshi's crypto-deposit guide tells users to select a supported asset and network and to retain the transaction hash for support.［3］ If the asset, network, or destination differs from the authenticated instruction, stop retrying and use the venue's official recovery route. Never share a seed phrase or private key.

If the on-chain transaction itself is pending, use the crypto deposit and confirmation guidance to distinguish network confirmation from platform credit. Keep this article focused on the prediction-market funding record.

Could the balance be present but unavailable?

Some venues display provisional buying power before a bank transfer fully settles, while keeping the amount unavailable for withdrawal. A returned deposit can later reduce that balance. Open positions, reserved orders, security holds, or a negative balance may also make the headline total differ from usable cash.

Reconcile ledger categories instead of adding unrelated figures. Record deposited cash, provisional credit, settled cash, reserved funds, open-position collateral, returns, fees, and withdrawable balance separately. Do not describe a hold as missing money when the ledger identifies it.

How should you escalate it when a prediction market deposit is missing?

Build one redacted evidence package:

Record the venue request ID, exact method, amount, currency, and timestamp with time zone.
Save the complete venue status history and any error or return notice.
Add the bank/card reference or crypto transaction hash appropriate to the rail.
Show the destination using only the masked account, card suffix, or safely truncated address.
State the expected ledger entry, observed ledger entry, and last known correct time.
List existing case numbers and the precise question each institution must answer.

Kalshi's transfer FAQ separates troubleshooting by debit, bank, wire, and crypto methods, including name, authentication, memo, issuer, and supported-asset checks.［4］ That is a useful evidence model, but another venue may use different providers and rules.

Contact the venue first when no accepted funding record exists or it cannot identify the handoff. Contact the bank, card issuer, or transfer provider when the venue supplies a reference that the receiving system can trace. If records conflict after the published process, use the venue's formal complaint route and seek qualified advice where material rights or deadlines are involved.

What should you avoid while investigating?

Do not send another deposit to “unlock” the first, pay a personal wallet, install remote-control software, or trust an unsolicited recovery agent. Do not alter account identity, apparent location, or payment details to bypass a restriction. Secure the account through the online security guide if the request, destination, or support conversation is unfamiliar.

Do not delete the original confirmation after making a redacted copy. Preserve the unedited evidence privately and share only what the authenticated support case requests.

How can you keep the evidence consistent?

Use a small reconciliation sheet with one row per event. Copy identifiers exactly, retain the original currency, and write both the displayed time and its time zone. If the bank and venue use different dates, convert them only in a separate comparison column so the source records remain intact.

Mark each statement as observed, supplied by support, or inferred. For example, “bank entry posted” is an observation, while “the processor lost it” is an inference unless a responsible institution confirms that event. This distinction helps support investigate without first correcting assumptions.

Keep changes to the account in the same timeline. A relinked bank, replaced card, corrected profile, or new crypto address can explain why later instructions differ, but it must not overwrite the destination used for the original request. Preserve the original and current values in masked form.

Summary

Identify the exact funding rail and last provable state.
Compare the external payment record with the prediction-market ledger.
Distinguish provisional credit, settlement, usable cash, failure, and return.
Avoid duplicate attempts until the first request has a clear outcome.
Escalate with a redacted chronology and rail-specific reference.

Frequently Asked Questions

Why did my bank balance fall while the prediction account shows nothing?

The bank entry may still be pending, or the venue may be processing, rejecting, or returning the transfer. Confirm the final bank state and obtain the venue request or processor reference.

Does a card authorization mean the deposit succeeded?

No. An authorization can remain after a failed attempt. Compare the final card posting with the venue ledger and status.

Does a blockchain confirmation guarantee platform credit?

No. It proves an on-chain transaction reached an address on a network. Asset support, network, destination, memo, conversion, and account assignment still matter.

Should I submit the deposit again?

Not while the first request can still settle or return. A second attempt can create another hold or duplicate funding.

Why can I trade but not withdraw the deposited amount?

The venue may have provided provisional buying power while the original funding remains unsettled or subject to a security hold. Read the account's ledger and availability date.

Which reference should I give support?

Use the identifier for the actual rail: venue request ID plus a bank reference, card transaction reference, wire memo, or blockchain transaction hash.

Can a VPN make the venue credit the deposit?

No. A VPN cannot change a bank, card, blockchain, processor, or venue ledger or release a funding hold.

When should I use a formal complaint route?

Use it when the provider's stated process has passed or the institutions cannot reconcile material evidence. Preserve all records and obtain qualified advice where needed.

Disclaimer: This article provides general information, not financial, investment, legal, or individualized platform advice. Funding methods, eligibility, timing, holds, fees, complaint rights, and remedies vary by venue, provider, country, and current terms.

Sources:

Kalshi — Bank Deposits — https://help.kalshi.com/en/articles/13823798-bank-deposits
Kalshi — Card Deposits — https://help.kalshi.com/en/articles/13823795-card-deposits
Kalshi — Crypto Deposits — https://help.kalshi.com/en/articles/13823799-crypto-deposits
Kalshi — Transfers FAQ — https://help.kalshi.com/en/articles/13823791-transfers-faq

Sources checked 12 September 2026.

Related articles:

Prediction Market Deposit Is Missing: What to Check