Building a licensed permit sales platform with a government API: what founders need to know

Selling a licensed product online, with a government API deciding whether each sale is valid, is a product job, not a brochure job. The customer sees a simple purchase. Underneath it there is authorisation, validation, a third-party system you do not control, a payment that must never be taken without a permit issued, and an operator who needs to sleep. Here is what that takes to build, what it costs, and how one authorised distributor got a platform that sells around the clock without anyone touching it.

Why the brochure approach fails

An authorised distributor often starts with a website that explains the product and a form that takes the request, and a person who completes the purchase in the government system by hand. It works for ten sales a day. It breaks at a hundred, at night, at the weekend, and every time the person is on holiday. The customer, who is often a driver at a border, does not wait.

Automating it means the platform talks to the government system directly. That is where the real work is.

The four things that have to be right

1. Compliance built in, not bolted on

The authorisation to sell comes with rules: what data to collect, what to store, what to show on the receipt, how long to keep records. Those rules are the product specification. A platform that validates everything before it calls the API never sends a bad request, and the audit trail exists because the system wrote it, not because someone remembered to.

2. An API you do not control

Government APIs can be slow, briefly unavailable, or change with little notice. The platform needs to queue requests, retry sensibly, and tell the customer the truth: “your permit is being issued, you will receive it by email within a few minutes” beats a spinner. Monitoring tells the operator before the customer does.

3. Payment only when the product exists

Take the payment, issue the permit, and if issuing fails, refund automatically and say so. Stripe handles the payment side, including holds and refunds, and the platform’s job is to make the two sides never disagree.

4. A site for the customer who is in a hurry

Many customers are foreign drivers, on a phone, possibly at a service station. The purchase has to work in their language, take their card, and finish in under two minutes. That is a design constraint, and it shapes everything from the form fields to the confirmation screen.

What it costs and how long it takes

This is the Build solution applied to a regulated product.

Scope	Typical range	Timeline
Brand, customer-facing site, purchase flow, one API integration, Stripe, operator admin	€15k to €25k (about £13k to £21k, $16k to $27k)	6 to 8 weeks
Above plus multilingual, queueing and monitoring, automated refunds, reporting	€25k to €35k (about £21k to £30k, $27k to $38k)	8 to 10 weeks
Above plus reseller accounts, a second product line, mobile app	€35k to €50k (about £30k to £43k, $38k to $54k)	10 to 12 weeks

The authorisation process itself often sets the calendar. Start it before the build, not after.

Case study: Vignetique

Vignetique is an authorised distributor for the national road infrastructure authority, selling the electronic road vignettes drivers need through a digital platform. A regulated product, a payment step people have to trust, and customers who are often foreign drivers passing through: the platform had to be simple, compliant and secure at once.

We delivered the brand, the website and the sales platform, with Stripe for payments and the authority’s system in the loop for every permit. The purchase flow was designed for a driver on a phone with a queue behind them.

• -40% bounce rate: visitors understand the product and start the purchase
• +65% session duration: drivers complete the flow instead of abandoning it
• +210% email subscribers: customers come back for the next permit instead of searching again

“We were a startup in a regulated space, and they treated it like a product, not a brochure. The platform sells permits around the clock, payments work, and I haven’t had to touch it. That was the point.”

Marius H, CMO @ Vignetique

What to prepare

• The authorisation documents and whatever API documentation the authority provides, however thin.
• A test account on the authority’s system, or the contact who can get one. This is usually the slowest step.
• Your refund and support policy, because the platform will enforce it automatically.
• The languages and countries your customers come from.

Sell a regulated product like a product

If you hold an authorisation and a spreadsheet, tell us what you are licensed to sell and which system issues it. We will come back with a scope, a number and an honest view of the authorisation timeline within one business day.