Pay for anything online and two things tend to land in your inbox. The first is almost instant and says, in effect, we have your order. The second turns up a little later and is drier: a sum, a currency, a date, a reference, and the name of whoever is now holding your money.
Most people read the first and archive it. The second looks like admin, so it gets skimmed and forgotten. Months later, when something needs proving, the file that survives is the wrong one — and the difference between the two is not cosmetic.
Two documents, two different jobs
A confirmation is a status message. Its job is to reassure you in the moment: the order exists, here is what you asked for, here is roughly when to expect it. It is written for a customer, and it is generated by whatever system processes orders.
An invoice — or a receipt, depending on which side of the payment it was cut on — is a financial record. Its job is to describe a transfer of value between two identified parties. It is written for accounting, and it is generated by, or at least reconciled against, whatever system actually took the money.
That distinction explains why the two documents can both be perfectly accurate and still have wildly different value to you. One describes an intention. The other describes an event.
A confirmation tells you what was agreed. An invoice tells you what happened. When those two diverge — and a dispute exists precisely because they have diverged — only the second one is testimony.
What actually settles a dispute
It helps to understand what the other side is doing with your evidence. A card issuer, a wallet platform or a payments team is not reading your document for its story. They are trying to match it to a row in their own ledger.
That row already contains an amount, a date, a merchant identifier and a settlement reference. Their question is narrow: does the thing this customer sent me correspond to this row, and does it show something the row does not — that the service was never delivered, that it stopped, that it was not what was described?
A document that lets them make that match in seconds gets acted on. A document that forces them to guess gets a request for more information, which costs you a week. This is the same logic that governs what to send support so a payment problem is solved in one message: the winning move is always to hand over the identifiers the other side searches on.
So the practical answer is not "the invoice" in the abstract. It is: whichever of your documents carries the matching fields. Usually that is the invoice. Sometimes, on a well-built system, the confirmation carries them too and either will do.
The fields that carry weight
Rather than judging a document by its title, read it for six things. If they are all present, it is a strong document whatever it calls itself.
| Field | Why it matters | Typically on |
|---|---|---|
| Payee name, as it settles | Links your evidence to the entry on your statement | Invoice only |
| Amount and currency | The single figure the ledger row is keyed on | Both |
| Date money moved | Starts the clock on every dispute deadline | Invoice only |
| Order or transaction reference | What a support desk can look you up by instantly | Both |
| What was bought, in words | Supports a not-as-described claim, not just a non-delivery one | Confirmation usually, invoice sometimes |
| Period covered | Proves service was still owed when it stopped | Invoice, on annual plans |
The first row is the one people underestimate. The name money settles under is frequently not the brand name on the site, for entirely ordinary reasons — what the descriptor on your statement is telling you goes through why that mismatch is normal rather than sinister. But it does mean that a document naming only the brand leaves a gap between your paperwork and your bank's record, and closing that gap later is tedious.
The last row matters specifically on yearly plans. If a service stops in month seven, the claim is not "I was charged" — the charge was legitimate. The claim is that five months of a defined period were not delivered. Only a document stating the period supports that.
What each payment route asks you for
The route you paid by changes which document does the heavy lifting, because each system holds a different half of the story already.
Card. Your issuer already knows the amount, the date and the merchant identifier. What it does not know is what you were promised. So the document that adds value is the one describing the service and the period, and the correspondence showing you tried to resolve it directly first. The rules on what can actually be reversed are set out in chargebacks: what a card network will and will not reverse.
Wallet or payment platform. The platform holds the entire transaction record, so identification is trivial. The contested question is almost always coverage — whether the thing you bought falls inside the protection scheme at all, which for digital goods has real edges, mapped in what a PayPal dispute actually covers for digital goods. Your best evidence there is the description and the timeline, not the amount.
Cryptocurrency. There is no dispute process, because there is no intermediary. The chain proves a transfer occurred between two addresses and nothing else — not who controlled them, not what was owed. The finality is the method's defining property rather than a failure of yours, as covered in crypto payments: fast, cheap, and completely final. Documents here are for your own records and for arguing with the seller, not for reversing anything.
When only one of the two arrives
The common case is a confirmation with no invoice behind it. Usually it means nothing worse than a system that sends financial documents on a batch rather than instantly, or an address typed with a small error. Give it a working day.
If nothing has arrived after that, ask, and ask specifically. "I have not had a receipt" invites a resend of the confirmation you already have. "Please send a receipt showing the payee name, the amount, the date the payment was taken and the period covered" gets the document you actually need. The broader question of what ought to arrive, and what to do when it does not, is covered in the receipt you should get, and what to do when none arrives.
The rarer case is an invoice with no confirmation — you have proof money moved and nothing describing what it bought. That is worth resolving quickly, because it is the version that leaves you strong on the charge and weak on the promise. Ask for written confirmation of the plan, the number of simultaneous screens and the end date, and keep the reply.
A third possibility deserves a mention: neither has arrived and your balance has moved anyway. That is often not a completed payment at all but a hold, and it behaves quite differently — see a payment that is authorised but never settles before treating it as a missing receipt.
Timing: ask while the record is fresh
Documents are easiest to obtain in the first few weeks and progressively harder afterwards. Recent orders sit in the working set of whatever system holds them; older ones get archived, migrated, or fall behind a manual lookup.
There is a second timing issue that catches people out on annual subscriptions. The dispute windows that matter are counted in months, and several of them run from the end of the service period rather than the payment date — which means a yearly plan bought in January can still be disputable well into the following year. People assume the window shut long ago and never ask. It frequently has not.
The practical rule: request anything missing within the first month, and keep what you have until at least a few months past the end of the period you paid for. What else is worth retaining alongside it is set out in the paperwork worth keeping after you pay for a yearly service.
How to keep them so they are findable
Evidence you cannot locate is not evidence. Two habits cover nearly all of it, and neither takes longer than a minute at the time of purchase.
First, save the financial document as a file rather than leaving it in a mailbox. Mail accounts get migrated, filters get changed, providers close. A PDF in a folder named for the year outlives all of that.
Second, rename it so the useful fields are in the filename — the date, the payee as it settles, and the amount. That way the search that finds it is the same search you would run when a strange line appears on a statement, which is the moment you will actually be looking.
One thing not to do: never store card details alongside the paperwork. The document needs the last four digits at most. Anything more is a liability you have created for yourself, and no dispute process has ever required it.
What we send, and when
An order here is placed in chat rather than through a checkout, for reasons set out in why there is no checkout button on this site. That changes the packaging of these documents slightly, not their substance.
You get a written confirmation in the conversation, naming the plan and the number of simultaneous screens, and a receipt to your email carrying the amount, the currency, the date, the reference and the twelve-month period covered. Payment is annual and one-time — $69, $97 or $137 for one, two or three simultaneous screens, all published on the pricing page — so there is one document per year and no recurring charge behind it.
If the receipt has not arrived within a working day, ask on WhatsApp, Telegram or support@pay-iptv.com and say which fields you need on it. We would rather reissue a document than have a customer discover eight months later that the only thing they kept was a message saying thank you for your order.
