EN
Back to the archive

The encyclopedia · Finance & Accounting · Financial decision · 2026

Chilli Beans' own card machines turn franchise sales data into a credit business

Brazil's sunglasses chain became its own acquirer: it keeps swipe fees, sees every store's cash flow, and lends to franchisees.

Chilli Beans

the move

Chilli Beans, Latin America's largest sunglasses-and-accessories chain, made a decision most retailers outsource: in August 2026 it launched its own payment-acquiring arm and branded card machine, ChilliPay, for its network of more than 1,000 franchised kiosks and stores.

By capturing transactions itself, the franchisor keeps the merchant discount rate and receivable-anticipation margins that used to go to acquirers, and removes intermediaries from daily settlement. For franchisees, the pitch is lower card-processing costs — material when Brazil's benchmark Selic rate stands at 14% and working capital is expensive.

The bigger play is credit: with full visibility of each store's receivables and cash-flow history, the company builds its own risk algorithms and offers working-capital and store-renovation loans, repaid through a lock on daily sales. The move turned Chilli Beans from a consumer brand into an embedded-finance ecosystem.

why it works

  • Swipe fees become revenue instead of an expense.
  • Daily sales data is better collateral data than a bank's.
  • Cheaper credit keeps franchisees alive in a high-rate economy.
  • The moat deepens as the network grows and data accumulates.
the payoffBe the card acquirer for your own franchise networkinspired

what transfers

If you own the store network, you own the payment data: becoming your own acquirer turns card fees into a finance business with better lending information than any bank.

what came after

The fintech vertical was rolled out at the brand's annual franchise convention, with credit for working capital and store renovations as the first products; analysts read it as a model other large Brazilian franchise networks were likely to copy in 2026.

references

spotted an error? The archive wants to know.

same kind of clever