Technical enough to validate. Simple enough to deploy.
Understand the integration model, device pairing, data flow, access boundaries and reliability for an Extend rollout.
ERP/POS or PDF -> Extend backend -> paired tablet -> tax refund provider -> result.
ERP/POS connector or PDF
Supported direct connectors or PDF intake.
Extend backend
Authoritative routing and tenant enforcement.
Paired tablet
Customer-facing workflow on the correct device.
Provider flow
Configured tax refund provider processing.
Result
Status or reference returns to the supported flow.
Short-lived QR-based device pairing
A one-time pairing flow links the workstation or connector to the appropriate tablet without placing long-lived provider secrets in the QR payload.
Separate user and machine identities
Access is scoped by merchant, branch and device relationships with server-side enforcement.
Configuration is separate from workflow payloads
Persistent operational configuration and metadata are handled separately from active shopper and invoice workflow data.
Real-time notification plus authoritative recovery
The backend maintains recoverable transaction state rather than depending only on an uninterrupted live connection.
Supported connectors run in the merchant environment
The customer-facing tablet runs the Extend app; connector prerequisites are confirmed during the technical review.
Schedule a technical review.
Architecture, integration, deployment or security.