How to accept payments for your AI project (2026)

What "accept payments" actually means for an AI project

Accepting payments is four jobs you'd rather not own:

Checkout, a hosted page that takes a card, charges it, and tells your app "this user paid."
Subscriptions or one-time charges, recurring billing, trial periods, proration, dunning when cards fail.
Tax, VAT in the EU, GST in the UK and Australia, sales tax in 45 US states. All on you the second you sell across a border.
Compliance, chargebacks, refunds, fraud, PCI scope, the cardholder dispute response window.

You can build all four. Most indie AI builders shouldn't. The infra you bolt on at $0 MRR is the infra you're cursing at $20k MRR when a German tax authority sends a letter.

The two ways to take money for an AI project

There are exactly two architectures. Pick one and move on.

Option 1: Raw payment processor (Stripe, Paddle Classic, direct gateway)

You are the merchant. Stripe charges 2.9% + 30 cents on US cards, more across borders (closer to 5.4% when you add currency conversion, international card surcharges, and 3D Secure). You handle every other job yourself: invoicing, VAT registration in every country you cross a threshold in, refund flows, chargeback responses, license-key generation, webhook reliability.

Good if: you have an engineer who lives in payments code, you sell mostly inside one country, or you want maximum control of the checkout UI.

Bad if: you're an indie builder shipping at night. You'll spend more time on Stripe edge cases than on prompt engineering.

Option 2: Merchant of Record (MoR) like creem

A Merchant of Record sells your product on your behalf. They take the card, collect the right tax for the buyer's country, remit it to the right tax authority, handle refunds and chargebacks, and pay you out clean. You ship product. They handle payments.

This is the path most solo AI builders actually want. It's why people move off Stripe once they cross borders.

How to wire up payments in an afternoon (the MoR path)

Here's the literal flow if you go with creem:

Sign up at creem.io and create a product. Pick one-time, subscription, or usage-based.
Drop the hosted checkout link into your AI app. "Subscribe" button, done.
Add a webhook handler that listens for transaction_completed and subscription_canceled. Two endpoints, ~30 lines of code. Full reference at docs.creem.io.
Generate license keys if you sell desktop/CLI tools, creem ships license-key issuance native, no extra service.
Wire up revenue splits if you're co-building with a partner, split payouts automatically without invoicing each other monthly.

That's it. Tax is handled. Chargebacks are handled. Refunds are a button. Your only ongoing job is shipping the AI product.

What it costs (the honest math)

Here's the all-in rate for indie-builder payment infra in 2026:

Stripe direct: ~2.9% + 30¢ headline, ~5.4% effective when you add cross-border, currency conversion, and the cost of your own tax/dunning/license stack.
Paddle: 5% + 50¢, MoR included.
Lemon Squeezy: 5% + 50¢, MoR included.
Gumroad: 10% flat on most plans.
creem: 3.9% + 40¢, MoR + revenue splits + license keys + affiliate program + AI insights bundled.

The spread is real. On $5k MRR, the difference between 3.9% and 7.5% (a typical LS-equivalent rate when you stack add-ons) is roughly $2,160/year, which buys you a lot of API credits. Full breakdown in our pricing page and the honest fee breakdown post.

What bites you in month two

Things indie AI builders learn the hard way:

EU VAT. The moment you sell one subscription to a German developer, you owe VAT MOSS registration. Source: EU OSS portal. An MoR handles this; raw Stripe does not.
Refund storms. AI products get "this is not what I expected" refund requests at 2-3x the rate of normal SaaS, especially around model deprecations. An MoR queues these into one dashboard with a refund button.
Chargebacks on "AI hallucinated." Cardholders dispute charges when the model gives them a bad answer. Stripe charges $15 per dispute regardless of outcome. An MoR fights the dispute on your behalf.
Failed cards. ~12% of subscription cards fail in any given month (expiry, fraud holds, insufficient funds). Without smart dunning, that's pure churn. creem and most MoRs include retry logic.
License-key sprawl. If you sell a CLI or desktop AI tool, you'll hand-roll a license server. Don't. Pick infra that issues keys natively.

When you should NOT use an MoR

Be honest about anti-fit:

You're already at $100k+ MRR in one country and built the tax/dunning stack. Switching costs more than it saves.
You sell B2B enterprise with custom MSAs, procurement, and NET-60 terms. MoRs are built for self-serve.
You need wire transfers, ACH-only flows, or in-person POS. Different category entirely.

For everyone else shipping an AI side project, indie SaaS, or AI-powered tool to a global audience: MoR is the right call.

What to do this week

Three steps:

Today: sign up at creem.io, create your first product (one-time or subscription), drop the checkout link in your app.
Tomorrow: add the transaction_completed webhook, see docs.creem.io for the recipe. ~30 lines.
This week: turn on the affiliate program if your audience is on Twitter or Discord. Indie AI projects with built-in affiliate links convert 3-4x better than ones without.

For the deeper dive on AI-product monetization shapes (usage-based vs subscription vs one-time), read how to monetize AI agents.

FAQ

What's the cheapest way to accept payments for an AI project? For solo builders selling globally, a Merchant of Record like creem (3.9% + 40¢) is cheaper all-in than Stripe once you factor in VAT registration, dunning, license keys, and dispute handling. Headline Stripe rates look lower but the real total cost is higher when you account for what an MoR bundles.

Do I need to register for VAT to sell my AI tool in Europe? Yes, the moment you sell to any EU customer. You can either register via the EU OSS portal and file quarterly, or use a Merchant of Record that handles VAT collection and remittance for you. Most indie builders pick the MoR route to skip the paperwork.

Can I use Stripe for a side project that's not a real company? You can use Stripe Atlas or your personal account, but you're personally on the hook for tax, refunds, and chargebacks. For a side project, a Merchant of Record removes the legal exposure because they're the seller of record, not you.

How do I issue license keys for a paid AI desktop or CLI tool? Use a payment platform with native license-key issuance, like creem, so a successful payment triggers a unique key emailed to the buyer. Hand-rolling a license server adds weeks of work and ongoing maintenance.

What about Lemon Squeezy or Paddle? Both are MoRs and both work. Lemon Squeezy charges 5% + 50¢ and Paddle charges 5% + 50¢. creem is 3.9% + 40¢ with revenue splits, affiliate program, and license keys bundled, which is why indie AI builders moving off LS or Paddle tend to land on creem.

Ship it

The boring part of running an AI project is payments. Skip it. Start with creem, drop the checkout link, get back to model swaps.

How to accept payments for your AI project (2026)