Aurora Payments found the business behind the swipe

Consider what sits on either side of a card reader. At a nail salon, an appointment, a technician and a returning customer. At a jeweler, an expensive object and a relationship built on trust. At a funeral home, a family making decisions it never wanted to make. The machine can accept the same card in all three places. The business around it changes completely. Aurora Payments built its strategy around that distinction.

01 / First, collect the businesses

The chronology has a wrinkle. Aurora dates its roots to 2005. Yet former chief executive Brian Goudie told a payments podcast that Aurora came into existence in April 2018, when capital and acquisitions brought several existing businesses together. Applied Merchant Systems supplied the earlier lineage. BlueSquare and Chosen Payments helped supply the expanding group. Both dates describe something real: the age of the operating roots and the birth of the consolidated company.

In a 2020 interview, Goudie resisted taking credit for creating its processing volume organically. Acquisitions mattered. So did distribution: agents, software companies and associations already knew merchants Aurora wanted to reach. Corsair acquired a majority stake in January 2022. This was a business assembling relationships and infrastructure, rather than waiting for every shopkeeper to discover a new checkout button.

02 / Then, connect the plumbing

Buying businesses leaves a practical question: can their systems cooperate? Engineering partner Proxet describes acquired legacy systems that were difficult to integrate, alongside pressure to improve payment orchestration quickly. That is the documented friction in Aurora’s story. A larger portfolio could bring more customers while leaving the underlying technology awkwardly divided. The attraction of scale did not make the software fit together by itself.

ARISE, launched in April 2024, was Aurora’s answer. The proprietary platform combined a virtual terminal, payment acceptance, reporting, invoicing and customer tools. Proxet describes custom APIs, microservices and connections to TSYS and ACHQ. An owner could send an invoice, take payment and investigate transaction information within a connected environment. For software vendors, APIs offered a way to place payments inside their own products. Aurora was building something it could control and extend.

03 / A manicure explains the model

In April 2023, Aurora acquired NailSoft, salon software developed by former salon owner Dat Nguyen. Booking, marketing and payment acceptance belonged to the same working day. Owning software that understood that day gave Aurora a reason to be involved before a customer reached for a wallet. NailSoft’s partner materials also advertise onboarding and service in English, Vietnamese and Spanish. Specialization can be as concrete as speaking the owner’s language.

The broader customer base includes jewelers, healthcare practices, funeral businesses, transportation operators and ordinary retailers. Association relationships, including Jewelers of America and the National Funeral Directors Association, help reach those markets. Square, Clover and Stripe are familiar alternatives across different portions of this landscape. Aurora’s proposition centers on industry knowledge, adaptable merchant services and embedded software. Whether that matters depends on how much of a merchant’s working day a generic checkout leaves untouched.

04 / The fee still goes somewhere

Aurora’s economics combine processing with software and related merchant services, sold directly and through partners. Its successor brand now publishes a useful starting point: Flute Standard lists 2.6% plus 10 cents for in-person payments and 3.3% plus 25 cents online. On a $100 sale, those advertised formulas produce $2.70 and $3.55 respectively. Hardware, setup and custom arrangements still require attention to the actual quote.

“Zero-cost” options require a different question: who absorbs the expense? Flute describes dual pricing, surcharging and cash discounts as ways to offset merchant card costs. A customer may face a different price or receive a cash incentive. Suitability depends on the customer base and the applicable requirements. A shop competing on a frictionless checkout should weigh that customer experience alongside the arithmetic. Moving a fee does not make its commercial consequences disappear.

There is also work customers never see. In April 2025, Aurora announced network tokenization for ARISE: card-network-issued tokens replace sensitive card details, with updates for expired or reissued cards. For a business collecting recurring payments, keeping credentials current addresses a mundane source of interruption. Aurora presents fewer declines and reduced fraud as intended benefits. Those claims describe the purpose of the feature; they are not a measured savings promise for every merchant.

05 / The new name carries the old problem

On June 1, 2026, Aurora announced its rebrand as Flute. Chief executive Derek Dean described merchants who had inherited confusing processing arrangements. The new platform brings payments, working capital, reporting and servicing into one account. The release reported more than 113,000 customers signed and $40 billion processed since founding. Those are cumulative figures. Aurora’s earlier 27,000-plus merchant portfolio and $12 billion annual processing figure measured different things; they cannot be stitched into a tidy growth chart.

“Most merchants didn’t choose their payment processor so much as they just inherited one.”

Derek Dean · Flute launch announcement · June 2026

There is a useful lesson here for anyone building business software: study the work surrounding the transaction. An invoice waiting for approval, a recurring bill and an appointment calendar create different needs. Aurora bought access to those needs, then invested in connecting the machinery. The approach makes sense when integration and industry support earn their keep. For a merchant with a simple checkout and little administrative complexity, a smaller setup may already do the job. The practical test is wonderfully ordinary: does tomorrow’s work become easier?