Private early access · Built for Europe
Keep building your product. Not the billing company around it.
Villow is European Merchant of Record infrastructure for the AI era. The plan: point your AI editor at our API and ship checkout, subscriptions, usage billing, tax, and payouts — designed to go live in minutes, not sprints. In private early access now.
- boltDesigned to go live in minutes
- verified_userMerchant of Record for you
- receipt_longVAT & invoices handled
- gavelBuilt to recover your revenue
Why a Merchant of Record
You ship the product. We're on the hook.
A payment processor moves the money — the tax, invoices, chargebacks, and refunds stay your problem. As Merchant of Record, Villow becomes the seller of record and takes them on.
What Villow takes on
- checkWe become seller of record and carry the tax liability
- checkInvoicing & receipts handled
- checkWe carry chargeback exposure and run the evidence workflow
- checkRefunds handled
- checkReserves & reason-coded payout holds on our side
- checkRecords kept for audit defense
A regular payment processor
- closeCalculate, collect & remit VAT (OSS)
- closeIssue compliant invoices & receipts
- closeChargeback & dispute liability
- closeRefund handling
- closeFraud exposure, reserves & payout timing
- closeAudit defense
Subject to legal and tax review by country and product category.
Revenue protection · planned early-access scope
Protect the revenue you worked to win.
Chargebacks, “I never got access” claims, and unpaid invoices quietly eat into revenue you already earned. Villow is designed to defend and recover it. Dispute evidence, recovery, and dunning are planned early-access scope, not yet live.
Win the disputes
- gavelDesigned to capture evidence at checkout: what the buyer saw, accepted, and accessed
- gavelAuto-assembled representment planned for card and PayPal disputes
- gavelThe “I never got access” defense, backed by real access logs
- gavelA full audit trail on every transaction
Recover overdue revenue
- savingsStructured dunning on legally due, overdue invoices
- savingsProvider-neutral external collection when dunning ends
- savingsRecovered funds recorded to the ledger, then reflected in your balance
- savingsReason-coded holds and reserves, fully visible
Subject to legal and tax review by country and product category.
The second product you never meant to build.
That whole second product? Villow is built to hand it to you through a single integration. Here's the planned scope:
Accepting payments is the easy part.
Then you're the billing department. The list only grows:
- check_box_outline_blankSubscription state
- check_box_outline_blankUsage tracking & metering
- check_box_outline_blankCredit balances & quotas
- check_box_outline_blankPlan limits and access control
- check_box_outline_blankCompliant invoices, credit notes & receipts
- check_box_outline_blankVAT, OSS & structured e-invoicing
- check_box_outline_blankRefunds and disputes
- check_box_outline_blankPayout reconciliation
Billing
Subscription state, plan changes, trials, coupons, cancellations.
Usage
Bill the API calls, tokens, and compute your app reports, including quotas and overages.
Credits
Balances, reservations, hard caps, expiry, invoice lines.
Entitlements
Feature access, plan limits, download access, overrides.
Tax & invoices
VAT and OSS workflows, compliant invoices and credit notes, e-invoicing formats such as ZUGFeRD and XRechnung where required.
Revenue protection
Win disputes, recover overdue payments, keep the revenue.
Payouts
Gross, fees, tax, reserves, refunds, net payout.
Compliance
Product and country checks before checkout.
Raw usage goes in. Revenue comes out.
Charge for usage before it burns you.
AI and API teams need revenue control before expensive usage happens.
- boltAuthorize usage before tokens, API calls, or compute are consumed
- boltCheck credits before usage
- boltEnforce hard quota limits
- boltSupport overages cleanly
- boltLink every invoice line to a raw usage event
- boltShow customers their own usage history
- boltCall entitlement checks straight from your product
Designed for the AI era
The goal: ship checkout in one prompt.
Building your SaaS with Cursor, v0, or Claude? Villow's docs are being written to be read by your AI. The plan: point it at our llms.txt or connect the Villow MCP server, describe what you want to sell, and it wires up checkout, billing, tax, and entitlements for you — designed for minutes, not a billing sprint. This is what we're building for private beta.
Planned developer surface — in build for the private beta.
"Add Villow to my app so I can sell: checkout, subscriptions, EU VAT and invoices, all handled."
// Villow (planned): checkout, subscriptions, EU VAT & invoices.
The design goal: your editor does the integration.
Frequently asked
Are you a payment processor?
No. Villow is the revenue and Merchant of Record layer for software businesses.
Will you act as Merchant of Record?
Yes — that is the core of the product, subject to legal and tax review by country and product category.
How fast will integration be?
The target: paste our AI-ready API into your editor and have checkout, billing, and tax configured in minutes. We're validating that with design partners in private early access.
Will you support usage-based billing and AI credits?
That's planned. Your product will send usage events; Villow will rate them and enforce limits, including credits and overages.
Will you handle VAT and invoices?
European VAT workflows, invoice fields, and receipts are part of the planned scope, subject to legal and tax review.
What will it cost?
One simple rate that already includes Merchant of Record, tax, billing, and payouts — no setup fee. Exact pricing is shared with design partners.
When will this be available?
Villow is in private early access. We are onboarding a small group of design partners first.
Is this you?
Good fit
- checkEuropean SaaS
- checkAI products with credits, tokens, quota or seat-plus-usage pricing
- checkAPI businesses with usage-based billing
- checkSoftware selling subscriptions across Europe
- checkTeams about to build billing, tax, usage or entitlement logic themselves
Lower fit for the first private beta
- removeHigh-risk categories (gambling, pharma, etc.)
- removeSellers who only need a basic payment button
- removeLarge enterprises with mature in-house billing teams
- removeProducts needing money movement outside licensed payment infrastructure
Apply for early access
Two fields. We'll take it from there.