Swile expanding benefits card into finance stack
Swile
This reveals that Swile’s real upside is not another benefits SKU, but turning a benefits card already sitting in employees’ wallets into the front door for broader company spend. Swile already has HR admins funding cards, employees using them, and Mastercard rails behind the scenes. Adding travel through Okarito lets it move from regulated lunch and gift budgets into the much larger stream of everyday business purchases, where software plus payment flow drives more volume and more fees.
-
The installed base matters because Swile is already embedded in payroll and HR workflows. After the Bimpli deal, it had 75,000 clients and 5M covered employees. Employers already top up balances and manage rules in Swile, so selling travel or other controlled business spend is much easier than starting from a cold finance software sale.
-
Ramp shows the product playbook. It started with corporate cards, then added bill pay, AP automation, procurement, vendor management, travel, and reimbursements. In practice that means moving from employee swipes to paying suppliers and managing approvals in one system. That is the same expansion path Swile is aiming at from a different wedge.
-
Swile also has an unusual bridge into payments for a European benefits company. Legacy peers like Edenred already make a meaningful share of revenue from card usage and have expanded into fleet and mobility. Swile’s Mastercard based card and merchant commission model means every new spend category can increase transaction volume without rebuilding a closed acceptance network first.
The next step is a finance stack for SMBs that starts with employee benefits, then absorbs travel, employee expenses, vendor payments, and approval workflows. If Swile executes, it stops looking like a niche meal voucher company and starts looking like a European spend management platform with a built in distribution engine that competitors in B2B payments would have to buy expensively.