There is a specific kind of frustration in this one. You have proof. You are looking at it. And the person on the other end is calmly telling you that nothing arrived.

The instinct is to assume somebody is being dishonest or incompetent. Usually neither is true. Two systems are showing two different things because they are measuring two different events, and the resolution is almost always procedural rather than adversarial.

How both sides can be right

A card payment is not one event. It is at least two, and they can be a long way apart.

The first is authorisation. Your card is checked, the amount is reserved, and your available balance drops. This is what you see, immediately, in your app. Nothing has actually moved.

The second is settlement, when the funds genuinely transfer. That happens later — hours, or a day, or longer over a weekend. Until settlement completes, the seller’s records may show nothing at all.

So there is a window, and it is not a short one, in which your app truthfully says the money is gone and the seller truthfully says it has not arrived. The mechanics of that gap are set out in full in a payment that is authorised but never settles.

"The money has left my account" and "we have received no payment" are not contradictory statements. They describe different moments in the same transaction, and the gap between them is where this entire argument lives.

The five reasons behind it

Beyond the timing gap, there are four other explanations, and they are worth knowing because each has a different fix.

Settlement has not completed. The common case. Time solves it. Nothing needs doing except waiting and, ideally, telling the seller the reference so they can look for it.

The payment reached a processor, not the seller. Where a third party sits in the middle, funds can be with the intermediary while the seller’s own dashboard shows nothing. This is more common than buyers realise, and who you are actually paying when a payment link comes from a processor explains the structure.

It is there but not matched to you. The money arrived and cannot be connected to your order, because the name differs, the reference was omitted, or the payment came from a household member’s card. The record exists; the link does not. Paying from a shared account creates exactly this, as paying from a shared or family account covers.

It failed, and the hold has not fallen away. The payment did not go through, but the reservation on your funds persists for a few days. Your balance looks lower. No money moved anywhere. This is the case where waiting is genuinely all you can do.

It went somewhere else entirely. The rarest and most serious: the payment was made through a page or an address that was not the seller’s. If the destination is not theirs, no amount of searching their records will find it. The warning signs are covered in signs a payment page is not the seller’s own.

Cause Clue What resolves it Typical time
Not yet settled Charge shows as pending Waiting, plus the reference Up to 1 working day
Held by a processor Descriptor names a company you do not recognise Seller checks the processor, not their bank Hours
Unmatched to your order Payer name differs from the account name Supplying amount, date and last four digits Minutes
Failed, hold still in place No confirmation was ever received The hold expires by itself A few business days
Sent elsewhere Payment page or address came from an unverified message Formal recourse through your payment route Weeks

What the seller is actually looking at

Understanding the other screen changes how you talk to the person in front of it.

A seller does not see your bank account. They see a list of received transactions, each with an amount, a timestamp, a partial card identifier, a reference and a status. They search that list. Your name may not appear on it at all, because the name attached to a card payment comes from the issuer and does not always match what you typed.

This is why "I paid on Tuesday, my name is such-and-such" so often produces "I cannot find anything". It is not obstruction. You have handed them a search key that does not exist in their data. What they can search on is a narrow set of fields, and what a seller can see about a payment that you cannot sets out exactly what is on that screen.

The screenshot that ends it

One image does more than twenty messages, and most people send the wrong one.

The wrong one is the account summary — a list of transactions with your balance across the top. It shows a line item and nothing that identifies the transaction to anybody else, and it exposes your balance for no reason.

The right one is the transaction detail view: tap into the individual payment. That screen normally carries the merchant descriptor as your bank recorded it, the exact date and time, the exact amount and currency, the status, and often a reference number. Those are precisely the fields the seller can search.

Cover your balance and your full card number before sending. Nothing else needs hiding — the descriptor and the reference are the useful parts, and obscuring them defeats the purpose. Screenshots that are worth something later goes through which captures carry weight and which are decorative.

The message to send

Six lines, in this order, and you will usually get an answer on the first reply.

The exact amount and the currency that actually left your account. The date and time. The payment method — card, wallet, or otherwise — and the last four digits if it was a card. The descriptor exactly as your statement renders it. The reference, if there is one. The email address or phone number you used when ordering.

Then one sentence saying what you are asking for: confirmation that it has been located, or confirmation that it has not, so you know which problem you have. Attach the transaction detail screenshot. Do not attach a photograph of the card.

The general discipline behind this — facts first, feelings never — is the same one that makes every payment query land well, and it is set out in what to send support so a payment problem is solved in one message.

Three things not to do

Do not pay again. This is the big one. A second payment does not replace the first, it joins it, and now somebody has to trace two transactions and refund one. It also muddies any later claim, since a duplicate-charge case and a missing-payment case are handled differently. The mess it creates is described in the cost of paying twice.

Do not open a formal dispute in the first hour. Once you do, an informal conversation becomes an adversarial process with a timetable, and the seller’s ability to fix it quickly often gets worse rather than better. Keep that route in reserve, where it is most useful.

Do not send anything unusual to make it go faster. A genuine seller solving a missing payment needs a reference, an amount and a date. Any request that escalates into full card details, a password, or a payment by a route with no way back should stop the conversation entirely. That line is drawn in what a legitimate payment request looks like.

How long to wait before escalating

A rough timetable that keeps you from either panicking early or drifting past a deadline.

First hour. Check your own confirmation first — a payment can succeed while the confirmation email lands in a spam folder, which produces exactly this argument from the other direction. Then send the details above.

Same day. Reasonable to expect an acknowledgement, even if the answer is "not visible on our side yet". Settlement timing is genuinely outside a seller’s control.

One working day. The payment should now be either found or definitively not found. If the seller still cannot see it, ask them to state that plainly, and ask your own bank whether the charge has settled or is still pending.

Two to three working days. If your bank confirms settlement and the seller confirms nothing arrived, one of the reasons in the table applies and you now have a real problem to escalate — with a clean record of having tried. What your bank will want at that point is set out in the evidence a bank asks for that nobody thinks to collect at the time.

What happens if this comes up here

Ordering runs through a conversation rather than a checkout, which changes the shape of this problem in a useful way: there is a message thread showing what was agreed and when, on both sides, before any money moved. Why there is no checkout button here explains why it is built that way.

If we say we cannot see a payment, we will say what we did check and when we checked it, rather than leaving you to guess. And access is not held hostage to a reconciliation problem that is ours to solve — if it is clear you have paid and the record is lagging, that is not your afternoon to spend.

The amounts to compare against are $69, $97 and $137 for one, two or three simultaneous screens, listed on the pricing page. One annual charge, no card kept on file, nothing renewing on its own — so a payment you do not recognise at all is worth a message rather than an assumption.

Send the amount, the date, the descriptor and the last four digits to WhatsApp, Telegram or support@pay-iptv.com, and you will get a straight answer about whether it is visible on this side.