docs
/
Appmint Mobile

Integration and deployment considerations

Plan the mobile environment, hardware transports and connected business workflows.

Appmint Mobile combines native device services with shared AppEngine records. Plan deployments around the workstation's role, operating system and connected providers.

Identity and context

Keep the organization, authenticated staff member, business location and selected event distinct. Menu visibility controls presentation; server permissions authorize operations. Location and event identifiers must remain attached to their corresponding orders and scan requests.

Native services

Camera, Bluetooth, staff NFC and payment-terminal integrations use platform permissions and native configuration. Match the reader or printer transport to the device. In-app BLE discovery and operating-system HID pairing are separate paths.

Payment-terminal setup uses the business location and its address. Keep signing entitlements, provider account setup and deployment permissions aligned with the features enabled for the device.

Payment lifecycle

Represent collected payments independently from receipt delivery. Preserve provider references, previously paid amounts and pending settlement information. Resume an existing payment or order when recovering an interrupted checkout; do not substitute a new charge for receipt or order reconciliation.

Event lifecycle

Validate admission against the selected event, point, zone, capacity and ticket policy. Record exits for occupancy and returns. Re-entry limits count additional admissions after the initial entry. Benefit redemption observes eligibility, remaining uses and applicable presence conditions.

Continuous input must distinguish repeated camera frames from a new ticket presentation while processing admission decisions in order.

Documentation and integration references