People imagine a payment dispute as an argument. It is not. It is a filing exercise.
Somewhere in a bank, a person who was not present when anything happened reads a file. On one side is your account of what you were promised. On the other is whatever the seller submits. The rules that decide it are not about fairness in the abstract; they are about which category the claim falls into, and whether the file contains anything supporting it.
That is the whole difficulty. The material that wins a case is generated in the first hour after paying, at a moment when nothing has gone wrong and collecting evidence feels absurd. By the time it is obviously needed, several pieces of it no longer exist.
Why the case turns on documents
A dispute reviewer is not deciding whether you are honest. They are deciding which of a short list of situations this is, and each one has different requirements.
Was the transaction authorised by you? Was the thing described actually delivered? Was what arrived materially different from what was sold? Was it cancelled and charged anyway? Different categories, different evidence, different outcomes.
You do not usually get to argue the category. It is inferred from your documents. A claim that says "it stopped working" with nothing attached tends to be read as a quality complaint, which is the weakest available framing. The same facts with a dated capture of what was promised and a dated record of what arrived becomes "not as described", which is a much stronger one — the distinction drawn out in what a card network will and will not reverse.
Nobody loses a dispute for lying. People lose disputes for having nothing to attach.
The seven items a bank asks for
The exact wording differs between banks, but the list is remarkably consistent. Seven things, and you can have all of them.
| Item | Why it is asked for | Still available in 3 months? |
|---|---|---|
| The transaction detail — date, amount, currency, descriptor | Identifies the payment being disputed | Yes, on your statement |
| The seller’s confirmation or invoice | Shows what the payment was for | Usually, if it came by email |
| The description of what you bought, as advertised | Establishes what was promised | No — the page can change |
| Evidence of what was delivered, or that nothing was | Establishes the gap | Rarely, unless captured |
| Your attempt to resolve it with the seller | Shows the direct route was tried | Only if you keep the thread |
| The seller’s reply, or proof there was none | Justifies escalating | Only if you keep the thread |
| The terms that applied at the time of purchase | Decides what was actually agreed | No — terms are edited silently |
Look at the right-hand column. Four of the seven depend on you having done something, and three of those four are impossible to recreate later. That is the entire problem in one table.
The three that stop existing
Some evidence is durable because a third party keeps it for their own reasons. Some of it evaporates, and it is worth knowing which is which.
The advertised description. A web page is not a fixed object. It is whatever the seller is serving today. A page describing a service in one way in January can describe it differently in March, with no record of the change and no way for you to prove which version you read. Nothing about the internet preserves that for you.
The chat thread. On a purchase arranged through a messaging app, the thread is the contract. It is also, on several platforms, editable, deletable and capable of disappearing entirely when an account changes. A message you read on Tuesday may not exist in that form on Friday, and if the account is gone the whole history goes with it.
The terms. Terms and conditions are edited routinely, usually without a version history a customer can see. The clause you agreed to is the one that was live at the moment you paid, but demonstrating what that said is your problem, not the seller's — one reason reading a subscription's terms before the money moves is worth the ten minutes.
Everything else on the list is durable. Your statement is kept by your bank. An emailed receipt sits in your mailbox. Those are the parts people do keep, and they prove the least, because the fact that a payment happened is almost never what is in dispute.
The document nobody keeps
If you take one habit from this, take this one. Before you pay, capture what you are being sold, in the seller's words.
Not your summary of it. Their description: the plan, what is included, how many devices, how long it runs, what happens at renewal, what support is offered. A screenshot of the page or the message, with the date visible somewhere in the frame.
This is the only document that answers the question every non-trivial dispute turns on: what was this money supposed to buy? A receipt proves a payment. A statement proves a payment. Only this proves the promise, and it is the one item nobody has, because taking it feels like anticipating a fight you have no reason to expect.
It costs about twenty seconds. If the purchase is arranged in a chat, the equivalent is asking the seller to state the package and its duration in one message, so a single clean screenshot contains the whole agreement — the approach in what a legitimate payment request looks like, line by line.
Why a screenshot beats a link
People submit links. It feels tidier and it is nearly worthless.
A link points at a page under the seller's control. What a reviewer sees when they open it is whatever is there on the day they open it, which may not be what you read when you paid. If the page has changed, the link now argues against you. If the page is gone, it argues nothing.
A capture is different. It is a fixed record of a specific claim on a specific date, and its evidential weight does not decay when someone edits a page. Four rules make one useful:
Capture the whole frame. The address bar, the account name, the timestamps. A cropped fragment showing one sentence is easy to dismiss and impossible to place in time.
Keep it legible. A reviewer reading forty low-resolution images on a small screen will skim. One clear capture per point beats a folder of them.
Prefer an export where one exists. Most messaging apps can export a conversation as a file. That is easier to read than a stack of images and harder to accuse of selective cropping.
Store it somewhere that is not the device that took it. Evidence on one phone is one dropped phone away from not existing, alongside the rest of the paperwork worth keeping after you pay for a yearly service.
The four-minute routine on the day you pay
Here is the whole thing, done once, on the day. It is short enough that there is no real argument against it.
Before paying. Capture the description of what you are buying and the terms in force. Two screenshots. If the deal was agreed in a chat, ask for the package and duration in one message first, then capture that.
Immediately after paying. Capture the payment confirmation and, once it lands, the delivery message — credentials, activation, whatever arrives. Note the time. The gap between those two is itself evidence if delivery later becomes the argument, which is why the confirmation versus the invoice matters more than it sounds.
Within a week. Check your statement and capture the line, including the descriptor and the amount as charged. On a foreign purchase the amount may differ from the price you were quoted, and knowing why is easier now than in four months — see the quiet surcharge on a yearly subscription.
Put it in one place. One folder, named for the seller and the date. Not scattered across a camera roll, a downloads folder and three chat apps. A file you cannot assemble under pressure is not evidence.
What each payment route asks for
The list above covers every route. What changes is who reads it and how much weight each item carries.
Card. The most structured process and the most document-driven. Your bank builds a file, the seller responds, and the network's rules decide. Categories matter enormously here, which is why the description-of-what-was-promised item does disproportionate work.
Wallet payments. The underlying card process applies, with the wallet's own record of the transaction available as well. Little extra evidence is needed; the wallet's history is durable and easy to produce.
PayPal. A separate process with its own rules, its own clock and its own view of what digital goods are. The messages exchanged inside the platform carry real weight, which is an argument for having the conversation there — the coverage and its limits are in what a PayPal dispute actually covers for digital goods.
Cryptocurrency. No arbiter, no file, no process. The transfer is final and there is nobody to submit evidence to. Your documents are still worth having, because they are what a seller acts on when you ask them to make something right, but they are material for a conversation rather than a case — crypto payments: fast, cheap and completely final is blunt about what that means.
Choosing the rail is therefore choosing whether your evidence has anywhere to go. The comparison across all four is on the payment methods page.
What we can produce for you
Our side of this is simple, and it is deliberately not dependent on you having been organised.
We keep the order record — what was bought, for how much, when it was paid, when it was activated and when it expires. Ask for it at any point and it comes back as a single message you can attach to anything. If your bank has asked a specific question, tell us what they asked and we will answer that rather than send a generic receipt.
What we cannot produce is your side: the thread where the arrangement was made, the page you read before you paid, the capture of the terms in force that day. Those are yours, and they are the ones that do the work.
Two things reduce how often any of this is needed. There is no card on file and no recurring charge here, so the largest category of dispute — a payment you did not expect — cannot occur. And the price is published rather than quoted: $69, $97 or $137 a year for one, two or three simultaneous screens, one-time, on the pricing page, so what was promised is on a page you can capture before you pay.
If something has gone wrong and you are working out what to send where, message WhatsApp, Telegram or support@pay-iptv.com. The fastest version of that message is set out in what to send support so a payment problem is solved in one message.
