We build custom apps for bank and payment Android terminals: sales, card and QR payments through the terminal's banking app, fiscal receipts, printing, offline mode and fleet management. Based in Uzbekistan, working across the CIS.

A bank Android terminal is a phone with a printer, a card reader and the bank's payment app. You can run your own app on it: ticketing, point of sale, orders, loyalty, field service, inventory. We build these apps around your process and connect them to card and QR payments through the terminal's banking app, to fiscal receipts and to your backend.


The amount is typed in by hand, there are no products, tickets or customers in it, and your reports live in another system.
The cashier rings up the receipt in one place and the card in another, and everything is reconciled by hand at the end of the day.
On a bus, on the road or in a warehouse there isn't always internet, but you still need to sell.
It's unclear which device is where, what version it runs, who worked on it and why a payment failed.
We build an app that becomes the terminal's home screen. The cashier signs in with a PIN, picks a product or service, takes the payment and hands over the receipt without leaving your app. We work with any bank and any acquirer: the payment goes through the banking app already installed on the terminal.
Catalogue, cart, discounts, cash and card, shifts, X and Z reports, refunds and receipt copies.
We call the terminal's banking payment app (ECR mode or the bank's service), get the result and print the slip. Our app never sees or stores card data.
We connect the terminal's fiscal module or cloud fiscalization under your country's tax rules and keep a queue of unsent receipts.
Receipts, tickets and labels on the built-in printer; QR and barcodes via the camera or the built-in scanner.
Selling without internet, a local database, and syncing to the server once the connection is back, with no duplicates or losses.
Pairing a device with a code from the back office, OTA updates over your own channel, telemetry (network, battery, version, errors) and remote commands.
A web back office for the owner: sales, shifts, reports, staff and roles. An API for your 1C, CRM or website.
We write in Kotlin and Java for Android and work with the vendor SDK and the terminal's banking shell. Three models are in production now; for others we use the vendor SDK and a test device from you or your bank.
| Model | What it is | More |
|---|---|---|
| PAX A8900 | a mobile Android terminal with a printer and a banking shell | PAX A8900 app development |
| Sunmi P3 | an Android smart POS with a printer, NFC and a camera | Sunmi P3 app development |
| SmartOne Bank Pro | an all-in-one terminal: card reader, fiscal register and printer | SmartOne app development |
| PAX A920, A80, A35 | the portable A920 and the countertop A80 and A35 on Android | via the PAX SDK |
| Sunmi P2, V2, V2 Pro | earlier generations of Sunmi smart terminals | via the Sunmi SDK |
| Ingenico, Verifone, Newland, Nexgo, Urovo, Telpo | Android models from these vendors | via the SDK, a device is needed |


Ticket sales by conductors and ticket offices, QR checks at boarding, seat maps.
A till on the terminal, catalogue, stock levels, receipt.
Orders at the table or at the door, payment and receipt on the spot.
Payment on delivery, a work report and a signature on screen.
Selling and checking tickets, passes.
A kiosk app on a countertop Android terminal.


Our apps on SmartOne, Sunmi P3 and PAX A8900: sales, payment through the banking app, fiscal receipts, offline mode, telemetry and remote commands.
No need to juggle contractors: we build the app, the server, the back office and the API ourselves.
We connect to the payment app of whichever bank issued the terminal and prepare the access request for you.
15+ of them our own products.
Yes, if it runs Android and the bank or fleet owner allows third-party apps. Distribution goes through the vendor store (PAXSTORE, Sunmi store) or the fleet owner's channel; card payments are still processed by the banking app.
No. We pass the amount to the bank's payment app and get the result back: approved or declined, the authorization code and the slip data. Card number and PIN stay inside the certified part of the terminal.
Any bank and any acquirer. We connect to the payment app of the bank that issued the terminal, using its interface and documentation.
PAX A8900, Sunmi P3 and SmartOne Bank Pro are in production. Other Android terminals (PAX A920, A80, Sunmi P2, V2, Ingenico, Verifone, Newland, Nexgo) via the vendor SDK and a test device.
Yes. Sales are stored on the terminal and synced when the connection is back. Whether cards can be taken offline is up to the bank.
We connect the terminal's fiscal module or the cloud fiscalization of the country where the terminal operates. Unsent receipts are queued and sent later.
For one or two devices you can do without one. A fleet needs a server and a back office: terminal pairing, updates, reports, staff. We build that too.
It depends on terminals, payments, fiscalization and back office. After a short discovery we send a phased estimate.
Yes, if the bank provides a SoftPOS SDK: card payments by tapping an NFC Android phone. We build the same app for the phone.
We will propose an architecture, stages and an estimate.
Call directly
Bakhtiyor Khasanov+998 94 123 42 07Mon–Sat 9:00–19:00, Tashkent time · Telegram @BakhtiKhasanov