When the sales application is on one screen and payment results stay in another record, staff have to investigate the same transaction again. MagicPay Android POS brings checkout and payment applications together on an Android terminal through a shared order reference. Connect card, contactless and QR collections to your sales workflow, then follow results in the same central dashboard, whether in-store, at a table or at a mobile sales point. Your own business applications can also form part of the terminal workflow.
Keep orders and payments on the same device
The sales application's amount and order details pass into the terminal's payment step. The result returns to the relevant sale, giving cashiers, service staff and central teams the same record. Track which order the customer paid and which user and device initiated the transaction together.
- Create terminal payment requests with an order reference.
- Connect card, contactless and QR flows to the sales experience.
- Post completed payments back to checkout or service records.
Bring your business application to the terminal
Alongside accepting payments, Android POS lets you run your own business applications on the device. Staff handle orders and payments at the same working point, and the application's sales identity stays in the payment history. Choose a terminal arrangement for your location from the existing CASTLES device catalog while using the same central branch and user structure.
Give cashiers and finance the same result
Cancellations and refunds remain linked to the original order. When customers ask about a transaction, teams start from a shared record instead of finding the person who used the terminal. Pending or uncertain payments are tracked separately; their latest status is checked before another collection is requested. Branch, device, date and status filters support both service control and financial follow-up.
Use Android POS in three steps
Make the device part of your everyday sales process.
- 1. Map your checkout, table or mobile sales point to the appropriate terminal and merchant account.
- 2. Connect the sales application, payment methods and staff permissions through shared references.
- 3. Run sales, cancellation and refund scenarios, then follow transactions in the central dashboard.
Who is it for?
Restaurant service teams, supermarket checkouts, retail stores and mobile sales locations. It creates a shared working arrangement between device and application for businesses wanting to complete payment where the order is taken. In multi-branch organizations, central teams see the network while staff work on their own location's transactions within their assigned responsibilities.