2D Transact
Your questions, answered.
Understand the mechanism, the channels and the responsibilities of connected platforms.
How 2D fits.
Does 2D hold customer funds?
The mechanism coordinates transactions. Account balances, custody and settlement are handled by the participating bank, wallet or service platform.
Is it limited to QR codes?
No. A transaction can be referenced by a numeric code, with QR providing another way to present that reference. Responding channels depend on the integration.
Can feature phones participate?
Yes, where an integrated USSD or other suitable service connects the phone journey to the controller. A feature phone alone does not create that integration.
Can it handle crypto, gold, rewards or time units?
The mechanism is value agnostic. The connected platforms must support the relevant accounts, units of value and execution workflow.
Is a customer anonymous?
Responder-independent creation means the request can be created before the responder is known. The connected platform still authenticates and authorises its customer and applies its required checks.
Does it settle without connectivity?
The connected operation described here requires access to the controller. Offline concepts need separate design and validation and are not advertised here as deployed functionality.
Does every integration offer all programmable rules?
No. Supported attributes and execution capabilities must be confirmed for each integration and commercial implementation.
Connect your next transaction.
Discuss your platform, channels, units of value and intended transaction flow with the 2D Transact team.
