Genies Pay / Attestation
A terminal transacts in the configuration you approved, or it does not transact.
Tantra AM 1.0 is the gate and the watchtower: what gets onto the estate, what it is allowed to be, and what it has been doing since.
——
—
——
—
——
—
——
—
7.5 · The gate
Admission is a check, not a registration form.
- The terminal presents identity and integrity evidence before it is permitted to transact
- A failed attestation blocks the terminal and raises an alert
- Re-registration and a fresh parameter download are required before it returns
- The block is enforced at the gateway, not only reported in a console
7.5 · Functional specification
What Tantra AM does.
| Capability | Specification |
|---|---|
| Terminal registration | Terminal identity, serial number, model, merchant and store assignment, and activation state. |
| Attestation | The terminal presents its identity and integrity evidence before it is permitted to transact; failed attestation blocks the terminal and raises an alert. |
| Parameter management | Parameter sets and key profiles per terminal group, versioned and downloaded on sign-on or on demand. |
| Estate monitoring | Terminal health, last-seen, transaction and decline trends, batch state and version distribution across the estate. |
| Alerts & reports | Threshold and event rules with severity, routing and escalation; scheduled estate and exception reports. |
The estate
Health, versions, and the one that went quiet.
Illustrative estate view. Health, last-seen, version distribution and decline trend come from Tantra AM. One terminal here has not been seen for four days — which is the kind of thing that is invisible until something watches for it.
Next step
Put one in your hand.
Tell us your terminal models, your channels and whether the SDK is going into your own app. We come back with a rollout shape, a key-injection procedure and an EMV Level 3 certification schedule.