EXTEND
For IT Teams

Technical enough to validate. Simple enough to deploy.

Understand the integration model, device pairing, data flow, access boundaries and reliability for an Extend rollout.

Conceptual architecture

ERP/POS or PDF -> Extend backend -> paired tablet -> tax refund provider -> result.

A

ERP/POS connector or PDF

Supported direct connectors or PDF intake.

B

Extend backend

Authoritative routing and tenant enforcement.

C

Paired tablet

Customer-facing workflow on the correct device.

D

Provider flow

Configured tax refund provider processing.

E

Result

Status or reference returns to the supported flow.

Pairing

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.

Identity

Separate user and machine identities

Access is scoped by merchant, branch and device relationships with server-side enforcement.

Retention

Configuration is separate from workflow payloads

Persistent operational configuration and metadata are handled separately from active shopper and invoice workflow data.

Reliability

Real-time notification plus authoritative recovery

The backend maintains recoverable transaction state rather than depending only on an uninterrupted live connection.

Deployment

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.

Book technical / integration review