MineSec Pay 7
User Guide
POS Integration

POS Integration

MineSec Pay 7 supports two integration models that let external apps or systems trigger payments. In both, MineSec Pay 7 owns the payment UI, card interaction, PIN entry and compliance controls.

POS integration is only available in MineSec Pay 7. It does not apply to the Embedded Payment SDK or the MPoC Isolated SDK.

Compare the two models

App Call AppPOS API
Integration typeAndroid app-to-app (Intent)RESTful API (HTTP)
Deployment scopeSame deviceSame local network
Target clientMobile / merchant appsExternal systems, companion devices, in-store controllers
UI ownershipMineSec Pay 7MineSec Pay 7
Payment flow controlMineSec Pay 7MineSec Pay 7
SettlementSupportedLimited / optional

Both models support application activation, runtime warm-up, transactions (Sale, Void and Refund) and transaction enquiry.

Which model to use

ScenarioRecommended
An Android POS or ordering app on the same device needs card-present paymentApp Call App
Payment requests come from a desktop POS, ECR or external system on the same LANPOS API
The merchant wants to keep the existing workflow and add payment acceptanceEither, depending on architecture

Prerequisites

RequirementApp Call AppPOS API
MineSec Pay 7 installed and activatedRequiredRequired
Merchant app on the same deviceRequired—
MineSec API library (JAR) integratedRequired—
Payserver enabled in Settings—Required
External system on the same local network—Required
TMS Portal configured (acquirer profile, EMV, payment methods)RequiredRequired

App Call App vs standalone

FunctionStandaloneApp Call App
SaleAmount entered in MineSec Pay 7Amount received from the merchant app
ActivationIn the app's own UIThrough the App Call App API
VoidSupportedSupported
Transaction historySupportedNot available (managed by the merchant app)
Navigation menuFull menuPayment screen only
App settingsSettings UIConfigurable through the App Call App API

Integration guides