Stripe Embedded Payments vs Fiat-to-Crypto Onramp
By Shawn Michael Thomas II, Founder of Simple Easy Transactions · Published ·
What's the difference between an embedded payment and an embedded crypto onramp? An embedded payment is a customer paying my business for something I sell, and the money lands in my own Stripe account. An embedded crypto onramp is a customer buying cryptocurrency from Stripe, and the coins land in the customer's own wallet; my business isn't the seller. They can look alike on the page, but they're different Stripe products with different approvals, and I keep their records separate.
AT A GLANCE
Embedded payment vs Crypto onramp.
| Question | Embedded payment | Crypto onramp |
|---|---|---|
| What the customer buys | Your product or service | Cryptocurrency, delivered to their wallet |
| Who the seller is | Your business | Stripe |
| Where the money goes | Your Stripe account | Stripe, which delivers the crypto |
| Identity checks | Only what the payment itself needs | Stripe verifies the buyer and screens for sanctions and fraud |
| Approval you need | A Stripe account that can accept payments | A separate Stripe onramp application |
| What proves the outcome | Stripe's signed payment webhook | Stripe's onramp session updates and delivery status |
HOW EACH ONE WORKS
How each one works.
In plain terms: fiat money is government-issued currency, such as US dollars. An onramp is the service that exchanges it for cryptocurrency. A crypto wallet is where the purchased cryptocurrency is delivered and held, and whoever controls access to the wallet controls what is in it. A network is the blockchain the cryptocurrency moves on, and the receiving wallet must support the network it is sent on.
Stripe's fiat-to-crypto onramp is a separate product from Stripe payments, with its own application and approval. In the onramp, Stripe runs identity verification and fraud checks, quotes the price and network fees, charges the customer, and delivers the cryptocurrency to the customer's wallet. Stripe's documentation describes Stripe as the merchant of record for onramp purchases. The business that hosts the onramp never takes custody of the money or the coins, and availability depends on where the customer lives.
An embedded payment is the opposite arrangement. The business sells its own product or service, it is the merchant of record, and the payment settles to its own Stripe account, where it handles refunds and disputes.
A business can offer both, but they should be built as two separate paths: payment events drive orders, and the onramp's own session updates report crypto purchases. Mixing the two makes it impossible to say which outcome a given event proves.
FIELD NOTES
What I've learned building this.
- This site runs both. Its checkout takes payments for SET's own services, and a separate onramp page lets an eligible business buy crypto from Stripe.
- The two share nothing but Stripe's script. Payment events and onramp events are handled by separate code, so a crypto purchase can never be mistaken for a paid invoice, or the other way round.
- The onramp page asks for agreement to my terms before any session exists, the same way my checkout does.
HOW TO CHOOSE
How I'd choose.
- Choose embedded payments when the customer is buying your product or service.
- Choose the onramp when the customer wants to buy crypto for their own wallet and your business has Stripe's onramp approval.
- Build both as separate paths when your app needs both, such as selling a service and letting users fund a wallet.
SOURCES
Where these facts come from.
Sources checked on . Providers change their products and rules, so the linked pages are the final word.