2D Transact
Connect through APIs. Extend across channels.
Integrate the 2D mechanism into the systems that already manage your users and their value.
An integration with defined responsibilities.
Request integration
Create and retrieve transaction requests and their supported attributes through the controller interface.
Response integration
Capture a user-authorised response after the connected platform applies its authentication and required checks.
Execution & outcomes
Connect settlement instructions, confirmations and reconciliation to the relevant platform workflow.
Design for a dependable transaction journey.
During integration design, agree request and response schemas, authentication, platform permissions, unique references, retry behaviour, duplicate prevention, outcome reporting and reconciliation. Establish the handling of expired requests, failed responses and interrupted execution before production rollout.
API documentation, environments and implementation requirements are provided through the technical engagement process.
Technology inclusion requires a connected route.
Numeric references support low-tech interfaces alongside QR-based smartphone journeys. USSD, POS and web access each require an implemented connection to the controller. This site describes connected operation; fully offline settlement is not presented as a current capability.
Connect your next transaction.
Discuss your platform, channels, units of value and intended transaction flow with the 2D Transact team.
