Android Payment App Development
Employer not named by the sourceRemote
Frontier is not the employer and does not collect applications.
About this role
Java, Mobile App Development, Android, Software Architecture, Odoo, Payment Gateway Integration, Mobile Development, Android App Development, API Development, API Integration · A native Android application that turns the sales phone into a card terminal, embedding SumUp's Tap to Pay SDK to read contactless cards over NFC. No separate card reader.
How it fits. Two applications on one device. The Odoo POS is a Progressive Web App, built separately, and launches this app when the operator selects the card payment method.
How the flow works. A PWA cannot receive an Android activity result, so the two apps never exchange the outcome directly. The POS passes a transaction identifier by intent. The app fetches the authoritative amount from the Odoo server over its own authenticated call, runs the payment through the SDK, and posts the result back to the server — which then updates the payment line in the POS. The amount never travels in the intent, so nothing on the device can set the price.
What it does. Seven areas of work:
Provisioning and terminal identity — one-time device binding with backend service credentials, encrypted device token, terminal status screen, guarded deprovisioning SDK lifecycle and token supply — single initialisation, a non-blocking token provider, proactive background refresh Request validation and amount conversion — caller signat