When a card payment appears in your processing dashboard but the deposit is missing from your bank, start by identifying the last step that the records actually confirm. A successful customer payment, an amount assigned to a payout, and a deposit visible at the bank are different observations.
Use the questions below to build one clear inquiry for the provider responsible for the payout. The aim is to replace “Where is my money?” with a specific amount, reference, expected date, and unanswered question. Your provider's account terms and actual records determine the answer; a general guide cannot establish why an individual payout is delayed.
1. Write down what you expected—and why
Record the expected deposit amount, currency, destination account's last four digits, and expected arrival date. Beside that date, identify its source: a dashboard estimate, a written funding schedule, or a support response. An assumption based on your previous deposit is worth recording, but label it as an assumption.
Ask your provider:
- Which sales or batch dates does this payout include?
- What cutoff time and time zone apply to those transactions?
- Is the displayed date a planned send date or an estimated bank arrival date?
- Does a holiday, account-specific review, or other exception change this particular payout?
For example, Adyen explains that payout assignment depends on the account's payout model and that clearing closures on bank holidays can affect payouts. That illustrates why a generic promise such as “next day” cannot diagnose an individual exception. Confirm the schedule for your own account. Adyen: Getting paid
2. Separate a missing payout from a different payout amount
Before opening a delay case, reconcile the amount you expected with the provider's payout report. Sales totals alone may not represent the deposit. In Adyen's documented process, payouts are net of items such as refunds, chargebacks, transaction costs, and other adjustments. Those are examples of entries to investigate, not a list of deductions that necessarily applies to your account. Adyen: Payout batches and reporting
Ask for the report that connects the relevant transactions to the payout reference. Adyen, for example, distinguishes transaction-level reconciliation from batch-level reconciliation that matches payouts to bank statements. Adyen: Settlement reconciliation
If the question is a line item rather than timing, use our merchant processing statement guide. If the provider identifies a reserve deduction, our rolling reserve guide explains the separate questions to ask about withholding and release terms.
3. Ask about the last confirmed stage
Copy the exact status shown in your provider's account. Do not translate “processed,” “paid,” or “deposited” into a conclusion without checking that provider's definition.
Shopify Payments, for example, says that a payout marked Deposited has been sent to the bank, but might not yet appear in the account. It recommends using the bank reference where available; it also cautions that not every bank uses that reference. These are Shopify-specific instructions, not universal status definitions. Shopify: Lower or missing payouts
| What your records show | The next question to ask |
|---|---|
| Payment recorded; no payout reference found | Which payout, if any, contains this transaction? |
| Payout listed with a future date | What does that date represent, and what remains before funds are sent? |
| Payout reported as sent; no matching deposit | What transfer reference and destination details can the provider confirm? |
| Payout reported as failed or returned | What reason was reported, and who must correct it before another attempt? |
| Account notice requests more information | Which specific request is outstanding, where should it be supplied, and how is completion confirmed? |
Treat this table as an inquiry tool. A status alone does not establish the cause or guarantee the next action will release funds.
If recurring payout questions are prompting you to review your broader account relationship, NUMUS can start a conversation about your processing needs. The provider handling the existing payout remains the source for that payout's status.
4. Keep one payout inquiry log
Use a separate row for each payout. Keep the evidence and open question together so that a handoff between support teams does not restart the investigation.
| Field | What to record |
|---|---|
| Merchant relationship | Provider and account reference used in its support system |
| Payout identity | Payout or batch ID, amount, and currency |
| Expected timing | Date, time zone, and the record supporting your expectation |
| Provider evidence | Exact status, when you checked it, and relevant report filename |
| Bank evidence | Whether a matching entry exists; account ending only in your shared summary |
| Open question | One unresolved fact, rather than an assumed cause |
| Next action | Responsible team, case number, and agreed follow-up date |
| Resolution | Confirmed outcome and supporting reference |
For a fictional example, imagine your dashboard lists payout EXAMPLE-104, USD 4,860, as sent, while your bank search finds no matching credit. Do not replace “sent” with “lost.” The open question is whether the bank can locate the transfer using the provider's reference and confirmed destination. Record the bank's response beside the provider's response before deciding what to ask next.
This log is your working record. Share supporting documents through the provider's approved channel, and include only the account information needed to investigate. Do not put full card numbers, passwords, or bank login credentials in a support summary or a general inquiry form.
5. Make the support request specific
Adapt this request to the records you have:
Please help reconcile payout [reference], for [amount and currency]. The account shows [exact status], checked at [date and time zone]. I expected arrival on [date] based on [schedule or message]. I have checked the destination account ending [last four digits] and cannot identify a matching entry. Please confirm the current payout stage, any transfer or return reference, any action required from us, and the next follow-up date. Our existing case number is [number, if applicable].
If the provider reports a failure, ask for the actual reason before changing account details or requesting another attempt. Shopify's failure guidance, for example, distinguishes incorrect bank details, unsupported account characteristics, and other rejection reasons. Its recovery steps depend on the failure reported. Follow your provider's instructions for your case. Shopify: Failed payouts
When a response is incomplete, identify the unanswered question and ask which team owns it. Keep the original case reference and a record of any agreed next step. Avoid creating several disconnected inquiries containing different amounts or dates.
6. Review the relationship after the exception is understood
A useful resolution records what happened, how you confirmed it, and whether your own reconciliation process needs to change. If the cause remains unresolved, keep that uncertainty explicit.
Separately, you may want to discuss your funding expectations, delivery model, or support needs when assessing future processing options. A new processing inquiry does not resolve or release an existing provider's payout. For businesses with a complex review history, our high-risk merchant account overview explains the starting point for a NUMUS conversation.
Bring a short description of your business and the processing questions you want to address. Use the initial intake to start that discussion, rather than submitting sensitive account records.
Sources are linked beside the relevant explanations. Read our editorial approach.