The record
Identity, assignment, capability profile, permitted currencies, rate card and fraud rule set.
MyMercho / Terminals
A terminal is a record with a capability profile.
What a terminal is allowed to do — which channels, which currencies, which keys — is configuration held here and enforced at the gateway before anything reaches the switch.
Terminal record
What each terminal carries.
| Attribute | What it governs |
|---|---|
| Identity | Terminal ID, serial number, model and vendor; the identity Tantra AM attests against. |
| Assignment | Merchant and store, and therefore the reporting line, the rate card and the fraud rule set that apply. |
| Capability profile | Channel — POS, SoftPOS, QR or virtual — and what the model can actually do, including contactless and magnetic-stripe fallback. |
| Permitted currencies | The transaction currencies this terminal may accept. A transaction in another currency is declined at the gateway. |
| Key profile | The key set and version the terminal holds, downloaded on sign-on or on demand. |
| Attestation state | Whether the terminal has presented acceptable integrity evidence. A failure blocks it from transacting. |
| Batch | The open batch and its totals, reconciled at close against stored transactions. |
Channels
One estate, several form factors.
| Channel | Form factor | Notes |
|---|---|---|
| Smart POS | Android smart terminal | TantraFino payment application, EMV Level 2 kernel, PIN pad, printer, camera for QR |
| Physical POS | Countertop and mPOS | Vendor terminals driven through the Payment SDK or the certified terminal interface |
| SoftPOS | The merchant's own phone | Tap-to-Phone acceptance, optional module; availability follows the scheme's programme in the territory |
| QR | Customer- and merchant-presented | Offline dynamic codes with device binding; static printed codes |
| E-commerce | Hosted checkout, Pay-by-Link, API | Phase 2, with 3-D Secure 2.x |
| Merchant portal | Browser | Self-service KYC, promotions, transactions and settlement |
Hand-off
Where the suite ends and attestation begins.
The suite owns what a terminal is. Tantra AM owns whether it can be trusted right now. They share the same terminal record.
The state
Registration, attestation evidence, parameter and key-profile versions, health and last-seen.
The enforcement
Validation at authorisation against the configuration cache — a terminal that fails attestation does not transact.
Attestation, parameter management and estate monitoring are described in detail on geniespay.com.
Next step
Bring the spreadsheet. We will show you what replaces it.
Send us your merchant hierarchy, your MCC list and your fee plans. We come back with a migration shape, a roles and scoping model, and a delivery schedule.