CileaPay
One dashboard for card takings across every till and every site, for merchants who had been reconciling terminals by hand.
- Industry
- Payments / monétique
- Platform
- Web platform + payment terminals
- Role
- Collaborator — Cilea software & payments dev team
Business context
A pharmacy chain or a restaurant group with several tills ends the day with several separate stories about what it earned, one per terminal. CileaPay's proposition is a single platform where card takings from every Android terminal across every site arrive together, on a flat monthly price with no per-transaction commission. That promise is only worth anything if the transaction record is complete, fast to search, and safe to expose to the right person and nobody else.
My responsibility
I work on this as part of Cilea's payments team under a B2B contract, across the payment service, the merchant-facing platform, and the customer portal.
Solution
Transaction history with filtering built for how a merchant actually looks for a payment, a transaction-grouping endpoint so takings roll up rather than arriving as a flat list, and merchant ticket and payment-recap screens with receipt preview. Exports to CSV and PDF, because reconciliation ends in an accountant's inbox. On the terminal side: parameterization with model selection and auto-filled terminal data, supervisor modules and profile listings for businesses whose staff should not all see the same thing, and session security work on terminal links — including making a terminal link single-use, so a URL that grants access to a payment device cannot be replayed.
Results
In production, integrated with the Lyra payment gateway. Transaction volumes and customer names are Cilea's to disclose.
Technology
Card data never lands in the platform: Lyra's embedded form keeps entry inside the gateway's scope, and the terminals hold no card data locally. What CileaPay stores is the transaction record around the payment, which is what merchants actually need to search.