Fintech and payments Case study
iOS point-of-sale app for a retail technology company
An iOS point-of-sale app with card payments, receipt printing, reports and accounting export, developed and maintained over six years.
Overview
A point-of-sale app for retail and restaurant use on iPhone and iPad. We designed and built it, then kept developing and testing it for six years as payment terminals, tax rules and accounting integrations changed.
The challenge
A POS has to be right every time: tax compliance through a tax-agency control unit, several payment providers with refunds and reversals, many receipt printers, and totals that agree across receipts and reports.
What we built
- iOS app design, prototyping and core screens for transactions and article (product) management
- Integration with a tax-agency control unit for compliance
- Payment gateway integrations (Bambora, Miura, Klarna) with sales, refunds and reversals
- Receipt printing for several printer models, with customer and merchant copies
- Day, month, X and Z reports, delivered by email or print
- Split receipts and parked receipts, discounts, VAT and currency handling
- Accounting integration (Visma) for vouchers and sales data, plus barcode scanning and article sync
- SMS receipts, Zendesk chat for support, and ongoing regression testing and crash fixing
How a system like this fits together
- Client side
- Services
- Third parties
In words: The iOS point-of-sale app prints receipts on several printer models and integrates with a tax-agency control unit. It syncs articles with a PHP and MySQL back end, takes payments through Bambora, Miura and Klarna payment SDKs, sends vouchers and sales data to Visma, and offers Zendesk chat for support.
Technology used
| Layer | Choice | Purpose |
|---|---|---|
| Mobile | iOS (Objective-C) | the point-of-sale app |
| Server | PHP, MySQL | back end and data storage |
| Payments | Bambora, Miura, Klarna | payment gateways with sales, refunds and reversals |
| Accounting | Visma | vouchers and sales data |
| Support | Zendesk | chat support |
What happened next
- Delivered
The work described above was delivered to the client.
- Operational facts
- Our work on this project spanned 2014–2020.
- It was maintained and extended over 6 years.
Could this be your project?
- You are planning an iOS or Android app, or have one that needs a stronger back end behind it. Mobile app development
- Your product has to connect to payment, accounting, messaging or other third-party systems.
- You work in fintech and payments and want a team that has built for it before. Fintech and payments work
Questions about this project
How long did this project take?
Our work on it ran from 2014 to 2020, with 9,000+ engineering hours logged in total.
What technology was used?
iOS, MySQL, PHP, Payment SDKs, Visma, Zendesk, Objective-C.
Was it maintained and extended over time?
Yes. Our work on this project was maintained and extended over 6 years, from 2014 to 2020.
Similar work
Also iOS and MySQL, also a mobile app
My Taxi Ride: taxi dispatch and booking platform
Passenger and driver apps for iOS and Android, a dispatch admin panel with reporting, APIs, SIP calling and the public website for the My Taxi Ride dispatch system, built over four years.
Also iOS, same industry
Authoriti: multi-factor permission code app
An app that generates encrypted multi-factor permission codes, protected by a fingerprint scanner, with driver-licence scanning and validation through a customised Acuant SDK.
Also MySQL and PHP, also an integrations project
QCare: compliance platform for DEKRA
QCare, DEKRA's quality, compliance and risk evaluation platform on the Collabtic service platform: certification and compliance tracking, organisations, training, shop certification and headquarters dashboards, on an Angular front end and a PHP API.