Genies Pay / Certification
Nothing goes to a merchant until this list is clear.
Certification is what sets the dates on an acceptance rollout, and almost none of it is code.
| Certification | Scope | Owner |
|---|---|---|
| EMV Level 3 | Per card scheme, for each terminal model and kernel configuration in the estate. | TantraFino + scheme + POS vendor |
| PCI PIN & key injection | Remote key injection procedures under dual control with the POS and HSM vendors. | TantraFino + vendors |
| PCI P2PE | Only where the institution elects that scope. | Institution |
| EMVCo QR | Conformance for the customer- and merchant-presented payloads. | TantraFino + scheme programme |
| Scheme acquiring | Authorization and clearing certification, per the scheme calendar. | TantraFino + scheme |
| PCI DSS | Alignment of the cardholder-data environment; formal assessment by the institution's QSA. | Institution's QSA, with our support |
Three dependencies, none of them ours alone.
Terminal hardware and key injection
Phase 1 dates depend on terminal availability, key-injection readiness and EMV Level 3 certification slots per terminal model. Adding a model to the estate adds a certification run.
The scheme calendar
Certification slots are booked against the scheme's published calendar, as early as membership allows. Card-not-present dates also follow 3-D Secure enrolment timelines.
Tap-to-Phone availability
SoftPOS depends on the scheme's programme in the licensed territory. Where it is not yet available it is a later release, and we say so rather than implying otherwise.
What the acquirer supplies
POS terminal hardware, vendor contracts and the key-injection facility; declared terminal models, capability profiles and the estate plan; acquiring scheme membership or sponsorship, BIN or ICA, certification slots and the scheme test environment; TLS certificates; and access to the mobile application team where the Payment SDK or QR SDK is embedded in the institution's own app.
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.