Your provider says the payment was authorised and the seller has it. The seller says nothing arrived. You have now asked both twice, and both are politely immovable.
The instinct at this point is to work out which one is lying. That is almost always the wrong question, and pursuing it burns the days you actually needed. Neither side is lying, neither side is in charge, and there is a third party in this that nobody has mentioned to you.
The shape of the deadlock
These arguments arrive in a small number of recognisable forms. Working out which one you are in takes a minute and saves a week.
| What you are told | What is usually true underneath |
|---|---|
| "The payment went through" / "We never received it" | One is describing an authorisation, the other a settlement |
| "Your bank declined it" / "We didn't decline anything" | A risk layer between them refused it, and neither side owns that layer |
| "The refund was issued" / "Nothing has arrived" | Issued and received are days apart on the return leg |
| "The service was delivered" / "It never worked" | Delivery of credentials is not the same event as working playback |
| "You agreed to the terms" / "I never saw them" | A genuine factual dispute — and the only one of these five that is |
Four of those five are not disagreements at all. They are vocabulary problems, and they dissolve the moment somebody names the stage rather than the outcome.
Why both sides can be telling the truth
A payment is not one event. It is a sequence, and each party watches a different part of it from a different vantage point. You see your statement and your balance. The seller sees an authorisation record, a response code and a settlement status, and no view of your account whatsoever — the split is mapped out in what a seller can see about a payment that you cannot.
So "the money left my account" and "no payment has reached us" can both be literally accurate at the same moment, because a reserved amount and a received amount are different things. The same mismatch explains most refund arguments: a seller who issued a refund is telling the truth, and so is a buyer who cannot see it, because the return journey runs on a schedule neither of them controls — the refund that arrives as a reversal instead of a payment covers why the wait differs.
Before deciding who is wrong, check whether the two of them are even describing the same stage. Four out of five deadlocks end there.
Who actually decides
Here is the part most buyers never have explained to them. When a card payment is formally disputed, four parties are involved and only one of them decides anything.
| Party | Role | Decides the outcome? |
|---|---|---|
| You | Supply the claim and the evidence | No |
| Your card issuer | Files the claim on your behalf and represents you | No — it advocates |
| The seller | Supplies records to their processor | No |
| The card network | Applies its rulebook to both submissions | Yes |
That reframes the whole exercise. Your bank is not a judge who needs persuading of your sincerity; it is a representative that needs your material in a form the rulebook accepts. The seller is not a defendant who can concede; they are a party filing their own documents. And the rulebook cares about categories, dates and proof of delivery, not about who was more reasonable in the chat.
On a wallet the structure is shorter — the wallet provider both represents you and decides, under its own scheme rather than a network rulebook. Faster, and with narrower criteria, as set out in what a wallet dispute actually covers for digital goods. On an irreversible rail there is no structure at all: nobody adjudicates a payment in cryptocurrency, which is the trade-off named in crypto payments: fast, cheap, and completely final.
The three stages a dispute passes through
Knowing the shape tells you where your effort matters, and the answer is: almost entirely at the start.
Stage one — the claim. You state what happened, under a category your issuer selects, with whatever evidence you attach. Most cases are effectively decided here, because the category and the first document set the frame for everything after.
Stage two — the response. The seller's side submits its records. For a digital service that typically means the order, the payment record, the terms you accepted and evidence that credentials were delivered and used. You generally do not get to read this file, and you are rarely invited to rebut it in detail.
Stage three — the decision, and occasionally a second round. The network applies its rules. There may be one further exchange, but new evidence is often refused at this point. Anything you did not send at stage one may never be looked at.
Which produces one blunt rule: front-load everything. The strongest possible first submission beats a brilliant argument made in week four, and the material it needs is the material listed in the evidence your bank will ask for.
Your actual job in the process
You are not the judge and you are not the advocate. You are the evidence, and a good witness supplies four things.
A timeline with real dates. Paid on this date, activated or not on this date, reported on this date, replied to on this date. Nothing persuades a rules-based process like a sequence that can be checked. The three dates that matter most on any subscription are separated in paid, activated, expires.
The original transaction detail. Amount, currency, date, method, last four digits, and the descriptor exactly as it appears on your statement — which will often not match the brand name, for the reasons in what the descriptor on your statement is telling you.
The written exchange. Complete and unedited, including the parts that are not flattering to you. Selective screenshots read badly and are easy to spot.
One clear sentence of what you want. The sum, and the outcome. Not a narrative. Somebody is going to summarise your case in a field with a character limit, and it is better if you write that sentence than if they do.
Breaking a tie before it becomes a case
Formal disputes are slow, and roughly half of these deadlocks can be ended in one message by asking for a fact instead of an explanation.
Ask each side for a field, not an opinion. To the seller: does your record show a settled payment for this amount, on what date, and what response code came back? To your provider: is this line an authorisation or a settlement, and has it cleared? Both are answerable by reading a record, and the answers together usually collapse the disagreement.
Put the two answers side by side, in writing. Then send each side the other's answer, without commentary. Contradictions tend not to survive that treatment, and if one does survive, you now have a documented conflict, which is a far stronger claim than an undocumented one.
Ask one closing question and then stop. Something like: is your position that no refund will be issued? A dated yes is more useful to you than five more rounds of goodwill. Getting that first message right is most of the work — what to send support so a payment problem is solved in one message has the template.
Do not run two processes at once. A refund arriving mid-dispute produces a double credit, a clawback, and a record that reads as carelessness. Pick a direction, and switch deliberately rather than by accident.
Deadlines that decide it for you
The quiet villain in most of these stories is not the seller. It is the calendar. Every route has a window, counted from the payment date rather than from the date the argument started — so every week of patient back-and-forth is a week spent out of it.
Find out on day one what your window is, and write the last date somewhere you will see it. Then negotiate freely inside that period, knowing exactly when the alternatives close. What each rail can actually reverse, and for how long, is compared in what a card network will and will not reverse.
A practical rhythm that works: one clear message, then seventy-two hours. A second message naming the deadline, then seventy-two hours. Then a decision. Sellers who intend to resolve something respond well inside that; sellers who do not will not respond better in week five.
What we do when we are one of the two sides
We answer with records, not adjectives. The order, the amount, the method, the timestamps, the activation, and whatever the processor returned — sent to you in the same message we would send to a provider, so you are not the last to know what our file says.
If our records show the fault was ours, the money goes back on the route it came in on and no dispute needs to run. If they show the service was delivered as described, we say so plainly and show you why, rather than going quiet and letting a case decide it. Either way you get a date and a figure.
Most of this never arises here because there is nothing recurring to argue about. One annual payment — $69, $97 or $137 for one, two or three simultaneous screens on the pricing page — no card kept on file, nothing renewing on its own, and the routes listed on the payment methods page. The written position on refunds is on the refund policy page, where it can be read before you buy.
If you are stuck between two answers right now, send both of them to WhatsApp, Telegram or support@pay-iptv.com and we will tell you which stage each side is describing.
