Sell credits for your AI tool by card and keep what you’ve earned.
AI tools draw stolen cards that buy compute and dispute it later, and card processors drop image generators over what users might make. Railbed takes your users’ cards for credits and plans and settles every sale to a wallet you control.
- No application to pass
- No setup fee
- Settled sales stay yours
Press the card to run an example sale.
- Settles to
- Your own wallet, as USDC on Polygon
- Chargebacks
- Settled sales can’t be pulled back. Card disputes go to the provider
- To start
- An email, your website and a payout wallet. No setup fee, no monthly fee
- Buyer ID checks
- Providers decide. Smart Routing picks the one least likely to ask
How can an AI image generator or AI tool take card payments?
AI tools can take cards, but processors treat them as high risk. One large processor measured attempted card fraud at AI startups at up to 4.3 times the rate for startups overall, and image, video and voice tools are judged by what users might generate. Railbed takes your users’ cards through independent, licensed card providers and settles each credit pack or plan to a wallet you control, with no underwriting and no application to pass. It has no automatic recurring billing, so plans sell as prepaid periods or credit packs.
Why do card processors treat AI tools as high risk?
An AI tool sells compute that’s expensive to run, delivered in seconds and easy to resell. That makes it a favourite target for stolen cards: a fraudster buys credits, burns or resells them, and the real cardholder disputes the charge weeks later, after your GPUs have done the work. Image, video and voice tools carry a second risk in a processor’s eyes, because of what users might generate.
- 4.3xAttempted card fraud at AI startups, at its peak, compared with startups overall
- 40%Rise in attempted multi-account abuse at AI subscription companies in six months
- 1 dayHow early one AI platform’s card processor left, without warning, in May 2025
Our card processor pulled out a day early, without warning.
The fraud numbers come from the processors themselves. Stripe reported that AI startups faced up to 4.3 times the attempted transaction fraud rate of startups overall, and that attempted multi-account abuse at AI subscription companies rose 40% in six months. It explains why: AI companies “offer compute that’s valuable and easy to resell”, and a fraudster “may use a stolen card to buy an AI subscription or a block of tokens, then sell that access on secondary markets”. When the cardholder notices, the dispute comes back to the merchant, along with a fee and a mark against its dispute ratio.
The content risk is less predictable. In May 2025 Civitai, one of the largest platforms for generative image models, announced that card payments would pause, then updated its notice: “Our card processor pulled out a day early, without warning.” It had already changed its content rules, and still, it wrote, “the processors ultimately decided Civitai was still outside their comfort zone”. Stripe’s prohibited businesses list bans “any artificial-intelligence generated content” that meets its adult-content criteria, which reaches image and video tools whose users can make such content even when that isn’t the product’s purpose.
What AI builders run into
- A stolen-card wave drives the dispute rate up in a week, and the processor adds a reserve or closes the account.
- An image, face-swap or voice tool gets reviewed for what users could make, not for what the business sells.
- Credits are spent the moment they’re bought, so a dispute weeks later recovers money but not compute.
The written rules go beyond adult content. Paddle’s list of what it won’t sell, last updated on 13 April 2026, has an entry for “Content generation” that names “Face Swaps”, “Deep Fakes Images or Videos” and “Voice Impersonations”, and marks “Human-like faces in realistic, stylized, or animated forms” as a restricted category that needs enhanced due diligence. A portrait generator, an avatar maker and a voice cloner all sit inside that entry, whatever their users do with them.
The fraud also moves. Stripe’s figures show attempted card fraud at AI startups falling from 4.3 times the startup rate in the third quarter of 2025 to 2.6 times in the first quarter of 2026, while the abuse shifted to sign-up: at the AI subscription companies hit hardest, attempted multi-account abuse rose 154% between January and June 2026. A tool that fixes one leak finds the next one a quarter later.
AI tools and card payments, 2025 to 2026
The pressure on AI tools comes from three directions at once: processors deciding what content they will carry, card networks tightening the room for disputes, and lawmakers writing the first rules for generated images. Most of it happened in eighteen months.
- May 2025
Civitai, a platform for generative image models, loses card payments when its processor leaves a day before the announced date.
- Jun 2025
Stripe adds a $15 fee for countering a dispute in the United States, beside the $15 fee for receiving one.
- Q3 2025
Attempted card fraud at AI startups on Stripe peaks at 4.3 times the rate for startups overall.
- Apr 2026
Visa lowers the ratio of disputes and fraud reports at which it counts a merchant as excessive, from 2.2% to 1.5%.
- 19 May 2026
The US Take It Down Act’s duties for platforms take effect: a reported intimate image, real or AI-made, must come down within 48 hours.
- Jun 2026
Stripe counts a 40% rise in attempted multi-account abuse at AI subscription companies since January.
- 27 Jul 2026
The EU’s AI Omnibus enters into force, with a prohibition on AI systems that generate non-consensual sexually explicit and intimate content.
- 2 Aug 2026
The EU’s AI Act, which asks providers of generative AI to make their output identifiable, becomes applicable with some exceptions.
Two things follow for anyone selling an AI tool. A processor’s comfort with your product can change faster than your product does, as Civitai found after it had already changed its rules. And the cost of each stolen-card sale has gone up: a dispute fee to receive it, another to fight it, and a lower ceiling on how many you can absorb.
How does Railbed fix it?
Railbed is card checkout for AI tools that never holds your money. Users pay with the card they already have, an independent licensed card provider charges it, and each sale settles as USDC straight to a wallet you control, usually minutes after the user pays.
| What goes wrong today | With Railbed |
|---|---|
| Stolen-card disputes arrive after the credits are spent, and come out of your balance | Settled sales can’t be pulled back from your wallet. Card disputes go to the provider that charged the card |
| A processor reviews your tool for what users might generate | No underwriting and no application to pass |
| A dispute spike adds a reserve or closes the account | Nothing is held back from your sales, and there’s no balance to freeze |
| Weeks of review before you can charge | Sign up with an email, your website and a payout wallet |
| One acquiring bank decides which users’ cards go through | Smart Routing sends each user to the card provider most likely to approve them, worldwide |
| Payment details on your own pages | Card details are entered on the provider’s page, never on yours |
The card provider charges the card and takes on the card dispute. Railbed confirms that the right amount reached your wallet before it marks a payment Paid, and a signed webhook tells your app to add the credits.
Which checkout fits an AI tool
Most AI tools need two of Railbed’s ways to sell: one inside the app, for the user who has just run out of credits, and one for the company that wants a bill. What you sell decides which.
| What you sell | What to use | What you build |
|---|---|---|
| Credit packs bought inside your app | A checkout session for each purchase, from the REST API | One API call with the user’s id as the reference, and one webhook handler that adds the credits |
| Two to four plans on a pricing page | A pricing table, on its own page or embedded in yours | Nothing to start. Add the webhook when you want plans to switch on by themselves |
| A lifetime licence, a model or a prompt pack | A buy button or a checkout page | Nothing. Paste the snippet, or share the page’s link |
| Team seats and prepaid API usage for a company | An invoice with lines, tax and a due date | Nothing. Send it from the dashboard or create it through the API |
| Credits in an app you built without code | A pricing table, with Zapier or n8n acting on each paid payment | A workflow that starts from the paid-payment trigger |
Whichever you choose, the user pays on the card provider’s page and your system hears about it from the same signed payment.paid event. Start with a pricing table if you want to be selling today, and move to checkout sessions when credits should land in the account without anyone opening the dashboard.
What one stolen-card sale costs
The arithmetic of a small credit pack is what makes AI tools fragile at a conventional processor. Take a $20 pack bought with a stolen card and disputed three weeks later, using fees the processors and networks publish:
| What happens | At a conventional processor | With Railbed |
|---|---|---|
| The sale itself | $20 is debited back from your balance | The settled sale stays in your wallet |
| The dispute | A $15 dispute fee in the United States, which Stripe’s dispute guide says is non-refundable | The dispute goes to the card provider that charged the card |
| Fighting it | Another $15 to counter, returned only if you win | Not yours to fight |
| Your dispute ratio | Counts toward Visa’s 1.5% line, and a merchant in its programme pays $8 for each fraudulent or disputed transaction | Nothing comes out of your wallet |
| The compute | Spent, and yours to pay for | Spent, and yours to pay for |
The last row is the same in both columns on purpose. Railbed changes who carries the card dispute, not who pays the GPU bill, so limits on new accounts are worth keeping wherever you take payments. The same guide notes that card networks “typically allow cardholders to initiate disputes within 120 days of the original payment”, which is a long time to keep a sale provisional when the credits were used in an afternoon.
What does Railbed refuse?
Railbed adds no rules of its own, and its acceptable use policy holds only the limits the law sets. Those include sexual content involving minors, and sexual content involving people who did not consent or who are shown without their consent. A tool built to make sexual images of real people without their consent falls inside those limits. Your own terms, moderation and the laws in your users’ countries stay your responsibility.
The laws an image, video or voice tool has to follow
Selling a general AI tool is lawful, and the first laws written for generated media are aimed at what gets made and published with it. They bind you whichever payment company you use, and following them is your job, not Railbed’s.
- United States. The FTC enforces the Take It Down Act’s platform duties, in effect since 19 May 2026. Its guidance says covered platforms must remove a reported intimate image “within 48 hours” of a valid request, that the law covers “digital forgeries” made with “software, an app, or artificial intelligence”, and that a business which “primarily provides a forum for user-generated content” may be covered. Violations can bring civil penalties of $53,088 each.
- European Union. The Commission’s summary of the AI Act says “providers of generative AI have to ensure that AI-generated content is identifiable”, and that deep fakes should be “clearly and visibly labelled”. The Act became applicable on 2 August 2026, with some exceptions, and the AI Omnibus that entered into force on 27 July 2026 “Prohibits AI systems that generate non-consensual sexually explicit and intimate content or child sexual abuse material”.
If your tool hosts a public gallery or lets users share what they make, read the first of those closely. If it only returns a private result to the person who asked, the labelling rules matter more. Either way, check the current text for the countries you sell to.
How does a sale work?
A user picks a 2,000-credit pack in your app. Your server creates a checkout session with their account id.
Railbed’s checkout opens and asks for an email. Smart Routing sends the user to the card provider most likely to approve their card.
The user pays on the provider’s page in a new tab. The provider decides whether to ask for identity details. Smaller payments often need little or none, and Smart Routing tries the providers least likely to ask first.
The provider buys USDC with the payment, and it’s forwarded to your wallet on Polygon. Railbed checks that the right amount reached the right wallet before it marks the payment Paid.
Railbed sends your server a signed webhook, and your app adds 2,000 credits to that account.
Try the whole flow in Test mode with a Test API key first. Payments are simulated and no card is charged.
Before you sell your first credit pack
None of this needs an application or a waiting period. It is the short list an AI tool gets right once, so that credits land in the right account by themselves and nothing is added twice.
A payout wallet. Save the Polygon wallet your sales should settle to. Use a wallet you hold the keys to, not an exchange deposit address.
Pack sizes and prices. Card providers have minimums, the smallest about $2, and a price of around $10 or more gives users the widest choice of providers. Sell 100 credits for $10, not 10 for $1.
An account id on every session. Put the user’s id in the checkout session’s
reference, so the payment finds its account without matching on an email address.A webhook that adds credits once. Add the credits when the signed
payment.paidevent arrives, and record the event’s id. A delivery that fails is retried, so the same event can arrive twice.Limits on new accounts. Cap what a brand-new account can generate in its first hours, and keep free credits small. The compute a fraudster burns is yours to pay for wherever the payment went.
A content policy and a way to report. Write down what your tool won’t make, and give people a way to report an image of themselves. The removal duties in the laws above are yours.
A refund rule. Decide what you refund for unused credits and how you send it, because Railbed can’t reverse a settled payment for you.
A run in Test mode. Buy each pack with a Test API key and watch the credits arrive before you take a Live payment.
Keeping abuse down when the money is already yours
Settled sales can’t be pulled back from your wallet, which removes the dispute from your books. It doesn’t remove the fraudster from your GPUs. The controls that matter for an AI tool sit in your product, and most of them are about accounts, not payments:
- Tie free credits to something scarce. Stripe describes multi-account abuse as creating “many accounts during sign-up to repeatedly claim free tokens, trials, and other new account benefits”, and says one voice company blocked 2,000 users a day from abusing its free tier. A small paid starter pack costs an abuser money each time.
- Rate-limit the first day. A new account that spends a large pack in an hour, or runs from many locations at once, is worth pausing before its next purchase.
- Ask for what you need at checkout. A checkout page can ask for a name or a company, and can require a date of birth with a minimum age. It records what the buyer says; it is not an identity check.
- Let the card provider do its part. The provider that charges the card runs its own fraud checks before it does, and under its own terms it may decline a buyer who has disputed before.
Renewals without a stored card
Railbed doesn’t run automatic recurring billing. A pricing table’s / mo or / yr label describes the plan; it doesn’t schedule another charge, and no card is kept on file. For an AI tool that usually means one of two shapes:
- Credits that run down. The user buys a pack, uses it and buys another when it’s gone. There is nothing to renew, and no charge to forget.
- Plans that end. The user buys a month or a year, your app shows the date it ends and reminds them before it does, and they pay again if they want to continue. For a company, send a renewal invoice with reminders around the due date.
You will lose some renewals that a stored card would have collected. You will also lose the “I didn’t authorise this” disputes that follow a forgotten renewal, which is a trade many AI tools would take.
Running Railbed beside the processor you have
Nothing about Railbed is exclusive, and you don’t have to move everything at once. If a mainstream processor still serves you, the usual first step is to add Railbed as a second way to pay by card. Three places it earns its keep early:
- As the fallback. When your main checkout declines a card, offer Railbed on the same screen. A buyer turned away by one fraud screen is often approved by a different card provider.
- For the sales your processor won’t take. If a product, a country or a kind of output is outside what your processor allows, send those orders to a Railbed checkout and leave the rest where they are.
- As the spare. A tool with two working checkouts keeps selling on the day one of them changes its mind about image generators.
Use the same account id as the reference in both, and let both checkouts’ paid events call the same code that adds credits.
Fees and getting paid
Railbed shows every fee before anyone pays. Fees come out of the USDC that arrives: the card provider’s own fee and exchange spread, which the user sees on the provider’s page, a 1% network fee, and the Railbed fee, from 0.9%, shown in your dashboard. There’s no setup fee and no monthly fee.
Set prices in USD, EUR, GBP, CAD, AUD, INR or SEK. Settlement is almost always USDC on Polygon, straight to your wallet. Pay your GPU and model bills from a bank account by sending USDC to any exchange or off-ramp you use, or pay providers that take USDC directly.
Credit packs of about $10 or more give users the widest choice of card providers, because each provider has its own minimum.
Railbed compared with a payment processor for AI tools
| Mainstream processor or high-risk account | Railbed | |
|---|---|---|
| Approval | A review of your model, your users and their content | No underwriting and no application to pass |
| Stolen-card disputes | Paid from your balance, with a fee and a ratio | Settled sales can’t be pulled back. Card disputes go to the provider |
| Reserve | Added when disputes rise | Nothing is held back from your sales |
| If you’re dropped | Card payments stop, sometimes without warning | Settled sales are already in your wallet |
| Renewals | Automatic charges that users forget and dispute | Each renewal a payment the user chooses |
| Payouts | On the processor’s schedule | Each sale, to your own wallet, as soon as it settles |
When Railbed is not the right fit
Railbed suits an AI tool that sells credits or prepaid plans and wants card payments without a category decision hanging over it. It is the wrong tool in a few cases, and it is better to know them before you build:
- You need cards charged automatically. Railbed has no recurring billing. If your revenue depends on silent monthly renewals, a plan that ends is a different product.
- You bill by metered usage after the fact. Railbed doesn’t meter anything. Sell usage as prepaid credits, or send an invoice for what a company used last month.
- You sell packs under about $2. Card providers have minimum amounts, so micro-purchases have to become larger packs.
- You want someone else to handle sales tax. A merchant-of-record platform collects and files VAT and sales tax in its own name. With Railbed the sale is yours, and so is the tax where you owe it.
- You never want to hold USDC. Sales settle as USDC to your wallet. Moving it to a bank is a few steps through an exchange, and it is a step you take yourself.
Words worth knowing
The terms an AI founder meets when a processor starts asking questions.
- Credits
- Prepaid units a user spends on generations, minutes or tokens. One payment buys a pack, and nothing is charged again when it runs out.
- Multi-account abuse
- One person opening many accounts to claim free credits or trials again and again. Stripe counted a 40% rise at AI subscription companies in the first half of 2026.
- Card testing
- Running stolen card numbers through small purchases to see which still work. Cheap credit packs and free trials that ask for a card attract it.
- Dispute ratio
- A merchant’s disputes and fraud reports as a share of its card sales. Visa has treated 1.5% as excessive since April 2026.
- Reserve
- Part of your sales a processor keeps back to cover future disputes. It usually appears after a dispute spike, when cash is already short.
- Restricted category
- A kind of business a processor accepts only after extra checks, and can look at again whenever it chooses. Paddle lists realistic AI faces this way.
- Digital forgery
- The Take It Down Act’s term for an intimate image made or altered with software or AI. Platforms must remove a reported one within 48 hours.
- Merchant of record
- A company that sells to your users in its own name, collects the money and the sales tax, and pays you afterwards on its schedule.
Questions
Stripe or PayPal closed my AI image generator. Can I use Railbed?
Yes. Railbed has no underwriting and no application to pass, and a past closure doesn’t rule you out. Sign up, connect your app with a Test API key and try the flow the same day.
What happens if a fraudster buys credits with a stolen card?
The cardholder’s dispute goes to the card provider that charged the card, and a settled payment can’t be pulled back out of your wallet. Keep sensible limits on new accounts anyway, because the compute they use is still yours to pay for.
Can I sell subscriptions?
Railbed doesn’t charge cards automatically. Sell monthly or yearly plans as payments the user chooses, or credit packs, and remind users by email or in your app when a plan ends.
How do I add credits to a user’s account automatically?
Create each checkout session from your server with the user’s id, and listen for Railbed’s signed payment.paid webhook. Add the credits once, when the payment is Paid.
Do users need crypto or a crypto wallet?
No. Users pay with the card they already have. The conversion to USDC happens after they pay, and only you need a wallet.
Will users be asked for ID?
Sometimes, and the card provider decides. Smart Routing sends each user to the provider least likely to ask for ID at their amount and location, so smaller payments often go through with little or no check.
Can Railbed freeze my money?
No. Every paid sale settles straight to a wallet you control, so there’s no balance with Railbed to hold. Railbed can stop new payments on an account only when the law requires it, and it can never touch USDC that has already reached your wallet.
How do I get the money into my bank?
Send USDC from your wallet to any exchange or off-ramp you use, then withdraw to your bank account. You choose when and how much. The guide shows each step.
Why do payment processors ban or restrict AI image generators?
For two reasons: fraud and content. Stripe measured attempted card fraud at AI startups at up to 4.3 times the rate for startups overall, because compute is easy to resell. And processors judge image, face and voice tools by what users could make with them: Paddle’s list names face swaps, deepfakes and voice impersonation.
Is it legal to sell an AI image or voice generator?
Selling a general-purpose tool is lawful in most countries. The laws that exist target what is made and shared: in the United States the Take It Down Act requires covered platforms to remove reported intimate images, including AI-made ones, within 48 hours, and the EU’s AI Act requires AI-generated content to be identifiable. Those laws are yours to follow.
What is the smallest credit pack I can sell?
Card providers set minimums, and the smallest is about $2. A price of around $10 or more gives users the widest choice of providers, so a pack of 100 credits sells more easily than a pack of ten.
Can I bill for API usage at the end of the month?
Not automatically, because Railbed doesn’t meter usage or store a card. Sell prepaid credits that your API draws down, or send a company an invoice for last month’s usage with a due date and reminders.
Can I sell credits without writing code?
Yes. Put your packs on a pricing table, share its link or embed it, and add the credits in your own app when a payment shows Paid in the dashboard. When you want it automatic, a Zapier or n8n workflow can start from each paid payment.
Can I keep my current processor and add Railbed?
Yes. Nothing about Railbed is exclusive. Add it as a second way to pay by card, so one processor’s decision about AI tools can’t stop every sale.
How fast do I get the money?
Usually within minutes of the user paying. The card provider buys USDC, it is forwarded to your wallet on Polygon, and Railbed marks the payment Paid once it has checked the amount and the wallet. There is no payout schedule and no balance held with Railbed.
Sources
- Stripe: What Stripe data shows about fraud at AI startups, checked 20 November 2026
- Civitai: Credit card payments pausing May 23, 2025, 19 May 2025, checked 20 November 2026
- Stripe: Prohibited and restricted businesses, last updated 22 September 2026, checked 20 November 2026
- Decrypt: Civitai turns to crypto after credit card processor ban, checked 20 November 2026
- Paddle: What am I not allowed to sell on Paddle?, last updated 13 April 2026, checked 20 November 2026
- Stripe Support: June 2025 pricing updates for disputes, checked 20 November 2026
- Stripe Docs: How disputes work, checked 20 November 2026
- Merchant Risk Council: Stricter VAMP ratio thresholds are now in effect, 1 April 2026, checked 20 November 2026
- Federal Trade Commission: Complying with the Take It Down Act, May 2026, checked 20 November 2026
- European Commission: AI Act, last update 19 October 2026, checked 20 November 2026
- European Commission: AI Omnibus enters into force, 27 July 2026, checked 20 November 2026
Last updated .
Paid5,000 credits, settled to your wallet$25.00
Sell the credits.
Keep what you’ve earned.
Set up in under a minute. Your first payment can settle today.
- No application to pass
- No setup fee
- Settled sales stay yours
Moving a lot of volume? Talk to our team