Worldpay for Platforms: The money inside your software

For a nonprofit, a donation ought to be a happy ending. Someone believes in the cause, enters a card number, and gives. But the organization still has to connect that gift to a donor record, reconcile the money, and explain anything that goes wrong. The transaction may take seconds. The administrative afterlife can last considerably longer.

Neon One, which makes software for nonprofits, encountered a version of this problem. Its customers needed tools for donors, members, volunteers, and events. Payments connected those activities, yet the company was juggling several payment partners. Its published account describes poor support and technology that customers found cumbersome. What failed was the connection between otherwise useful pieces.

The donation that became a software problem

Neon One’s answer was Neon Pay, a payment service carrying its own name and built with Payrix Pro. The software company could bring the payment experience into its family of products without assembling every underlying payment capability itself. That distinction explains Worldpay for Platforms, the business formerly called Payrix whose website now uses Global Payments for Platforms branding.

Its customer is usually a software company serving a particular industry. Behind that company are merchants: nonprofits collecting donations, schools collecting fees, fitness businesses collecting memberships. Worldpay supplies the payment infrastructure that their software can incorporate. The merchant gets a more connected workflow; the software business gets a chance to earn income from the transactions moving through it.

“Payments revenue is a large part of our business plan”Misty Novich · VP of Payment Solutions, Neon One

The business opportunity sits in a familiar place. Software already knows the customer, the invoice, and the reason money is due. Adding payment collection there can remove another handoff. In Neon One’s case, the attraction included speed to market and room to evolve its offering. The buyer was choosing an operating relationship as well as a technical integration.

Choose how much of the job you want

There are three broad ways into the offering. A referral arrangement leaves much of the merchant relationship with the payments provider. PayFac-as-a-Service gives the software company more command over branding, pricing, and customer experience while the provider handles underwriting and core compliance functions. Registered payment facilitation gives the platform a larger operational role, requiring its own payments expertise.

Stripe Connect, Adyen for Platforms, and Finix compete for similar software businesses. Embedding payments alone does not distinguish this offering. Worldpay for Platforms makes its case through the range of operating models, payment expertise, and connection to an established acquiring business. Buyers should compare the division of work and available markets as closely as the developer tools. A polished API answers only part of the question.

The middle option is especially revealing. The software company can look like the payments business its customers recognize while relying on another organization for specialist functions behind it. Product names still carry that history: Payrix Pro remains part of the story even as the corporate identity changes. The underlying question is who owns each task when a merchant signs up or a payment goes wrong.

The price is also an org chart

A software company evaluating the service needs two calculations. One concerns transaction economics: payment volume, processing costs, and the revenue it can retain. The other concerns people. Who supports merchants? Who handles disputes? Who maintains the integration? The current model comparison explicitly assigns different responsibilities to the software platform and the provider. A larger share of the work requires capacity to perform it.

Pricing is tailored through a quote. That makes a platform’s own numbers essential: expected volume, merchant mix, implementation effort, and support workload. A useful buying exercise is to put every proposed revenue line beside its associated cost and owner. Payment income can help fund a software business, but the retained margin after operating expenses is the number that matters.

This also explains the limits. A small platform without payments staff may have little reason to adopt the most demanding model. A company needing a particular local payment method must establish availability in that market. And a cleaner checkout will do little for a merchant whose reconciliation or support problems remain unresolved. Each responsibility needs somewhere to land.

A business that outgrew its name

Payrix began in 2015, founded by Benny Silberstein and Boruch Greenberg. An October 2020 financing announcement said investment had surpassed $50 million. FIS acquired the company in December 2021 and announced the deal in February 2022. Later financial disclosures put the purchase price at $777 million. In September 2022, FIS introduced Worldpay for Platforms, combining Payrix technology with its broader capabilities.

By October 2025, an Affirm partnership announcement described an offering serving more than 1,000 SaaS companies, with over $400 billion in payment volume and 4.6 billion transactions during the preceding year. Those are historical figures for Worldpay for Platforms. Affirm’s planned integration would add installment payment options to the offering, extending what software partners could provide to eligible merchants and shoppers.

Another ownership change followed. Global Payments completed its acquisition of Worldpay on January 9, 2026. By October, the platform website redirected to Global Payments branding. For a software buyer, the sequence invites practical questions about product continuity and contractual responsibilities. A familiar interface can sit inside a changing corporate structure.

The border changes the calculation

iClassPro, a class-management software provider, supplies a useful final complication. In a published video, it explains that its US volume and internal expertise support operating as a payment facilitator there. Abroad, local knowledge of onboarding, risk, and regulation changes the calculation. A referral arrangement can make sense where the company lacks equivalent scale or expertise.

That is the useful lesson to borrow. Map the customer’s payment journey, decide which responsibilities your team can carry, and choose a model for that situation. Revisit it when the market changes. The payment button may look identical in two countries. The organization required to stand behind it can be very different.