A retail customer journey may span more than one channel. An in-store sale, online order or return at another branch may belong to the same business relationship. MagicPay's retail approach considers checkout and payment records alongside channel and branch information.
From checkout to payment result
The sale amount and order reference should reach the terminal consistently, and the payment result must link back to the checkout. Test controls to prevent duplicate charges if a cashier restarts the same transaction.
- Map device, branch and checkout identifiers.
- Separate card, cash and other method records.
- Define partial refund and cross-branch return conditions.
Connect the data before connecting the channels
Review how customer and order references are held across systems. An omnichannel experience can be planned only where permissions, data and provider scope align.
Start with a pilot store
Test the terminal model, network conditions and checkout software in a real store workflow. Include end-of-day differences and support scenarios in acceptance testing. The payment layer does not automatically replace inventory or fiscal document systems.