Most guidance about paying online assumes one person: they choose the service, they pay for it, they own the account, and if something goes wrong they are the one who complains. A large share of household purchases do not work like that. One person decides, another one's card pays, and a third might be the one who actually uses it.
That is entirely normal and no seller should have a problem with it. It does, however, split a set of rights that are usually bundled together, and the split is invisible until the day something needs undoing.
The split nobody notices until it matters
Three roles exist in every subscription purchase, and in a household they can land on three different people.
| Role | Defined by | What it gives you |
|---|---|---|
| Cardholder | The name on the payment method | The right to dispute; the destination of any refund |
| Account holder | The name and email on the subscription | Support access, changes, renewal notices |
| User | Whoever holds the credentials | Day-to-day access, and nothing else |
When one person occupies all three, there is nothing to manage. When they are split, each right travels with its own role and cannot be transferred by agreement between the people involved. The seller cannot move a refund to a different card because everyone in the house says so, and a bank cannot open a dispute for someone whose name is not on the card. These are not policies a seller chooses; they are how the rails work.
Who can actually dispute a payment
The named cardholder, through their own bank, and nobody else. That is the whole rule, and it survives every household arrangement you can construct around it.
It follows that a purchase made on somebody else's card leaves you without the strongest recourse available in the transaction. You can still ask the seller for a refund — that route is open to anyone with the order details — but the fallback if the seller does not respond belongs to the cardholder. What each of those two routes actually reaches is set out in the difference between a refund, a chargeback and a goodwill credit, and in a shared-card situation you have full access to the first and none to the third.
The same asymmetry applies on the wallet side. A payment made through a wallet account belongs to whoever owns that account, and a claim under its buyer protection is opened from inside it. The mechanics of that are in what a PayPal dispute actually covers for digital goods. Cryptocurrency removes the question entirely by removing the reversal, which is the trade-off described in crypto payments: fast, cheap, and completely final.
The practical consequence is simple and worth deciding on deliberately. If you want to be able to act alone when something goes wrong, pay with your own method. If you use someone else's, you have chosen a shared decision, and that is fine as long as everyone knows it in advance rather than at the point of conflict.
Who controls the subscription itself
Payment rights follow the card. Control of the service follows something else entirely: the name and contact address on the account.
That is who a support desk will speak to, who can ask for a change, and who receives anything about the subscription. It is not a security theatre — a seller who took instructions about an account from whoever happened to message them would be a considerably worse seller. But it does mean the person who paid can find themselves unable to get an answer about the thing they paid for.
So decide it consciously at the point of ordering rather than letting it fall out of whoever typed first. The cleanest arrangement in a household is a single named account holder using a contact address both people can actually reach — a shared mailbox, or one that is not tied to a single person's work or phone.
A work address is the specific trap here. It is the one most people have open when they order, it is the one that gets typed, and it is the one that stops existing the week somebody changes jobs. Everything about the subscription then becomes unreachable at once: the renewal notice, the confirmation, and the address a support desk will check any request against. A twelve-month term outlives a surprising number of jobs, and recovering an account whose registered address no longer exists is slow in a way that has nothing to do with the seller being difficult.
Joint accounts and shared liability
A genuinely joint bank account is a different case from borrowing a partner's card, and it cuts both ways.
The helpful direction: either holder can normally raise a dispute on a payment from that account, because both are account holders in their own right rather than one being a guest on the other's card. Recourse is not stranded with one person.
The unhelpful direction: both holders are liable for what either one authorises, and both see every transaction. A payment made from a joint account is a payment made by the household, which removes any notion of a private purchase and means a disagreement about whether it should have been made is a conversation rather than a dispute.
Either way, one thing improves the position at no cost. Because both holders can see the line on the statement, make sure it will be recognisable when it appears. Note the descriptor and the date somewhere both people can find, along with the rest of the records listed in the paperwork worth keeping after you pay for a yearly service. An unfamiliar entry on a shared statement is the trigger for the problem in the next section but one.
Paying on a card you are named on but do not own
A supplementary or additional card carries your name but belongs to somebody else's account. It is the arrangement most likely to be misread, because the name on the plastic makes it feel like your card.
For the seller, it behaves as a normal card and the payment goes through unremarkably. For disputes, the rights sit with the primary account holder, not with the name embossed on the card you used. A refund goes back to the account, which is theirs. Statements go to them.
None of that is a reason to avoid it. It is a reason to tell them, before the line appears, that a subscription was bought and roughly what it will look like on the statement. Our figures are published in full on the pricing page — $69, $97 or $137 a year depending on simultaneous screens — so the amount can be checked against something public rather than taken on trust.
The unrecognised-payment problem
Here is the failure this whole article is really about, and it has nothing to do with fraud.
A cardholder sees an unfamiliar amount on their statement. They do not recognise the descriptor. Nobody mentioned it. They do the responsible thing and report it to their bank as an unrecognised transaction. The bank reverses it, the seller receives a chargeback, and the subscription is suspended — usually automatically, because a chargeback against a digital service is treated as the end of the relationship rather than a query.
Everyone involved acted reasonably. The cardholder was right to query something they did not recognise. The bank did its job. The seller applied a standard rule. And the household has now lost the service, the money is in transit, and the seller has a file marked disputed, which is a worse position to negotiate from than any of the alternatives. What a card network will and will not reverse, and why sellers treat it so seriously, is covered in chargebacks explained.
The prevention is a single sentence sent to the cardholder on the day: what was bought, how much, and what name will appear. That is it. It is the highest-value two minutes in this entire article.
How to set it up so none of this bites
Five things, none of which take longer than the payment itself.
- Decide who the account holder is before ordering, and use a contact address that more than one person in the household can open.
- Tell the cardholder what the charge is and roughly what the statement line will say, on the day it happens.
- Keep the confirmation where both people can find it rather than in one person's inbox. The case for holding onto it is in the receipt you should get.
- Agree who renews. Two people both remembering an annual date is how duplicate payments happen, and the cleanup is described in the cost of paying twice.
- Query the seller before the bank. If a household payment looks wrong, a message resolves it in hours; a dispute takes weeks and closes doors that do not reopen.
How it works here
There is no card stored on our side and no automatic charge, so a shared card cannot produce a surprise renewal twelve months later on an account nobody is watching. Every payment is a deliberate act by a person, once a year, and the reasoning behind that choice is in why we do not keep your card on file.
The account is held against whatever contact details are given at ordering, and that is who the desk will deal with. If the person paying is not the person who will be using it, say so in the thread when you order — it takes one line, and it means the confirmation goes to the right place first time rather than being forwarded on.
And if a line appears on a shared statement that nobody in the house recognises, ask us before your bank. We can identify a payment from the amount and date in a few minutes, which is faster than a dispute and leaves the subscription intact either way.
