Choosing and Running Worldpay for Platforms Inside Your Software
Your sales team has told a new customer they'll be taking card payments through your app by the first of the month. With Worldpay for Platforms, that promise depends on three things: the partnership model you signed, the fee schedules that turn into your payments revenue, and an underwriting review every new merchant has to clear before it can process anything. The product grew out of Payrix, so the docs your developers will read still say Payrix Pro.
Referral, PayFac-as-a-Service or full payment facilitation
Worldpay offers all three. The revenue share and the exact split of duties are set in your contract.
Your payments revenue is a set of fee rules
On Payrix Pro, the platform earns by charging fees to its merchants: boarding fees when a merchant signs up, transaction fees (a flat-rate style like 3% plus 10 cents), monthly platform service fees, chargeback fees when a dispute opens, and fees for add-ons like Account Updater. Each fee is an entity or group, a schedule that triggers it, optional rules and modifiers. Worldpay also lists split payments, dividing one transaction between parties such as the platform, a service provider and a third party.
That makes the fee setup your real price list. A rule pointed at the wrong group undercharges every merchant in it, and no dashboard total will tell you. n-frames builds the check that recomputes what each merchant should have paid from your own pricing records, compares it with the fees Payrix Pro collected, and lists every gap before month end.
What to settle before your first merchant boards
Who reviews our first merchants, and what does each one see meanwhile?
New partners' first submissions are underwritten by hand. A merchant is created straight away with a Not Ready status, can log in and set things up, but can't take a payment until it shows Successfully Boarded. Once your portfolio's approved, automated decisions come back within about 30 seconds. Your app should show that status so sales doesn't guess.
Which webhooks are we turning on?
They're all off by default. Each one is a resource and event pair you add under Admin, with your endpoint and headers. A status change you didn't subscribe to never reaches your app.
Which funding timeline will our merchants actually get?
Settled card funds reach the merchant's available balance, then pay out. T+1 needs Next Day Funding approval. Otherwise it's T+2, or T+3 when a batch closes after the processor's cutoff. Custom batch times can move that, and merchants will ask why a deposit was a day late.
What happens when a payout bounces?
ACH returns fall into three groups. NSF places no hold. BAD ACCOUNT blocks the bank account. UNAUTHORIZED needs the merchant's bank to whitelist Worldpay's funding IDs and send a letter. Your support team needs that path written down.
Who explains a negative disbursement?
When refunds or lost chargebacks exceed a merchant's balance, the difference is debited from their bank account. Disputes have their own rules, covered on our Worldpay chargebacks page.
Building Worldpay payments into your own product?
n-frames builds the platform side Worldpay leaves to you: boarding status inside your own admin, the fee check that proves your revenue share is right, and deposit answers your support team can give without opening the Payrix Pro Portal. For the developer side, see the Worldpay API page.
Board merchants from your app →Questions people ask
What is Worldpay for Platforms?
Worldpay's embedded payments product for software companies. Instead of only taking its own payments, a platform lets its customers accept cards and bank payments inside the platform's product, and earns from the fees it sets on that volume.
What's the difference between Worldpay for Platforms and a normal Worldpay integration?
An ordinary Worldpay setup pays one business for what it sells. Worldpay for Platforms puts a software company above many merchants: it boards them, sets their fees, and, depending on the model, carries some of the underwriting and support work for them.
What are the different Worldpay for Platforms models?
Three: a referral model where Worldpay owns most of the risk for a smaller share, PayFac-as-a-Service where you brand the experience while Worldpay underwrites behind it, and full payment facilitation where onboarding and risk are your platform's job.
Is Worldpay for Platforms the same as Payrix?
It's built on Payrix, which became part of Worldpay's business before the rebrand. The developer and partner docs still live at resource.payrix.com under the Payrix Pro name, and Worldpay's platforms site now redirects to a Global Payments address, so expect all three names in one integration.
How soon can a newly signed merchant take payments?
Not until underwriting finishes. Early on, every merchant you submit is reviewed by hand, covering the business, its owners, fraud checks and the bank account. After your portfolio is approved, many merchants get an automated decision in seconds, while flagged ones go back to Not Ready.
Who builds the onboarding and reconciliation around Worldpay for Platforms?
That's work n-frames does for software companies on it: merchant signup inside your app with live boarding status, fee schedules checked against your own pricing, and deposits, returns and negative disbursements explained in your admin rather than the Portal.