T-NET / Integration
Every interface is its own project.
Each external system gets a plan, environments, test cases and exit criteria. The workstream runs in parallel with the product phases and gates each go-live.
4.2 · Communication matrix
What talks to what, and how.
| Source | Destination | Protocol | Purpose |
|---|---|---|---|
| POS terminal / SDK | TANTRA PAYGATE 3.0 | HTTPS REST (TLS 1.2+, JWT) | Transactions, batch close, terminal status |
| Customer app QR SDK | Secure Point | HTTPS REST | QR generation, device binding, verification |
| PAYGATE 3.0 | Redis / PostgreSQL | Internal | Entity validation from the configuration cache; transaction persistence |
| PAYGATE 3.0 | AML system | REST hook | Transaction and merchant screening |
| PAYGATE 3.0 | HSM service | gRPC over mTLS | PIN translation, MAC, EMV cryptogram services |
| HSM service | HSM appliance | Host command channel | PIN, MAC and key operations |
| PAYGATE 3.0 | T-NET Acquiring Route | gRPC | Authorization, reversal and settlement messages |
| T-NET Acquiring Route | Scheme / network | ISO 8583 over TCP, 2-byte LLBC framing, TLS | Acquiring authorization and clearing |
| T-NET Acquiring Route | Core banking | ISO 8583 or REST over TLS | Posting, holds, capture and settlement |
| T-NET / PayGate | Accounting / GL | REST | Journal posting and reconciliation |
Workstreams
Nine of them, each with an owner.
| Workstream | Scope | Interface | Responsibility |
|---|---|---|---|
| HSM | Readiness, key ceremonies, BDK and ZPK loading, PIN translation and MAC services | Host commands / gRPC | TantraFino + HSM vendor |
| Scheme / network | Acquiring authorization and clearing certification, brand testing | ISO 8583 certified | TantraFino + scheme |
| EMV Level 3 | Terminal and kernel configuration certification per card scheme and per terminal model | EMV L3 test suites | TantraFino + scheme + POS vendor |
| Core banking | Posting, holds, capture, settlement and GL mapping | ISO 8583 / REST | TantraFino + CBS vendor |
| 3-D Secure | ACS and directory-server enrolment and testing | Scheme API / EMV 3DS | TantraFino + scheme |
| AML | Screening hook, alert routing | REST / ISO hook | TantraFino + AML vendor |
| Accounting / GL | Journal posting and reconciliation interface | REST | TantraFino + finance systems team |
| POS vendors | Terminal models, key injection, application deployment and remote update | Vendor SDK / TMS | TantraFino + POS vendors |
| SMS / e-mail | Advice, OTP, statements | SMPP / SMTP / REST | TantraFino + provider |
Dependencies
Three things that set the dates, and none of them are code.
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
Phase 2 dates follow the scheme certification calendar and 3-D Secure enrolment timelines. We plan against the published calendar and book slots as early as membership allows.
Tap-to-Phone availability
SoftPOS depends on the scheme's Tap-to-Phone programme in the licensed territory. Where it is not yet available, it is a later release rather than a missing feature.
What the institution supplies
Connectivity and firewall rules per the communication matrix; vendor contacts and contracts for core banking, scheme, AML, 3-D Secure, accounting, POS and gateways; the acquiring BIN or ICA and certification slots; non-production environments and test data; and named certification participants.
Next step
Send us your message spec. We will send back a profile.
Your scheme endpoint, your CBS interface and your terminal mix are enough for us to come back with an ISO 8583 packaging profile, a sizing note and a certification schedule.