2D Transact
Give each transaction its instructions.
Connect supported rules, destinations and units of value to a transaction request.
Configure the intended behaviour.
Value & destination
Specify the unit of value and supported destination relevant to the transaction.
Validity & conditions
Use supported attributes such as expiry or response eligibility where available in the implementation.
Allocation & routing
Coordinate supported splits or designated wallets when the connected systems implement those capabilities.
Illustrative transaction: a merchant reward.
A merchant presents a purchase request. The customer authorises through their connected wallet. The implementation coordinates payment and, where configured and supported, a reward allocation. Each step has a defined outcome for the participating systems to record.
Rule availability must be confirmed during solution design. A transaction reference does not replace the underlying platform’s permissions, balance checks or settlement controls.
Connect your next transaction.
Discuss your platform, channels, units of value and intended transaction flow with the 2D Transact team.
