Take cards for your NSFW AI app and get paid the day users buy.
Processors class AI that makes adult content as adult content, then reject it, freeze it or look again once sales grow. Railbed takes your users’ cards for credits and memberships and settles every sale to a wallet you control. Settled sales can’t be pulled back.
- 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
Can an NSFW AI app take card payments?
Yes, but most card processors class AI that can produce sexual content as adult content, then refuse it, freeze it or look again once sales grow. Railbed takes your users’ cards through independent, licensed card providers and settles each credit pack or pass to a wallet you control, with no underwriting and no application to pass. It has no recurring billing, and the laws on companions and age checks stay yours to follow.
Why card processors turn NSFW AI apps away
Card processors treat AI that produces sexual content as adult content, the highest-risk category on the card networks. Most won’t take it at all. The ones that approve an AI app often look again after launch, when sales grow or a word in your marketing trips a review.
- 10.8–15.5%Of each sale at specialist adult billers, by their published pricing
- 6 daysOf sales before one AI image founder’s account was closed
- 1.5%Visa’s fraud and dispute threshold before a merchant is flagged, since April 2026
6 days worth of sales
Stripe’s prohibited and restricted businesses list bans “any artificial-intelligence generated content” that meets its adult criteria, along with adult live-chat features. A companion that stays strictly safe for work isn’t on the list, but romantic or explicit features move an app into the adult category. PayPal’s acceptable use policy prohibits certain sexually oriented materials and requires pre-approval for mature audience content, and Square’s payment terms rule out adult entertainment “in any medium”. The app stores are closed too: Apple’s App Review Guidelines ban overtly sexual material, and Google Play’s sexual content policy bans sexual content outright. NSFW AI sells on the web or not at all.
The card networks code adult AI output as adult content, merchant category code 5967, according to LegitScript. That puts it in the top tier of Visa’s Integrity Risk Program, where the acquiring bank needs Visa’s approval for the whole category and registers every merchant in it.
What happens in practice
- In May 2025, the AI platform Civitai lost card payments. Its own explanation was that processors “label generative-AI platforms high risk”, especially with user-made mature content.
- In April 2026, processors would only return to Civitai if mature content moved to a separate domain. Its mature side now takes crypto only.
- An AI image founder on Hacker News described an account closed after “6 days worth of sales”. An AI companion builder said payment processor compliance was harder than the model or the interface.
Specialist adult billers will take the risk at a price: about 10.8% to 15.5% of each sale, reserves held for six months, and underwriting that asks for your moderation design, prompt and output filters, age assurance plan and token terms before the first payment. However careful your app is, someone else holds your revenue, and that someone can decide your product has the wrong shape.
How Railbed fixes it
Railbed is card checkout that never holds your money. Users buy credits and memberships with the card they already have, and each sale settles as USDC straight to a wallet you control, usually minutes after they pay. Nothing is held back from your sales, and there’s no balance for anyone to freeze when your app takes off.
| What goes wrong today | With Railbed |
|---|---|
| Processors reject adult AI, or reclassify your app once sales grow | No underwriting and no application to pass. Money you’ve been paid is already in your wallet |
| Card checkout taken away, or mature content pushed to a crypto-only side | Users keep paying by card, in the same app. You receive USDC |
| Disputes over token packs and renewals count against your chargeback ratio | Settled sales can’t be pulled back from your wallet. Disputes go to the card provider that charged the card |
| Weeks of underwriting documents before the first sale | Sign up with an email, your website and a payout wallet, and test the whole flow tonight |
| App stores won’t list NSFW apps | Sell from your web app or PWA, with a hosted checkout or one embedded in your page |
| One acquiring bank decides which users’ cards go through | Smart Routing sends each user to the card provider most likely to approve them |
An independent, licensed card provider charges the user’s card and buys USDC with it, and the USDC is forwarded to the Polygon wallet you saved in Railbed. Nobody in that chain can recall it afterwards. If a user disputes a credit purchase, the dispute is between their bank and the card provider that charged the card, and nothing comes out of your wallet.
Adult AI and the rules around it, year by year
Adult AI has met two kinds of pressure at once. Payment companies narrowed what they would carry, and lawmakers began writing rules aimed at AI companions in particular. The dates below are the ones an adult AI founder runs into most often.
- Apr 2021
Mastercard requires documented age and identity checks for everyone depicted in adult content, and review before publication.
- Apr 2025
Italy’s data protection authority fines the maker of the Replika companion €5 million, finding no age verification system.
- May 2025
Card payments stop at Civitai, an AI platform with user-made mature content.
- Sep 2025
The FTC orders seven companies to explain how their AI companions make money and protect children.
- Oct 2025
California’s governor signs SB 243, the companion chatbot law, with damages of at least $1,000 per violation.
- Nov 2025
New York’s AI companion safeguards take effect on 5 November, with a reminder every three hours that the user is talking to AI.
- Jan 2026
Ofcom opens an investigation into the age checks of an AI character companion service.
- Apr 2026
Processors agree to return to Civitai only if mature content moves to a separate domain.
- Aug 2026
The EU AI Act’s transparency duties apply: a chatbot must tell people they are talking to AI unless it is obvious.
Two things follow. The payment side of an adult AI app is fragile in a way the product side isn’t: an app can do everything the law asks and still lose its checkout. And the legal side is getting more specific each year, so the work of keeping an app lawful grows whichever payment company you use.
Which checkout fits an AI app
Most adult AI apps need two ways to take a card: a checkout their own code opens when a user buys credits, and a simpler one for memberships or one-off offers. Pick by what you sell, not by what you could build.
| 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, with the user’s ID as your reference | One API call when the user taps Buy, and one webhook handler that adds the credits |
| Monthly or yearly memberships | A pricing table, on its own page or embedded in yours | Nothing to start. Switch access on from the dashboard, or from the webhook later |
| A one-off offer, a custom character or a commission | An invoice, sent by email or shared by link or QR code | Nothing. Create it in the dashboard |
| A buy button on your landing page | A buy button or embedded widget | Paste the snippet into your page |
Every one of them ends the same way: the user pays on the card provider’s page, the payment settles to your wallet, and your server hears about it from the same signed payment.paid event. Start with a pricing table if you want to sell tonight, and move credit packs to checkout sessions when you want them added without anyone touching the dashboard.
How a sale works
A user taps “Buy credits” or “Upgrade” in your app. Your server asks Railbed for a checkout session with the amount, currency and your own reference.
The checkout opens and the user enters an email address. Smart Routing sends them to the card provider most likely to approve their card, based on their country, the amount and the currency.
The user pays on the provider’s page. The provider decides whether to ask for identity details. Small purchases often need little or none, and Smart Routing tries the providers least likely to ask first.
The provider buys USDC with the card 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
payment.paidto your webhook, signed. Your server credits the account once, keyed on the event ID, and the checkout returns the user to your app.
Build and test all of it in Test mode, where payments are simulated and no card is charged.
The laws written for AI companions
Selling an adult AI app is lawful in most places, but since 2025 several governments have written rules aimed at AI companions and at AI that can produce explicit material. They bind you as the operator, whichever payment company you use. What each one says, in its own words:
- California. SB 243, signed on 13 October 2025, defines a companion chatbot as an AI system that gives “adaptive, human-like responses” and can “sustain a relationship across multiple interactions”. Operators must show a “clear and conspicuous notification” that the chatbot is “artificially generated and not human” where a reasonable person would be misled, keep a protocol that refers users who express suicidal ideation to crisis services, and, for users they know are minors, take reasonable measures to stop the chatbot producing sexually explicit visual material. A person harmed by a violation can sue for the greater of actual damages or $1,000 per violation.
- New York. General Business Law Article 47 took effect on 5 November 2025. The governor’s office says operators must detect signs of suicidal ideation or self-harm and direct users to crisis services, and must remind users they are not talking to a human “every three hours of continued companion use”. The Attorney General enforces it.
- European Union. Article 50 of the AI Act has applied since 2 August 2026. The European Commission’s guidance says providers of chatbots, AI agents and avatars must tell people they are interacting with AI “from the start of the first interaction”. Providers of generative AI must also mark AI-made images, audio and video in a machine-readable way, with a grace period to 2 December 2026 for systems already on the market before August. Fines can reach 15 million euros or 3% of worldwide turnover.
- United Kingdom. Ofcom says the Online Safety Act covers services that publish pornographic images, video or audio “including via chatbots”, and that they must use highly effective age assurance. In January 2026 it opened an investigation into an AI companion service’s age checks. Ofcom can fine up to £18 million or 10% of qualifying worldwide revenue, and in the most serious cases can ask a court to require payment providers to withdraw their services.
- Italy. The data protection authority fined Replika’s maker €5 million in April 2025, finding among other things a “failure to set up users’ age verification systems”.
- United States, nonconsensual images. The Take It Down Act’s removal duties have applied since 19 May 2026. The FTC’s guidance says a covered platform must remove a reported intimate image, including an AI-made “digital forgery”, within 48 hours of a valid request.
In the United States, the FTC has also asked seven chatbot companies how they “monetize user engagement”, develop characters and protect children. That inquiry is a study, not a rule, but it shows where regulators are looking.
None of this is legal advice, and these laws change. Which of them reach your app depends on where your users are and what the app does. Following them is your job, as it would be with any processor.
What the age field at checkout does, and what it doesn’t
A Railbed checkout can ask the buyer for a date of birth and refuse anyone under a minimum age you choose: 13, 16, 18, 21 or 25. A buyer who gives a younger age is told they can’t buy before anything is charged. It records what the buyer says; it is not an identity check.
That distinction matters for adult AI. Ofcom’s guidance on highly effective age assurance lists methods such as photo ID matching, facial age estimation and credit card checks, and says plainly that “self-declaration of age” is not highly effective. If the law where your users are asks for real age assurance, it belongs at your app’s door, before any explicit content is shown, and the minimum age at checkout is a second line, not the first.
Before you take your first credit purchase
Nothing here needs an application. It is the short list an adult AI founder gets right once, so the first paid pack lands in the right account and the app stays on the right side of the law.
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.
Credit packs in real money. Decide your packs and show each price in your currency. Card providers have minimums, the smallest about $2, and around $10 or more gives users the widest choice of providers.
A webhook that runs once. Add credits when the signed
payment.paidevent arrives, and record the event ID so a retried delivery never adds them twice.An age gate at your door. Put the check the law asks of you in front of the app itself. Add a minimum age to the checkout as well if you want a second line.
The disclosures your users’ laws require. If you serve California, New York or the EU, show the AI disclosure, keep a crisis referral protocol and publish what the law asks you to publish.
A takedown route. Give people a way to report an image of themselves, and act on it fast. The Take It Down Act gives covered platforms 48 hours.
A refund rule for unused credits. Write down what you refund and how, because Railbed can’t reverse a settled payment for you.
A run in Test mode. Buy each pack in Test mode and watch the credits appear before you take a Live payment.
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. The fee is locked when the user starts paying. 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. To pay your model and hosting bills from a bank account, send USDC from your wallet to any exchange or off-ramp you use and withdraw it there. The guide to moving money to your bank shows each step. Many AI teams keep part of their revenue in USDC.
Refunds are your call. Railbed can’t reverse a settled payment, so if you refund unused credits, send USDC back or agree another arrangement with the user.
Refunds, unused credits and disputes
Credit apps get two kinds of complaint: a user who bought a pack and didn’t use it, and a user whose card was used by someone else. Both are handled differently once the money is already yours.
A refund is something you send, not something a processor takes from you. Decide whether unused credits can be refunded, for how long, and whether spent credits ever can, and say so beside your packs. When you refund, return the USDC or agree another arrangement, and take the credits back in your app.
A dispute goes to the card provider that charged the card, under that provider’s terms and the card networks’ rules, and nothing comes out of your wallet. At a conventional processor the same dispute counts against you. Since 1 April 2026 Visa treats a ratio of fraud reports and disputes above 1.5% of a merchant’s settled card-not-present transactions as excessive, and merchants in its monitoring programme pay $8 for each disputed or fraudulent transaction.
None of that makes a refund policy optional. A user who can get money back from you quickly has little reason to ask their bank, and a card provider may decline future payments from a user who disputes.
No underwriting, no application to pass
Railbed has no underwriting and no application to pass, and there’s no moderation design to submit. The acceptable use policy keeps only the limits the law puts on Railbed itself, and for AI apps one of them matters: no sexual content involving minors, real or generated, and nothing that sexualises a real person without their consent, including tools that “undress” photos or swap real faces into explicit scenes.
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.
Running Railbed beside the biller you have
You don’t have to leave a biller that works. Nothing about Railbed is exclusive, and many apps add it as a second way to pay by card before they decide anything else. Three places it helps from the first week:
- As the fallback. When your main checkout declines a card, offer Railbed on the same screen. A user turned away by one bank’s fraud screen is often approved by a different card provider.
- For the users your biller won’t take. If a country, a feature or a price point sits outside what your biller allows, send those purchases to Railbed and leave the rest where they are.
- As the spare. An app with two working checkouts keeps selling on the day one of them asks for a fresh review.
Use the same reference in both, and let both checkouts’ paid events call the same code that adds credits. Your app then never needs to know which one took the money.
Railbed compared with an adult AI merchant account
| Adult or high-risk merchant account | Railbed | |
|---|---|---|
| Approval | Days to weeks of underwriting | Under a minute |
| To apply | Moderation design, prompt filters, age assurance plan, token terms, statements | An email, your website and a payout wallet |
| Pricing | About 10.8–15.5% at specialist adult billers, plus card-network registration fees | The card provider’s fee, a 1% network fee and the Railbed fee from 0.9%, all shown before payment |
| Payouts | On the biller’s cycle | Each sale, to your own wallet, as soon as it settles |
| Chargebacks | A fee for each, and a Visa monitoring threshold of 1.5% of transactions since April 2026 | Settled sales can’t be pulled back. Disputes go to the card provider |
| Reserve | Held for six months at specialist adult billers | Nothing is held back from your sales |
| When sales jump | A fresh review, with your balance held | Settled funds are already yours |
| Mature features | Can be pushed to a separate domain without card checkout, as Civitai’s were in 2026 | Card checkout for the same app |
When Railbed is not the right fit
Railbed suits an adult AI app that sells credits or passes on the web and wants the money in its own wallet. It is the wrong tool in a few cases, and it is better to know them before you build:
- Your model depends on silent renewals. Railbed never charges a card by itself. If your revenue plan assumes monthly charges that nobody has to approve, passes and invoices are a different product, and some users will let them lapse.
- You want the payment company to handle age assurance. Railbed’s minimum age records what the buyer says. If the law asks you for highly effective age checks, you need an age assurance service at your app’s door.
- You sell tiny amounts. Card providers have minimums, the smallest about $2, so a pack of a few cents has to become a bigger pack.
- You need an app store listing. Apple and Google ban sexual content in apps, whoever processes the payments. Railbed works for web apps and PWAs.
- You never want to hold USDC. Sales settle as USDC to your wallet. Moving it to a bank is a step you take yourself, through an exchange.
Words worth knowing
The terms an adult AI founder meets when looking for a way to take cards.
- Companion chatbot
- California’s term for an AI system with human-like responses that can sustain a relationship across many conversations. SB 243 sets duties for anyone who offers one to users in the state.
- Merchant category code 5967
- The card networks’ code for direct marketing of adult content, where adult AI output is placed. It puts a merchant in the networks’ highest-risk tier.
- Highly effective age assurance
- Ofcom’s standard for age checks under the UK Online Safety Act. Photo ID matching and facial age estimation can meet it; self-declaration of age can’t.
- Digital forgery
- The Take It Down Act’s term for an intimate image made or altered with software or AI. A covered platform must remove a reported one within 48 hours.
- Credit pack
- A fixed number of credits bought with one payment and spent inside the app. With Railbed, each pack is its own payment, and nothing renews by itself.
- 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 a merchant’s sales a processor holds back against future disputes. Specialist adult billers hold reserves for six months.
Questions
Stripe or PayPal closed my AI app. Can I use Railbed?
Yes. A past closure or a MATCH listing doesn’t rule you out, and there’s no processing history to send. Railbed has no underwriting and no application to pass, so you can be live today.
Is my AI companion app “adult content”?
If it can produce sexual content, the card networks and most processors treat it as adult content. Railbed has no underwriting and no application to pass, so the label doesn’t change how you set up your checkout.
Do my 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 small credit packs often go through with little or no check. Large or unusual payments may still need one.
What happens if a user disputes a credit purchase?
The dispute goes to the card provider that charged the user’s card, and a settled payment can’t be pulled back out of your wallet.
Can I sell monthly memberships?
Yes, as passes of any length. Railbed doesn’t charge cards automatically, so a new month is a new payment the user chooses to make. Remind users in your app when a pass is about to end.
How do I add credits to a user’s account automatically?
Listen for the signed payment.paid webhook and credit the account once per event ID. You can simulate paid, held and failed payments in Test mode before you go live. The developer docs have working examples.
Can I offer a free trial?
Yes. Let users try your app for free, then sell their first pack through Railbed. Railbed never charges a card without the user paying on the spot, so a free trial can’t turn into a charge they didn’t expect.
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.
Is it legal to run an NSFW AI chatbot?
In most places, yes, for adults. The laws that apply set conditions rather than bans: California and New York require AI disclosures and crisis protocols for companions, the EU requires chatbots to say they are AI, and the UK requires highly effective age checks for services that produce pornographic content. Railbed’s acceptable use policy refuses sexual content involving minors, and anything that sexualises a real person without their consent.
Does California’s companion chatbot law apply to my app?
SB 243 applies to anyone who makes a companion chatbot platform available to a user in California. It covers AI with human-like responses that can sustain a relationship across conversations, and leaves out customer service bots and some game characters. Whether your app is covered is a question for your lawyer.
Do I need age verification for an AI companion app?
It depends on where your users are and what the app shows. In the UK, a service that can produce pornographic content needs highly effective age assurance, and self-declaring an age doesn’t count. Railbed’s checkout can refuse buyers under a minimum age, but it records what they say and is not an age check.
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, as a fallback for declined cards or for the users your processor won’t take, so one decision can’t stop every sale.
What is the smallest credit pack I can sell?
Card providers set minimums, and the smallest is about $2. A pack of around $10 or more gives users the widest choice of providers, which is why a bigger pack usually sells better than a very small one.
Sources
- Stripe: Prohibited and restricted businesses, last updated 22 September 2026, checked 5 October 2026
- PayPal: Acceptable use policy, checked 5 October 2026
- Square: Payment terms, unsupported industries, last updated 30 July 2026, checked 5 October 2026
- Apple: App Review Guidelines, last updated 8 June 2026, and Google Play: Sexual content and profanity, checked 5 October 2026
- LegitScript: Adult, escort and dating merchants and the VIRP updates, 16 February 2026
- Visa: Visa Integrity Risk Program guide, April 2023
- Civitai: Credit card payments pausing, 20 May 2025, and Two front doors, 9 April 2026
- Hacker News: an AI image founder on account closure, 2 August 2023, and an AI companion builder on compliance, 28 February 2026
- The Payments Edge: adult processor pricing compared, compiled June 2026
- European Commission: Key principles on in-game virtual currencies, March 2025
- Visa: Visa Acquirer Monitoring Program, and Chargeflow on the 1.5% threshold from April 2026, updated 3 September 2026
- Mastercard: Protecting our network, protecting you, 14 April 2021, checked 20 November 2026
- Law Library of Congress: Italian authorities sanction maker of Replika chatbot, 4 September 2025, checked 20 November 2026
- Federal Trade Commission: FTC launches inquiry into AI chatbots acting as companions, 11 September 2025, checked 20 November 2026
- California Legislature: SB 243, Companion chatbots, chaptered 13 October 2025, checked 20 November 2026
- Governor of New York: AI companion safeguard requirements now in effect, 10 November 2025, checked 20 November 2026
- Ofcom: Ofcom investigates AI companion chatbot service, 15 January 2026, checked 20 November 2026
- Ofcom: AI chatbots and online regulation, what you need to know, 18 December 2025, checked 20 November 2026
- Ofcom: Age checks to protect children online, 16 January 2025, checked 20 November 2026
- European Commission: Transparency obligations under Article 50 of the AI Act, last updated 24 July 2026, checked 20 November 2026
- Federal Trade Commission: Complying with the Take It Down Act, 8 May 2026, checked 20 November 2026
- Merchant Risk Council: Stricter VAMP ratio thresholds are now in effect, 1 April 2026, checked 20 November 2026
Last updated .
Paid500 credits, settled to your wallet$20.00
Build the companion.
Keep what users pay.
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