Add card payments to your platform without becoming a payfac.

Embedded payments now earn some vertical software companies more than the software does, but taking them on means a sponsor bank, liability for your customers’ losses and a restricted list that turns some customers away. With Railbed each customer holds their own account and wallet, and your software creates their checkouts and invoices through the API.

  • No sponsor bank needed
  • Each customer's own wallet
  • One API, every account

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 a vertical SaaS platform add card payments without becoming a payfac?

Yes, if each customer holds their own account. A payment facilitator signs up sellers on behalf of an acquirer or receives their settlement, and takes on registration, liability and onboarding duties. With Railbed each of your customers signs up and saves their own payout wallet, and your software creates their checkouts and invoices through the API with their key. Sales settle to the customer’s wallet. Railbed doesn’t split payments, so no part of a sale passes through your platform.

Why platforms want payments, and what it takes

Software for one trade, whether it books a salon’s chairs, dispatches a plumber’s vans or runs a landlord’s units, sits exactly where that trade’s money changes hands. Adding payments looks like the obvious next product, and for many platforms it has become the biggest one.

an entity that performs either one of these functions is considered a PF, even if they don’t perform both functions

Visa
Beyond the Acquirer

The numbers explain the rush. Stripe, writing after its 2026 Sessions conference, counted more than 16,000 platforms on its network and reported that median payments adoption rose from 27% in 2024 to 40% in 2025, with the top platforms above 80%. It quoted Tidemark’s estimate that each customer who adopts embedded payments adds about $4,200 a year in recurring revenue. Toast, the restaurant platform, shows how far it can go: in 2025 it booked $5,037 million from financial technology solutions and $936 million from subscriptions, more than five dollars of payments revenue for every dollar of software.

Behind that revenue is a set of obligations the card networks write down. Visa’s guide to acceptance entities, Beyond the Acquirer, defines a payment facilitator as a third party that can sign a merchant agreement with a seller on an acquirer’s behalf, or receive settlement on the seller’s behalf, and adds that “an entity that performs either one of these functions is considered a PF, even if they don’t perform both functions.” Once you are one, “all Visa requirements apply equally to a sponsored merchant, as if the sponsored merchant was contracted directly with an acquirer”, and the acquirer “remains responsible for the acts and obligations” of everyone between it and the seller. That is why acquirers ask so much of the platforms they sponsor.

The platform products built to spare you that work move the same duties around rather than removing them. Stripe Connect’s risk documentation says the platform “is always responsible for its own negative balances”, and that responsibility for connected accounts’ negative balances “can belong to your platform or to Stripe, depending on your integration”. Where it’s the platform’s, Stripe “holds funds in your platform account in reserve” while it collects. And each customer you onboard becomes a Stripe user in its own right: the Connected Account Agreement incorporates the Stripe Services Agreement, so the prohibited and restricted businesses list applies to your customers one by one.

What embedding payments asks of a platform

  • A sponsor. A bank or acquirer that agrees to take your customers’ card sales, and that answers to the card networks for you.
  • Registration and security. Visa’s registration programme checks financial conditions and data security, including PCI DSS, for the entities in the chain.
  • Onboarding every customer. Collecting identity and business details for each seller and checking them, before their first sale and again when they grow.
  • Liability for losses. Negative balances, chargebacks and fraud at your customers’ businesses can land on your balance sheet.
  • A licence question. Visa notes that local law may require a payment facilitator to hold a money transmission licence to receive and pass on settlement funds.
  • A list you don’t control. Your partner’s restricted businesses apply to each customer, so some of the trades your software serves can’t take payments through it.

How Railbed works for a software platform

Railbed approaches the problem from the other side. Instead of your platform becoming the merchant of record for its customers’ payments, each customer opens their own Railbed account, saves their own payout wallet, and gives your software an API key. Your software creates their checkout sessions and invoices and listens for their payments. The money never passes through you, or through Railbed: each sale settles as USDC straight to the customer’s wallet, usually minutes after their buyer pays.

What goes wrong todayWith Railbed
A sponsor bank, registration and a long build before the first paymentEach customer signs up with an email, their website and a payout wallet. No underwriting and no application to pass
Your balance answers for every customer’s chargebacks and negative balancesSettled sales can’t be pulled back from the customer’s wallet. Card disputes go to the provider that charged the card
A partner’s restricted list turns some of your customers awayRailbed’s acceptable use policy holds only the limits the law puts on Railbed itself
Reserves held on your platform account while losses are collectedNothing is held back from your customers’ sales, and nothing sits in a platform balance
Onboarding and checking every seller yourselfEach customer accepts Railbed’s terms in their own name

An independent, licensed card provider charges the buyer’s card and buys USDC with it, and the USDC is forwarded to the Polygon wallet your customer saved in Railbed. Railbed checks that the right amount reached the right wallet before it marks the payment paid, then sends a signed webhook to the endpoint your software registered for that account.

What Railbed is, and what it isn’t

It’s worth being exact, because the words in this market are slippery and a platform’s lawyers will ask.

Railbed is checkout and invoicing for each of your customers. Every customer is a Railbed merchant in their own right: their own sign-up, their own team, their own payout wallet, their own secret keys, their own dashboard and their own records. Your software works on their behalf with a key they create and can revoke.

Railbed isn’t a payment facilitator product for you. You don’t sign up sellers on anyone’s behalf, there are no sub-merchant accounts under a master account, and no settlement passes through a platform balance. Whether that keeps your business outside any particular rule is a question for your own adviser, but the money flow is simple to describe: buyer to card provider, card provider to your customer’s wallet.

Railbed doesn’t split payments or pay out. There’s no application fee taken from each sale for the platform, no transfer of part of a payment to a second wallet, and no payouts to third parties. If you charge customers for your software, you bill them for it yourself, and you can bill them through your own Railbed account.

Railbed has no recurring billing. Each payment is one payment. A customer’s buyer pays a deposit, an invoice or a package price; nothing charges a card again on a schedule.

Embedded payments, year by year

Embedded payments went from a side product to the centre of vertical software’s business model in a few years. The record below is the one a board deck usually leaves out: the rules arrived alongside the revenue.

  1. 2023

    Toast books $3,189 million from financial technology solutions and $500 million from subscriptions.

  2. 15 Feb 2024

    Visa publishes its guide to acceptance entities: payment facilitators, marketplaces and the duties each carries.

  3. 2024

    Median payments adoption across vertical SaaS platforms on Stripe stands at 27%.

  4. 2025

    Adoption reaches 40%, and Toast’s payments revenue reaches $5,037 million.

  5. 1 Apr 2026

    Visa lowers the fraud and dispute ratio at which it counts a merchant as excessive, from 2.2% to 1.5%.

  6. Nov 2026

    Thirty-one states have enacted the model Money Transmission Modernization Act in full or in part.

  7. 22 Sep 2026

    Stripe updates its prohibited and restricted businesses list, which binds every connected account.

Two things stand out. The revenue is real and growing, so the pressure on every vertical platform to add payments will keep rising. And the duties grew at the same time: a lower dispute threshold at Visa applies to every seller you sponsor, and a growing number of states share one model law for anyone who moves other people’s money.

What your customers sell, trade by trade

Vertical platforms differ in what their customers bill for, but almost all of it is one of three shapes: a deposit before the work, an invoice after it, or a fixed price paid up front. Railbed’s checkout sessions and invoices cover each. Some examples by trade:

  • Field service. A heating company takes a $149 tune-up when the job is booked, sends an invoice for the repair with a deposit as the smallest first payment, and sells a yearly maintenance visit paid up front.
  • Salons, spas and studios. A booking deposit that holds the chair, a prepaid package of ten sessions, a class pack sold from the studio’s schedule page.
  • Property management. Application fees, a repair charged back to a tenant, a parking or storage fee, sent as invoices with due dates and reminders. Deposits and rent held in trust follow their own rules.
  • Clinics outside insurance. A self-pay visit, a treatment plan in parts, a product sold at the front desk’s online shop. Insurance and HSA billing stay where they are.
  • Contractors and installers. A deposit on acceptance of a quote, milestone invoices as the work goes on, and a final balance with any change orders.
  • Event and venue software. A table deposit, a private booking in two payments, a package with extras.
  • Shops on your commerce platform. Online orders paid at checkout, including the trades a processor won’t take.

Every amount must be one a card provider can take, the smallest about $2, and the smallest amounts have the fewest providers. A single checkout or invoice goes up to 100,000.00; larger sales are split.

How a sale works

  1. A homeowner books a furnace tune-up on a heating company’s booking page, which your software runs.

  2. Your server creates a checkout session in that company’s Railbed account with the company’s key, with your job id as the reference.

  3. Railbed’s checkout asks the homeowner for an email and any details the company turned on. Smart Routing picks the card provider most likely to approve this buyer.

  4. The homeowner pays on the provider’s page, in a new tab. The provider decides whether to ask for identity details, and Smart Routing tries the providers least likely to ask first.

  5. The provider buys USDC with the card payment, and it’s forwarded to the heating company’s wallet on Polygon. Railbed checks the amount and the wallet before it marks the payment paid.

  6. Railbed sends the payment.paid webhook to the endpoint your software registered for that account. Your job board marks the visit paid and the technician sees it on the schedule.

Build all of it against Test mode first. Payments are simulated, no card is charged, and Test webhooks reach your server as real signed requests.

Building it: keys, sessions and webhooks for each account

The integration is the ordinary Railbed API, called once per customer account. What changes is that your software holds many keys instead of one.

If your customers would rather not use the API at all, they can build a checkout page, pricing table or invoice in their own Railbed dashboard and paste its link or embed code into the pages your software hosts.

Customers your payments partner won’t take

Every vertical has trades a processor won’t onboard, and a platform with an embedded payments partner inherits that list. A commerce platform for convenience stores meets vape and smoke shops. Software for supplement brands meets kratom and kava. Booking software meets psychics, dating coaches and adult performers. A platform that sells to gun shops, CBD stores or game server hosts runs into the same wall. Your software works for them; your payments partner doesn’t.

Those customers usually end up with a second processor of their own, at high-risk rates, with a reserve, outside your software. Your platform loses the payments revenue and part of the reason they chose you. Railbed gives you a way to keep them inside the product: the customer signs up for Railbed themselves, and the same integration you built for everyone else creates their checkouts. Railbed’s acceptable use policy holds only the limits the law puts on Railbed itself, and Railbed stops new payments only when the law requires it. You can keep your main payments partner for most customers and offer Railbed to the rest.

Support, disputes and who answers the phone

When payments live inside your software, your support team hears about them first. It helps to know in advance which questions are yours, which are your customer’s and which belong to the card provider.

Before you add Railbed to your platform

A short list to get right once, before the first customer connects.

  • Your own Test account. Sign up yourself and build the whole flow in Test mode: sessions, invoices, webhooks and a revoked key.

  • A connection screen. Give customers one place to paste a key, show whether it’s Test or Live, and let them disconnect.

  • Key storage. Store keys encrypted and server-side only, and never log them. Treat a leaked key as revoked.

  • Idempotent webhooks. Record each event id once, map each payment to your own record by reference, and never undo a paid job on a later event.

  • Clear words for your customers. Tell them in your settings screen that the money goes to their own wallet as USDC, that refunds are theirs to send, and that Railbed has no recurring billing.

  • A rule for regulated money. Decide which charges your vertical may collect this way, and keep trust money, deposits held for others and insurance billing out of it.

  • A support playbook. Write down the answers to the five questions above so your team gives the same ones.

Running Railbed beside your payments partner

If you already have a payments partner, you can keep it. Three ways the two sit together:

  • For the customers your partner declines. Offer Railbed in the same settings screen, so the trades on your partner’s restricted list still take payments inside your software.
  • For buyers your partner’s checkout declines. Show Railbed as a second card option when the first checkout fails. A buyer turned away by one fraud screen is often approved by a different card provider.
  • For a customer who wants their own wallet. Some business owners would rather hold their sales themselves than wait for a payout schedule.

Keep one job or order id across both, so your reports read the same whichever checkout took the payment.

Refunds and disputes

A paid booking or invoice has settled to your customer’s wallet, so a refund is something the customer sends, not something a processor takes back. For a cancelled appointment or a job that didn’t go ahead, the customer sends the USDC back or agrees another arrangement with their buyer, and can record the refund on the order through the API.

A dispute works differently too. The buyer’s bank raises it with the card provider that charged the card, under that provider’s terms and the card networks’ rules, and nothing comes out of your customer’s wallet or your platform’s balance. There’s no chargeback fee and no chargeback ratio for anyone to manage. That doesn’t make a refund policy optional for your customers: a buyer who can get their money back quickly has little reason to ask their bank.

What stays your responsibility, and your customers’

Your platform remains responsible for your software: how you store keys, what your screens tell customers, the data you hold about their buyers and the privacy rules that apply to it. Your customers remain responsible for their businesses: what they sell, their prices, their refunds, their licences and permits, the tax on their sales and anything their trade’s own regulator asks of them. Railbed’s acceptable use policy holds only the limits the law puts on Railbed itself, and those apply to every customer’s account.

Fees and getting paid

Railbed shows every fee before anyone pays, and all of them come out of the USDC that arrives in your customer’s wallet. The card provider takes its own fee and exchange spread, shown to the buyer on its page. Then come a 1% network fee and the Railbed fee, from 0.9%, shown in your customer’s dashboard and locked when the buyer starts paying. There’s no setup fee, no monthly fee and no chargeback fee, for your customers or for you.

The buyer pays the price your customer set. A furnace tune-up at $149 is a $149 payment, and what reaches the heating company’s wallet is that amount less the fees above, usually minutes after the homeowner pays. To pay suppliers or staff from a bank account, the company sends USDC from its wallet to any exchange or off-ramp it uses and withdraws it there.

No part of those payments reaches your platform, because Railbed doesn’t split them. What you gain is customers who can take payments inside your software, including the ones your partner turned away. Price that into your own plans, and bill for it yourself.

Railbed compared with a payments platform for platforms

Platform payments productRailbed
Who the seller signs up withThe provider, through your onboarding flowRailbed directly, in their own name
Where the money goesThe seller’s balance at the provider, then payouts to a bankThe seller’s own wallet as USDC, usually within minutes
Losses and negative balancesYours or the provider’s, depending on the integrationNobody’s balance: settled sales can’t be pulled back
Restricted tradesThe provider’s list applies to every sellerOnly the limits the law puts on Railbed
Revenue for the platformYour own pricing on top, plus per-account and payout feesNo share of each sale; bill for your software yourself
Recurring billingOften availableNone. Each payment is one payment
Card terminalsOften availableNone. Online checkout and invoices only

When Railbed is not the right fit

Railbed suits a platform whose customers take deposits, invoices and fixed-price sales online, and which wants to serve trades its payments partner won’t. It is the wrong tool in a few cases, and it is better to know them first:

  • Payments revenue is the plan. If your business case depends on a margin on every customer’s card sales, Railbed won’t provide it: it doesn’t split payments, so no part of a customer’s sale comes to you.
  • Your customers need card terminals. Railbed is online checkout. Counter and in-person card payments stay on a terminal provider.
  • Your customers bill monthly automatically. Railbed has no recurring billing, so memberships and monthly service plans charged by card on file stay elsewhere.
  • You pay people out. Marketplaces that collect from buyers and pay sellers, workers or landlords need payouts, which Railbed doesn’t make.
  • Your customers never want to hold USDC. Sales settle as USDC to each customer’s wallet, and moving it to a bank is a step they take themselves.

Words worth knowing

The terms a platform meets when it talks to a payments partner, a sponsor bank or a lawyer.

Payment facilitator
Visa’s name for a third party that signs sellers to merchant agreements on an acquirer’s behalf, or receives settlement for them. Doing either one makes a business a PF.
Sponsored merchant
A seller signed up through a payment facilitator, sometimes called a sub-merchant. Visa’s rules apply to it as if it had contracted with the acquirer directly.
Acquirer
The bank that contracts with merchants to take card payments and answers to the card networks for them and for everyone in between.
Payfac as a service
A provider that lets a platform offer payments without registering as a payment facilitator itself, usually with the platform carrying some of the risk.
Embedded payments
Card acceptance built into software a business already uses, so its customers pay without leaving the platform’s screens.
Payments adoption
The share of a platform’s customers who take payments through it. Stripe put the median at 40% for vertical SaaS in 2025.
Negative balance
What a seller owes after refunds, disputes or fees exceed its incoming money. Platform payments products assign the loss to the platform or the provider.
Money transmitter
A business licensed to accept money from one person and send it to another. US states license them, and federal rules exempt some payment processors.
KYB
Know your business, the checks a provider runs on a company before it can take payments: who owns it, what it sells, where it operates.
Restricted business
A trade a provider won’t serve, or serves only with approval. On a platform payments product, the provider’s list applies to each customer.

Questions

Can my platform offer card payments without becoming a payment facilitator?

With Railbed, each of your customers opens their own account and saves their own payout wallet, and your software uses their key to create payments. You don’t sign them up on anyone’s behalf and their money never reaches you. Whether that keeps your business outside a particular rule is a question for your adviser, but there’s no settlement in your hands.

Does Railbed split payments or pay my platform a fee from each sale?

No. Railbed doesn’t split payments, take an application fee for a platform or pay out to a second wallet. You bill customers for your software yourself, and you can do that through your own Railbed account.

How does a customer connect their Railbed account to my software?

They sign up with an email, their website and a payout wallet, create a secret key in Developers and paste it into your settings screen. A Full access key lets your software create sessions, invoices and webhook endpoints; revoking it disconnects you and removes the endpoints it added.

Who is liable when a buyer disputes a payment?

The buyer’s bank raises the dispute with the card provider that charged the card, under its terms and the card networks’ rules. Settled sales can’t be pulled back from your customer’s wallet, and nothing comes out of your platform’s balance, because there isn’t one.

Can I offer payments to customers Stripe Connect won’t onboard?

Often, yes. Connected accounts are bound by Stripe’s own prohibited and restricted businesses list. Railbed’s acceptable use policy holds only the limits the law puts on Railbed itself, so trades such as vape shops, CBD stores or kratom sellers can take payments through the same integration as everyone else.

Do my customers need to pass underwriting?

No. Each customer signs up with an email, their website and a payout wallet, with no underwriting and no application to pass. Railbed stops new payments only when the law requires it.

Can my software send invoices with deposits and part payments?

Yes. The Invoices API creates invoices with up to 50 lines, discount, tax, a due date and part payments with a smallest first payment, and can email them with their PDF. Invoice events tell your software when one is viewed, part paid or paid.

Does Railbed support recurring billing for my customers’ memberships?

No. Every payment is one payment. Your customers can sell prepaid packages, terms paid up front and invoices with reminders, but nothing charges a card again on a schedule.

Is there a card terminal for my customers’ counters?

No. Railbed is online checkout and invoicing. A customer with a counter can show a checkout page’s QR code for a buyer to pay on their phone, but in-person card payments stay on a terminal.

How do my customers get their money?

Each sale settles as USDC to the customer’s own wallet on Polygon, usually minutes after the buyer pays. To move it to a bank, they send it to an exchange or off-ramp they use and withdraw it there.

What are the API rate limits for a platform with many accounts?

Limits are per account and per mode: about 120 requests a minute and 12 session starts a minute. Each customer’s account has its own budget, so one busy customer doesn’t slow another.

Can my support team see my customers’ payments?

If a customer invites them. A Developer on a Railbed team handles keys, webhooks and integrations and reads records, but can’t change the wallet, settings or team. A Read only key also lets your software show payments in your own screens.

Will my customers’ buyers have to show ID?

Usually not, but the card provider decides. Smart Routing sends each buyer to the providers least likely to ask, and some may ask for light details such as a name, date of birth or address. Railbed can’t promise a buyer will never be asked for ID.

Sources

  1. Stripe: Five vertical SaaS insights from Sessions 2026, 11 May 2026, checked 20 November 2026
  2. Toast: Fourth quarter and full year 2025 financial results (SEC exhibit 99.1), February 2026, checked 20 November 2026
  3. Visa: Beyond the Acquirer, additional Visa acceptance entities, 15 February 2024, checked 20 November 2026
  4. Stripe: Risk and liability management with Connect, checked 20 November 2026
  5. Stripe: Connected Account Agreement, last modified 18 November 2025, checked 20 November 2026
  6. Stripe: Prohibited and restricted businesses, last updated 22 September 2026, checked 20 November 2026
  7. Merchant Risk Council: Stricter VAMP ratio thresholds are now in effect, 1 April 2026, checked 20 November 2026
  8. CSBS: Money Transmission Modernization Act, adoption status as of November 2026, checked 20 November 2026
  9. eCFR: 31 CFR 1010.100, general definitions, checked 20 November 2026
  10. Stripe: Connect pricing, checked 20 November 2026
  11. Toast: Fourth quarter and full year 2023 financial results (SEC exhibit 99.1), 15 February 2024, checked 20 November 2026

Last updated .

PaidA furnace tune-up, settled to your wallet$149.00

Their sale, their wallet.
Built into your software.

Set up in under a minute. Your first payment can settle today.

  • No sponsor bank needed
  • Each customer's own wallet
  • One API, every account

Moving a lot of volume? Talk to our team