White-Label vs Embedded Payments with Stripe
By Shawn Michael Thomas II, Founder of Simple Easy Transactions · Published ·
Is a white-label payment platform the same as an embedded payment integration? No. White-label is about who owns the platform: you resell a vendor's payment product under your name, and the vendor usually holds the merchant account underneath. Embedded is about where the payment appears: inside your own page instead of on a provider's. You can have either without the other. The first question I'd ask is who holds the merchant account and your customers' saved cards, because that decides what leaving costs.
AT A GLANCE
White-label vs Embedded.
| Question | White-label | Embedded |
|---|---|---|
| What it describes | Who owns the payment platform | Where the payment appears |
| Customers see your brand | Yes, on the vendor's product | Yes, on your own page |
| Who holds the merchant relationship | Usually the vendor | Not decided by this choice |
| Work to set up | Mostly configuration | A spot on your page and a server step |
| Affects what leaving costs | Yes, a lot | No |
| Affects the checkout experience | Only indirectly | Directly |
HOW EACH ONE WORKS
How each one works.
In payments, white-label usually means a platform or payment-facilitator product that you rebrand as your own. The vendor often holds the main merchant account, sets the processing price and stores your customers' payment methods, so leaving can mean asking customers to re-enter their cards unless the vendor agrees to move the data.
Stripe Connect separates those questions. A platform signs up each business as its own connected account, and with direct charges the connected business is the merchant of record: its name appears on the customer's statement, payments settle to its own Stripe account, and the platform can take a fee on each payment.
If your concern is the customer's experience, that's the embedded question, and you can answer it inside your own Stripe account without a white-label vendor. If it's speed with no engineers, that's the white-label question. If it's long-term control, ask who holds the merchant account and where the saved cards live.
FIELD NOTES
What I've learned building this.
- SET's platform is built the opposite way from most white-label products. Each client business gets its own Stripe account, is the seller on its own sales, and its customers' payments settle straight into that account.
- My fee is taken per payment as an application fee that Stripe shows in the payment record, and I return it on refunds and on disputes the client loses, so a client can see exactly what the platform earned.
- If a client leaves, their Stripe account keeps working as an ordinary Stripe account. I only remove it from my platform.
HOW TO CHOOSE
How I'd choose.
- If you care most about the checkout experience, answer the embedded question. You may not need a white-label vendor at all.
- If you need to launch fast with no engineers, answer the white-label question, and check that the vendor supports an embedded checkout.
- If you care about long-term control, find out who holds the merchant account and the saved cards before you sign.
SOURCES
Where these facts come from.
Sources checked on . Providers change their products and rules, so the linked pages are the final word.