Amount, merchant reference, session details, and optional redemption data are attached to a QR request.
Technology
The gateway model behind QR checkout
A technical view of the request, scan, redemption logic, decision, and merchant result.
State model
Keep every checkout request readable
The value of QR payment is not the code. It is the state model behind the code.
A supported wallet or app reads the request and shows the customer what they are approving.
The request can be authorized, cancelled, expired, or left pending.
Counter staff get a readable result before closing the sale.
Gateway role
Coordinate checkout without replacing the processor
SkanPay is best explained as the coordination layer between checkout, wallet participation, redemption logic, and payment processing.
Route the request
A gateway helps collect and route checkout information so the right systems know what should happen next.
Keep money movement separate
Payment processors and banks remain responsible for authorization, clearing, and settlement where applicable.
Validate offers in context
Coupon or voucher logic can be coordinated with the checkout request instead of being treated as a separate afterthought.
Responsibilities
Separate merchant, customer, and partner roles
Clear roles make QR checkout easier to explain, support, and integrate.
Present request and read status
The store needs a clean checkout prompt and a final result staff can trust.
Review and approve
The customer needs merchant details, amount, and a familiar app approval experience.
Handle app participation
Payment, wallet, e-commerce, loyalty, or offer apps need a defined checkout boundary.
Integration touchpoints
Where deeper technical conversations begin
SkanPay keeps public claims focused, then uses direct conversations to discuss partner-specific requirements.
01QR request format
02Supported app or wallet behavior
03Status and timeout handling
04Coupon or voucher validation
05Merchant confirmation display