MineSec gives you the parts of a card-present payment system. The three paths differ in how much of that system you
build yourself and how much MineSec runs for you.
Compare the paths
Flip through the paths to see what runs in MineSec's environment, what runs in yours, and how a transaction flows
between them.
Launch MineSec Pay 7
PSPs who want to go to market without app development
Embed payments in your app
PSPs and ISVs adding card acceptance to their own app
Build your own SoftPOS app
Solution providers building their own SoftPOS product
Hosted and run by MineSecRun and managed by you
Merchant's device · Where the card is tapped
On the merchant's deviceMineSec Pay 7Published under your brand. Reads the card, takes the PIN and runs the whole transaction with MineSec.
1Encrypted card data6Transaction result
Attestation with AMS and settings from TMS, alongside
MineSec environmentHosted and run by MineSec, as SaaS
Transaction processingAccess GatewaySaaSPCI DSS
Receives the encrypted transaction from every device
Routes each transaction to your payment host
Attestation & MonitoringAMSSaaSChecks every device, alongsidePortal & API
Terminal managementTMSSaaSMerchants, terminals, settingsPortal & API
2Transaction request5Transaction result
Host connection†
MineSec integratesorYou, via Host API
Your environmentRun and managed by you
Payment hostYour payment host*Your payment gateway, or the acquirer host
3Authorisation request4Authorisation result
ExternalCard networksVisa, Mastercard and others
You bring your brand and your payment host. MineSec runs everything else. View guide
1The app encrypts the card data and PIN on the device and sends them to Access Gateway.
2Access Gateway sends the transaction to your payment host.
3Your payment host routes the authorisation request through the acquirer to the card network.
4The card network returns the authorisation result.
5Your payment host returns the result to Access Gateway.
6Access Gateway returns the result to the app.
* Payment host. In most deployments, Access Gateway connects to your payment gateway, which routes the transaction to the acquirer (bank) host and on to the card networks: Access Gateway → your payment gateway → acquirer host → card networks. If you do not run your own payment gateway, Access Gateway connects directly to the acquirer host.
† Host connection. Either MineSec builds and runs the connection to your payment host, or you build it yourself on the Outbound Host API.
Merchant's device · Where the card is tapped
You buildYour appUI and business logic. Calls the SDK with an amount.
calls
Embedded in your app · by MineSecEmbedded Payment SDKReads the card, takes the PIN and runs the whole transaction with MineSec.
MineSec environmentHosted and run by MineSec, as SaaS
Transaction processingAccess GatewaySaaSPCI DSS
Receives the encrypted transaction from every device
Routes each transaction to your payment host
Attestation & MonitoringAMSSaaSChecks every device, alongsidePortal & API
Terminal managementTMSSaaSMerchants, terminals, settingsPortal & API
Your environmentRun and managed by you
Payment hostYour payment host*Your payment gateway, or the acquirer host
ExternalCard networksVisa, Mastercard and others
1Encrypted card data2Transaction request5Transaction result6Transaction result
You buildYour appUI and business logic. Calls the SDK with an amount.
calls
Embedded in your app · by MineSecEmbedded Payment SDKReads the card, takes the PIN and runs the whole transaction with MineSec.
1Encrypted card data6Transaction result
Attestation with AMS and settings from TMS, alongside
MineSec environmentHosted and run by MineSec, as SaaS
Transaction processingAccess GatewaySaaSPCI DSS
Receives the encrypted transaction from every device
Routes each transaction to your payment host
Attestation & MonitoringAMSSaaSChecks every device, alongsidePortal & API
Terminal managementTMSSaaSMerchants, terminals, settingsPortal & API
2Transaction request5Transaction result
Host connection†
MineSec integratesorYou, via Host API
Your environmentRun and managed by you
Payment hostYour payment host*Your payment gateway, or the acquirer host
3Authorisation request4Authorisation result
ExternalCard networksVisa, Mastercard and others
You build your app and call the SDK with an amount. MineSec handles the card, the backend and terminal management. View guide
1The app encrypts the card data and PIN on the device and sends them to Access Gateway.
2Access Gateway sends the transaction to your payment host.
3Your payment host routes the authorisation request through the acquirer to the card network.
4The card network returns the authorisation result.
5Your payment host returns the result to Access Gateway.
6Access Gateway returns the result to the app.
* Payment host. In most deployments, Access Gateway connects to your payment gateway, which routes the transaction to the acquirer (bank) host and on to the card networks: Access Gateway → your payment gateway → acquirer host → card networks. If you do not run your own payment gateway, Access Gateway connects directly to the acquirer host.
† Host connection. Either MineSec builds and runs the connection to your payment host, or you build it yourself on the Outbound Host API.
Merchant's device · Where the card is tapped
Embedded in your app · by MineSecMPoC Isolated SDKReads the card, takes the PIN, encrypts both.
calls
You buildYour payment appRuns the transaction flow and sends the encrypted data to your backend.
MineSec environmentHosted and run by MineSec, as SaaS
Attestation & MonitoringAMSSaaSThe only part MineSec runs in this pathPortal & API
Your environmentRun and managed by you
Payment backendYour payment backend*Takes transactions from your app and sends them on to the card networks
Embedded in your app · by MineSecMPoC Isolated SDKReads the card, takes the PIN, encrypts both.
calls
You buildYour payment appRuns the transaction flow and sends the encrypted data to your backend.
1Encrypted card data6Transaction result
Straight from your app to your backend. It does not pass through MineSec.
Your environmentRun and managed by you
Payment backendYour payment backend*Takes transactions from your app and sends them on to the card networks
4Authorisation request5Authorisation result
ExternalCard networksVisa, Mastercard and others
2Check attestation3Attestation status
Your payment backend checks the device with AMS before step 4.The SDK also reports device attestation to AMS, alongside
MineSec environmentHosted and run by MineSec, as SaaS
Attestation & MonitoringAMSSaaSThe only part MineSec runs in this pathPortal & API
You build the app and the payment backend on the MPoC Isolated SDK. MineSec runs attestation and monitoring. View guide
1The MPoC Isolated SDK encrypts the card data and PIN; your app sends them to your payment backend.
2Your backend asks AMS for the attestation status of that SDK instance.
3AMS returns the status. Your backend continues only if the device passes.
4Your backend routes the authorisation request through the acquirer to the card network.
5The card network returns the authorisation result.
6Your backend returns the result to the app.
* Payment backend. Your own payment gateway or host. It reaches the card networks through your acquirer (bank) host, or connects as the acquirer host itself.