Top-ups land as cashflow. Every till sees the identified customer. Attribution flows back per branch. Foodics keeps doing what Foodics does; Feddi handles the wallet stack on top.
For the operator
Customers top up their Feddi wallet, that's revenue in your bank that day, against future till spend. Every redemption at the till identifies the customer to that branch's operator instantly. Attribution flows back the same hour, not at month-end.
For Foodics
The Foodics terminal stays as it is. Feddi appears as a payment method alongside cash and card. The receipt prints as Foodics normally prints. No new operator training beyond "scan the wallet pass when the customer asks to pay with it."
For the customer
Customers install one wallet pass per chain. The balance is honoured at every branch. Reloads happen in-app or at any till. No physical card, no app per chain, no per-branch loyalty token.
How it works
Feddi subscribes to transaction.completed + order.completed + customer.updated on your Foodics account. Every transaction at every branch reaches Feddi inside one second.
Feddi registers as a payment method through the Foodics payment API. The till operator selects "Feddi wallet" the same way they select "cash" or "card." The Feddi backend authorises the wallet debit against the till in real time.
When a customer identifies via the wallet, Feddi writes the phone-keyed customer record to Foodics. When Foodics has an existing customer with the same phone, Feddi reads the Foodics record and joins on it. One identity, two systems, in sync.
Setup
We provision your Feddi tenant + brand the wallet pass. Your team adds the Feddi app from the Foodics marketplace, generates an API key, and shares webhook + payment-method credentials with us. We register the payment method, subscribe to webhooks, and run an end-to-end test in your sandbox branch.
One branch goes live. Operators get a 20-minute walkthrough. We sit on the floor for the first lunch service. Reconciliation runs nightly; we read the numbers with you the next morning.
Once the pilot branch is honest, we roll across the network branch by branch on your schedule. Typical pace: five to ten branches per week. Each branch goes live with a one-page playbook and a 15-minute team huddle.
Frequently asked
No. Feddi sits on top of your existing Foodics deployment. Your terminals, menus, and operator workflows keep working exactly as they do today. The Feddi wallet is a payment option alongside cash and card.
Feddi listens to Foodics webhooks for transactions and integrates as a payment method via the Foodics payment API. Wallet top-ups generate Foodics-side payment records; redemptions debit the wallet and clear against the till. Reconciliation is automatic, branch by branch.
Typical chain: two to four weeks. Week one we wire the Foodics webhook plus payment method, week two we provision branded wallet passes, week three we run a single-branch pilot, week four we roll across the network.
Foodics owns the POS, the menu, the till workflow, and the receipt. Feddi owns the wallet, the customer identity, the incentive rules, the attribution data, and the operator decisioning surface.
Yes. Feddi prices its tiers independently of Foodics. The Foodics subscription continues as today; Feddi adds the wallet stack and its tier-based pricing on top. See /pricing/.
Yes. Existing customer records in Foodics stay in Foodics. New customers identified through the wallet are written to both sides, wallet identity on the Feddi side, customer record on the Foodics side, joined by phone number.
15-minute call. We'll walk through the integration on your sandbox account before any commitment.