The three models, what the platform builds, who handles what, PCI scope and when card-present payments enter the picture.
Embedded payments puts acceptance inside your software. The platform owns the experience and a provider moves the money. You build checkout, payment requests, tokenization, onboarding, reporting and reconciliation. The model you choose decides how much risk and operations you take on.
Embedded payments puts payment acceptance inside your software, so your customers take and receive payment without leaving your product. The platform owns the experience. A provider moves the money. What sits between them is the engineering: checkout, payment requests, merchant onboarding, reporting and reconciliation.
| Model | How it works | What you build |
|---|---|---|
| Integrate with a provider's onboarding | Merchants sign up with the provider through your product, and the provider carries most of the payment obligations. | Checkout, onboarding screens, reporting and reconciliation. |
| Build for a payment facilitator | You, or a partner, operate as a facilitator and onboard sub-merchants under one registration. | All of the above plus more of the risk, support and financial operations. |
| Integrate a gateway and let merchants bring their own account | Each merchant keeps their own processor relationship. | Connectivity to several gateways and consistent reporting across them. |
Which one fits depends on your agreements, your risk appetite and your merchants. Your provider and legal advisers decide the model. Paying.co does the engineering, and we never hold funds or hold payment licences.
| Area | Usually the platform | Usually the provider |
|---|---|---|
| User experience | Yes | Hosted fields or components where used |
| Card data capture and storage | Avoid where possible | Yes, through tokenization |
| Merchant underwriting and risk | Collects information | Decides and monitors, depending on the model |
| Settlement and payouts | Shows status | Moves the money |
| Reconciliation and reporting | Yes | Provides data |
This table is a general guide. Your contracts decide who is responsible for what.
Before you design screens, map where card data moves. Hosted fields and hosted pages keep card entry on the provider's side and generally reduce your PCI scope. A design that lets card data pass through your servers brings those servers into scope. Confirm the scope with your provider or a qualified assessor.
What a platform earns on payments depends on its agreements: the model, the provider's pricing, risk costs and support costs. Treat revenue assumptions as a question for your provider and finance team, not as a default.
Some platforms start online and later add terminals, kiosks or tap on phone. Card-present payments bring EMV certification, and tap on phone brings PCI MPoC. We cover both: see EMV Level 3 certification and the MPoC program. You can also score your MPoC readiness.
For scope and timeline, read payment gateway integration: scope, timeline and hidden dependencies.
Tell us what you sell, who your merchants are and which provider you plan to use. We will scope what to build, what the provider covers and how to roll it out.
Talk to us Book a meeting with a founder