How I disputed a hosting provider's billing in 30 minutes with AI (a documented 2026 EU case)

Most “vendor horror stories” are just venting. This one has a point, and a receipt for every claim in it. It’s a fully-documented account of one hosting-billing mess — and, more usefully, a concrete example of something this site keeps arguing: one person plus AI can now close a task that used to need a lawyer and a second language. I got every bogus charge cancelled in about half an hour.

Why I’m writing this

When you run several sites, you’re constantly dealing with hosts and registrars — and sooner or later you hit billing that’s dishonest, or just careless. The lesson never changes: always read and verify the terms of use. Not the marketing promises — the actual sopimusehdot / terms. They decide a dispute, and as this case showed, they work better than any amount of emotion or threat.

But the more interesting thread is the second one. Reconciling someone else’s invoices in Finnish, checking them against the law, and writing a proper complaint used to be an evening’s work for one person — if it was possible at all without a lawyer and the language. Here the whole thing took about 30 minutes, with AI.

Who this is about

Domainkeskus Oy (Turku, Finland, Y-tunnus 1607767-8) is one of the older Finnish registrars and hosts, around since 2001. It operates under several names: billing lives on billing.euronic.fi, support on euronic.help, the Finnish site is domainkeskus.com, and there’s a separate Estonian storefront, domeenikeskus.ee, selling .ee domains. Invoicing and collections are outsourced to Finvoicer Group Oy (per the invoices themselves).

That three-headed setup — Domainkeskus sells, Euronic bills, Finvoicer collects — turned out to be the source of every problem below.

The funnel: 10 cents to get in

Standard industry hook: the Mini hosting plan is €1.20 + VAT for the first year with a promo code (a symbolic “10 cents a month”); renewal is €23.88 + VAT 25.5% ≈ €30/year. Credit where due — they show the renewal price right on the order confirmation (“Uudistuksen hinta: 23,88€”), and the promo terms are clear: first-year only, normal price after. The problems start later.

Problem 1 — “Payment will not be taken automatically.” It is.

The first-year invoices say it in plain English: “Payment will not be taken automatically. To pay your invoice, please login and click Pay Now.” You pay by card manually — one-off, no mandate for recurring charges. Ten months later, with no consent from the customer, the renewal invoice arrives reading “Payment will be taken automatically from the credit card MasterCard-XXXX on [date]” — and the system does attempt to charge the stored card. In this case, six weeks before the due date, for a service period that hadn’t even started. Under Finnish payment-services law (maksupalvelulaki), charging without the payer’s consent is an unauthorised payment transaction. Here it was only saved by an empty card: both attempts failed.

Problem 2 — Finvoicer lives in a parallel timeline

This is the sharp part. The email invoice from Domainkeskus itself gives a due date of 6 August (logical — that’s when the paid period ends). But Finvoicer, handed the same invoice, issues it with its own due date of 21 June — six weeks earlier. So in July, paper maksuhuomautus (payment reminders) arrive with penalties — €5.00 reminder fee + 7.5% annual interest on each invoice — for “overdue” invoices that, by the seller’s own reckoning, weren’t due yet.

The tell: in its reply to the complaint, the company confirmed it outright — “Eräpäivätietoa tänne ei saada haettua, kun laskujen lähetys on ulkoistettu Finvoicerille” (“the due-date data isn’t pulled through here, because invoice sending is outsourced to Finvoicer”). Their billing system structurally doesn’t pass due dates to their own collections contractor, which then stamps penalty reminders on its own calendar. That’s not a one-off glitch — it’s the architecture.

Problem 3 — You can’t remove the card. Literally.

The obvious move after unauthorised charge attempts is to delete the card from your account. You can’t: the “remove payment method” function in their client panel (WHMCS) dies with a fatal PHP error — Call to a member function functionExists() on null in PaymentMethodsController. So you get a closed loop: the system tries to charge a card it has no mandate for, and you can’t revoke that card through the interface because the code is broken. The only exits are a written demand to the company, or blocking the card at your bank.

Problem 4 — The practice contradicts their own contract

The best part: none of this auto-renewal is even backed by their own terms. Domainkeskus’s yleiset sopimusehdot (rev. 14.12.2023) state the contract is fixed-term (“Sopimus on määräaikainen”); it ends with no notice period, services running to the end of the paid period; and continuation happens like this — “Asiakas voi jatkaa sopimusta tilaamalla lisäaikaa” — the customer continues the contract by ordering more time. So by their own contract, renewal is an active customer action, a new order. There’s no auto-renewal, no obligation to pay a second year, no advance invoicing two months out. The “Uudistuslasku” with auto-charge is a practice that lives in the billing system, not in the contract — which the company half-admitted in its reply: “laskut voidaan mitätöidä suoraan asiakkaan ilmoituksella että palveluita ei haluta jatkaa” (invoices are cancelled on a simple statement from the customer that they don’t want to continue).

How AI got me out in about 30 minutes

The trigger was the nasty kind: paper letters with penalties, for invoices that weren’t due. The situation where people either panic-pay “to make it stop” or drown in a foreign language and foreign law. Instead — about half an hour with AI, and a finished complaint. Step by step, how it actually went:

1. Put the whole packet in one place — every first-year invoice, the renewal invoice, the email invoice with the real due date, the paper Finvoicer reminders, the failed-charge notices. The physical letters as scans.
2. Had AI read and cross-check it — in Finnish and English at once. It surfaced and translated the key wording, and crucially reconciled the dates: the email invoice’s 6 August against Finvoicer’s 21 June on the same claim. The contradiction the whole case rests on showed up in minutes, not an evening of scrolling PDFs.
3. Checked it against their own terms and the law — the clauses in sopimusehdot about a fixed-term contract and renewal-as-an-active-order, mapped to the Finnish statutes (maksupalvelulaki for the unauthorised charge; perintälaki for the penalty-only-on-overdue rule).
4. Attached the technical bug as evidence — the WHMCS card-removal error, framed as its own argument: the customer is physically prevented from revoking the payment method.
5. Escalated it to the right bodies. Because the company sells .ee domains and targets Estonia (domeenikeskus.ee), a cross-border dispute can lean on the consumer protection of the country of residence — the Estonian Tarbijakaitseamet (TTJA) and the ECC-Net network, alongside Finland’s KKV. That gave the complaint weight: not just “refund this,” but “here’s where I’m required to report it if you don’t.”
6. Assembled it into a structured complaint and sent it in writing — before the due date on the reminder, to block the disputed claim being passed to collection.

How it resolved

One written complaint (reklamaatio) to laskutus@domainkeskus.com — disputing both invoices in full, citing the contradictory due dates, the absence of any renewal order, and their own terms, plus terminating services from the end of the paid period. Within a few days: both renewal invoices cancelled in full, penalties included (two separate credit notes / hyvityslasku), services marked to end at the paid period, and the card removed manually by staff — the thing their own system couldn’t do. No argument, no pushback. Which is both reassuring (competent support) and telling: the claims had no basis to begin with, and the company knew it.

Takeaways & checklist

To be fair: Domainkeskus isn’t a scam — the service works, prices are disclosed, and support responds fast and fairly to a written complaint. But their billing pipeline is built so an inattentive customer overpays by default: auto-charge switches on without an explicit mandate, an outsourced collector runs on its own dates and stacks penalties on not-yet-due invoices, and you can’t unlink the card through the panel.

If you’re a customer of Domainkeskus / Euronic / Domeenikeskus — or any host with a similar setup:

1. Promo price = first-year price. Check “Uudistuksen hinta” (the renewal price) immediately and set a reminder a month before the period ends.
2. Don’t leave a card in billing if you don’t want auto-renewal. If you can’t remove it, demand removal in writing and/or block the card at your bank.
3. Reconcile the dates on any collector’s reminder against the original invoice. Penalties on a not-yet-due invoice aren’t lawful — you don’t have to pay them.
4. Dispute in writing, in time. A riitautus sent before the reminder’s stated due date blocks the disputed claim being passed to collection. Get a ticket number and keep everything in it.
5. If you don’t want to renew, say so explicitly. Their terms make a statement enough; termination has no notice period, and the service runs to the end of the paid period.
6. Cite their own terms — it works better than any threat.
7. EU residents: because the company targets Estonia (.ee), a cross-border dispute can rely on the consumer protection of your country of residence — Estonia’s TTJA and the ECC-Net network, alongside Finland’s KKV.

Choosing where to host in the first place is its own decision — the honest EU hosting roundup is the place to start, and the broader admin side is in the EU admin guide.

Based on the full document set of one 2025–2026 customer case: orders, invoices, receipts, Finvoicer payment reminders, and support correspondence. Personal data omitted. The case ended with the company voluntarily cancelling the claims (two credit notes). This is a documented account and general information, not legal advice.