PAYING.CO GUIDES

Embedded payments for software platforms.

The three models, what the platform builds, who handles what, PCI scope and when card-present payments enter the picture.

7 min read · By Kevin Medina · Updated November 19, 2026
The short version

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.

What embedded payments means for a software platform

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.

Three ways to put payments in your product

ModelHow it worksWhat you build
Integrate with a provider's onboardingMerchants 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 facilitatorYou, 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 accountEach 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.

What a platform actually has to build

Who handles what

AreaUsually the platformUsually the provider
User experienceYesHosted fields or components where used
Card data capture and storageAvoid where possibleYes, through tokenization
Merchant underwriting and riskCollects informationDecides and monitors, depending on the model
Settlement and payoutsShows statusMoves the money
Reconciliation and reportingYesProvides data

This table is a general guide. Your contracts decide who is responsible for what.

Know where payment data travels

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.

Payment economics

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.

When card-present enters the picture

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.

Before you start

For scope and timeline, read payment gateway integration: scope, timeline and hidden dependencies.

Frequently asked questions

What are embedded payments?
Embedded payments means payment acceptance built into a software product, so customers pay and get paid without leaving the platform. The platform owns the experience and a provider moves the money.
What does a software platform have to build for embedded payments?
Checkout and payment screens, payment requests, tokenization integration, merchant onboarding interfaces, transaction reporting and reconciliation, and clear handling for refunds, failures and disputes.
Do we need to become a payment facilitator?
Not necessarily. Some platforms integrate with a provider's onboarding and let the provider carry most obligations, and others become facilitators. Your provider and legal advisers help you choose.
How do embedded payments affect PCI scope?
Hosted fields, hosted pages and tokenization generally keep card data out of your systems and reduce scope. Letting card data pass through your servers brings them into scope. Confirm with your provider or a qualified assessor.
Can we move existing customers to a new provider?
Often, but it takes a plan. Tokens are generally issued by a provider and are not automatically portable, so stored cards and subscriptions may need a migration. Reporting and reconciliation should keep working during the move.
Does Paying.co hold funds or act as the payment provider?
No. We do integration and engineering. We never hold funds and we do not hold payment licences. We work with your provider and your agreements.

Planning embedded payments for your platform?

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