31 August 2026 · 8 min read
How does a platform know a deposit arrived?
The most common message a new operator receives is that a deposit has not appeared. Understanding the path it takes turns that from an alarming message into a two minute check.
The path a deposit takes
- The user is shown an address or a payment page, ideally unique to them
- They send funds
- The transaction appears on the network or with the provider, unconfirmed
- Confirmations accumulate
- Your platform is told, or notices, that the payment is settled
- The balance is credited and the user is emailed
Every missing deposit is stuck at one of those six steps, and knowing which one is most of the answer.
How detection actually works
Two mechanisms, and platforms use one or both:
A callback: the payment provider sends your platform a message saying a payment happened. Fast, and dependent on a message arriving and being verified as genuine.
Polling: your platform periodically checks an address or an API for new payments. Slower, more robust, and it catches what a missed callback would have lost.
Software that relies only on callbacks will eventually lose a deposit, because messages get lost. Ask what happens when one never arrives, as set out in can you add a payment gateway after launch?
An admin controlled investment platform, installed and configured for you. Full admin control, live in 6 to 12 hours, from $149.
Why confirmations delay crediting
A transaction that has appeared is not necessarily final. Crediting immediately means crediting something that could still be replaced, and on a platform where the user can withdraw straight away, that is a real loss rather than a theoretical one.
The trade is simple: more confirmations is safer and slower. Whatever number you choose, show the user their progress toward it. A screen that says nothing during the wait produces the support message you were trying to avoid, which is the dashboard point made in what should an investor dashboard actually show?
The four places it goes wrong
| Problem | What happened | What to do |
|---|---|---|
| Still pending | Not enough confirmations yet | Show progress, wait |
| Callback lost | The message never arrived | Reconcile against the provider, credit with a reason |
| Wrong address | Sent to an old or shared address | Verify on the network, credit manually |
| Below minimum | Amount under your threshold | Decide a standing rule and apply it consistently |
Three of those four end with a manual balance adjustment, which is exactly why that control exists and why every adjustment needs a reason recorded. See how to manage user balances.
Answering the missing deposit message
A short routine that resolves nearly all of them:
- Ask for the transaction reference, not a screenshot
- Check it against the network or the provider dashboard
- If it is confirmed and not credited, credit it and write what you verified in the reason field
- If it is unconfirmed, tell the user the number of confirmations required and where to watch
- If it went to a wrong address, verify before doing anything, because this is the case people fake
What to check before buying
Ask whether each user gets a unique deposit address, how callbacks are verified, whether duplicates are detected, and what happens when a callback is never delivered.
Then ask to see the deposit list in the admin panel, with its confirmation counts. That screen is where you will spend your first week, and it is described alongside the rest in inside the admin panel.
Common questions
Why has my user deposit not appeared?
Usually one of four things: not enough confirmations yet, a callback that never arrived, a payment sent to the wrong address, or an amount below your minimum.
What is a confirmation and why wait for them?
A confirmation is a network acknowledgement that a transaction is settled. Crediting before enough of them risks crediting a payment that does not stick.
How many confirmations should I require?
It depends on the asset and on how much risk you accept. Higher is safer and slower, and the number should be visible to the user while they wait.
Should each user get a unique deposit address?
It makes matching payments to accounts automatic and removes most manual work. Shared addresses with a reference are workable and cause more support.
What if a deposit is sent to an old address?
It should still be creditable manually, which is one of the legitimate reasons for a balance adjustment with a reason recorded.
Can deposits be credited twice?
If callbacks are not deduplicated, yes, and it is a liability problem rather than a display bug. Ask the vendor how duplicates are handled.
Question this did not answer? Ask on Telegram. Reader questions get written up first.