Embedded payments for platforms & ISVs

Embed payments. Skip the middle man.

QorPay gives software platforms embedded payments and full PayFac-as-a-Service on QorCommerce, the processing platform we own and operate. As both a registered PayFac and direct processor, we bring boarding, payments, payouts, and settlement together in one integrated stack, with the team behind the platform operating the processing layer itself.

Ship embedded payments this quarter. Keep your margin.

Most embedded payments offers are a software layer over someone else's processor. Your revenue share is computed on top of their margin, your roadmap requests queue behind their vendor, and the diligence trail runs through a company you have never met.

Integrate with QorPay and your product talks to the processor itself. REST APIs for boarding, payments, and payouts. Merchant applications through Automated Underwriting with MIDs back in the same flow. Embedded forms that keep your PCI scope small. Buy rate or revenue share, both computed against actual processing cost, and full PayFac-as-a-Service under our registration when you want the whole program managed.

Scope it with us this week. Tell us what your platform boards and sells, and we will map it to endpoints and hand you sandbox keys the same day.

Sandbox keys same day Buy rate or revenue share PayFac-as-a-Service under our registration

What can a platform embed?

Three things today: payments, merchant boarding, and payouts. All of them run on QorCommerce APIs, so the pieces you embed talk to the processor directly instead of passing through a reseller layer.

Embeddable surfaces: live today, expanding with QorElementals

Secure Embedded Forms: card and ACH capture inside your UI, with tokenization handled by QorCommerce so your PCI scope stays small.
AppBloqs: drop-in components for tokens, payments, and account management.
Boarding API: submit merchant applications from your own signup flow and get MIDs back from Automated Underwriting.
Payouts: sub-merchant funding on schedules your program defines.

Payouts come with a recipient portal. Each payee gets a read-only view of their own payouts, returns, payout methods, and 1099 status, opened from a link in their email with nothing to install and no password to remember. The where-is-my-money emails that would otherwise land on your support queue answer themselves.

And landing soon: QorElementals, the next-generation embeddable UI SDK. One SDK with Stripe-Elements-style payment fields at its core, expanding into KPI dashboards, Recurring billing components (plan picker, customer portal, subscription manager), and Virtual Terminal widgets, all sharing one theming system so everything you embed looks like your product, not ours. If you are building an embedded payments experience this year, plan it on QorElementals.

Integrate with us once and every surface above is yours. Tell us what you are building and we will hand you sandbox keys the same day.

How do platforms make money on payments?

Two models: buy rate or revenue share. With a buy rate, QorPay sets your wholesale cost and you keep everything you price above it. With revenue share, you take an agreed percentage of program margin and QorPay handles merchant pricing.

Because QorPay is the processor, there is no second margin stacked underneath your economics. The buy rate you negotiate is against actual processing cost, not a reseller's marked-up cost. Both models are line-itemed in reporting, so you can reconcile what you earn against what actually settled. Numbers live on the pricing page.

Want the math on your own volume? We will model both structures against your merchant mix before you commit to either.

PayFac-as-a-Service or become your own PayFac?

Start with PayFac-as-a-Service. QorPay holds the Pathward registration, runs underwriting under its own credit policy, and carries the compliance load, while your merchants board and transact inside your product.

Becoming a registered PayFac yourself means sponsorship, card-brand registration, risk staffing, and capital requirements. It makes sense at volume, and QorCommerce supports that graduation: the platform you integrated for managed PayFac is the same platform you would run your own program on. You change agreements, not code.

Not sure which side of that line you are on yet? We will help you pick, and the platform is the same either way.

How long does boarding take?

Most applications clear Automated Underwriting without human touch: KYC, KYB, match-list checks, and risk scoring run in one flow, and a clean file gets a MID the same day. Files that trip a threshold route to an exception queue for manual review instead of being auto-declined.

For your product, boarding is an API call or an embedded form. Your signup flow collects the data once; QorCommerce returns status webhooks as the application moves.

Board your first test merchant this week and time it yourself.

What do you handle vs what do we handle?

The split is clean. QorPay runs everything regulated and settlement-critical; you run the product and the merchant relationship.

QorPay handles

Sponsor registration and card-brand compliance
Underwriting, KYC/KYB, and MID issuance
Authorization, settlement, and funding
Risk monitoring and Circuit Breaker controls
PCI DSS Level 1 infrastructure and tokenization

You handle

Your product, UX, and merchant signup flow
First-line merchant support and communication
Accurate boarding data and program-rule adherence
Your pricing above buy rate, or your rev-share terms

Frequently Asked Questions (FAQs)

Should a software platform be a PayFac or work with an ISO?

Most platforms should not become a PayFac on day one. Registration, sponsorship, and compliance staffing are real costs that only pay off at scale. PayFac-as-a-Service on QorCommerce gives you the same embedded experience, with QorPay carrying the registration and the liability, and a graduation path if you later want your own program.

Who owns the merchant relationship?

You do. Your merchants sign up in your product, see your brand, and call your support line first. QorPay is the processor and PayFac of record underneath, and the sub-merchant agreements reflect that split.

How is liability split between the platform and QorPay?

Under PayFac-as-a-Service, QorPay holds the sponsor registration and carries credit and fraud loss under its own underwriting policy. Your obligations are contractual: accurate boarding data, cooperation on risk reviews, and staying inside program rules. The exact split is written into the program agreement, not implied.

Can we white-label the payment experience?

Yes. Boarding flows, Secure Embedded Forms, hosted checkout, and receipts can all carry your branding. Merchants transact inside your product without seeing QorPay in the flow.

What does integration actually require?

QorCommerce is REST APIs with key-pair header auth and JSON in and out. Boarding, payments, and payouts are separate endpoints you can adopt incrementally: many platforms ship embedded forms first and add API boarding later.