If offline processing is enabled on a terminal, the terminal can still accept payments when it can’t connect to the gateway, for example, if the terminal loses internet connection.
When a merchant runs a payment and the terminal is offline, the terminal saves the payment details and information about the transaction. When the terminal connects to the gateway, it sends the payment details to the gateway to process the payment.
Note: Offline processing should be used only temporarily as there are risks to the merchant. For more information about the risks, see risks of offline processing.
How it works
Mermaid source
flowchart TD
A([Run a payment]):::blue
B[Customer presents their card]:::neutral
C{Can the terminal connect to the gateway?}:::yellow
D([Payment sent to the gateway for processing]):::green
E{Is the terminal enabled for offline processing?}:::yellow
F([Payment declined]):::red
G[Terminal saves the payment details and transaction information]:::neutral
H{Can the terminal connect to the gateway?}:::yellow
I([Payment sent to the gateway for processing]):::green
A --> B --> C
C -->|Yes| D
C -->|No| E
E -->|No| F
E -->|Yes| G --> H
H -->|Yes| I
H -->|No| G
classDef blue fill:#0051C2,stroke:#001D4E,color:#FFFFFF
classDef green fill:#00E0B8,stroke:#001D4E,color:#001D4E
classDef yellow fill:#F4F7FE,stroke:#0051C2,color:#0051C2,font-size:15px
classDef red fill:#DC2626,stroke:#991B1B,color:#FFFFFF
classDef neutral fill:#E5E5E5,stroke:#636363,color:#001D4E
Risks of offline processing
If the terminal can’t connect to the gateway, the gateway can’t authorize the payment. There are many risks involved with accepting an unauthorized payment including:
- Customer could use a fraudulent card.
- Customer might not have the funds to pay.
- Customer could claim that they didn't authorize the payment and raise a chargeback.
Important: The merchant is liable for funds that they can't capture from a cardholder's account and chargebacks arising from offline payments.