Offline payments | Adyen Docs (2024)

To process a transaction, the payment terminal needs to have internet access. When there's a temporary loss of internet connectivity, you can continue making point-of-sale payments by enabling offline payments. Offline payments are possible either:

• Using a standalone payment terminal. This must be a terminal model with a built-in printer.
• Or using local communications for your integration.

How it works

1. You initiate a payment like you usually do.
2. When the shopper completes the payment, the terminal tries to reach the Adyen payments platform, but is unable to establish a connection.
3. The terminal verifies whether the payment can be completed offline, by running the following checks:
   • Are one or more types of offline payment enabled? If no, the payment is Declined.
   • Is the card configured by the issuer to process offline payments?
   • Has the payment terminal reached its maximum number of store-and-forward offline payments yet?
   • Is the transaction amount within the maximum transaction amount for the type of offline payment?
   • Does the payment scheme support offline payments?
4. If Approved, the terminal stores the card data and details of the transaction.
   • If you are using a standalone terminal, it will print the receipt.
   • In a local integration, the terminal generates a transaction response including data you can use to generate a receipt.
5. Later, when the terminal is able to connect to the internet again, it sends the stored payments to the Adyen payments platform for further processing.

Risk with offline payments

When you enable offline payments, your integration approves payments before the money is received from the shopper's account. That means it is possible that you will not receive the money for the goods that are taken by the shopper. There's also a higher risk that card fraud goes undetected.

You are fully liable for the risk of failed captures, chargebacks, and disputes related to payments that you process offline.

To reduce your exposure to these risks, you need to set a transaction floor limit before your integration can make offline payments. This is a maximum per-transaction amount that your terminals can approve while they are offline.

Types of offline payment

There are two types of payment that you can do while your integration is offline. Each varies by card type, region, and the risk of the payment being declined by the issuer when it is processed:

• Offline EMV payments: the payment terminal verifies that the PIN entered by the shopper matches the PIN on the EMV chip embedded in the card, and then asks the card to approve the payment. Whether the transaction is approved, depends on how the issuer configured the card. Because the card is in control, the payment can be processed in the clearing stream directly. This ensures a higher approval rate.
  Offline EMV transactions are supported by most major credit card schemes. Most debit cards do not support this type of payment.

• Store-and-forward payments: the payment terminal approves payments without any verification. Because of this, the risk of payments being declined by the issuer is higher than for offline EMV transactions. In practice the authorization rates range from 95% in some industries to several percentage points higher.

  See Also

  The 4 advantages & disadvantages of online bankingAre Online Banks Safe?How to Open Savings Account Offline?What Do You Need to Open a Bank Account? - NerdWallet

  Store and Forward is supported for contact chip and contactless transactions by the major credit and debit card schemes and also by some local card schemes. Any Cardholder Verification Method (CVM), such as PIN and signature, can be processed.
  Store and Forward is not supported for most local card schemes, QR code wallets, magnetic stripe transactions, or cashbacks.
  Contact our Support Team to learn whether Store and Forward is supported for a specific local card scheme.

If you enable both types of offline payment, the terminal will try offline EMV first, then Store and Forward.

Configure offline payments

To set up offline payments:

1. Ask our Support Team to enable offline payments and give them the following information:

   • Type of offline payments you want to enable: offline EMV and/or Store and Forward.

   • Whether you want to enable Store and Forward for payments that normally require a PIN as CVM.
     This includes initial transactions that create recurring details for a shopper for loyalty use cases or later recurring payments using a token.

   • For offline EMV, the following limits:

     • Chip floor limit: the maximum transaction amount that the terminal accepts for an offline EMV transaction where the shopper inserts their chip card into the chip card reader. Transactions above this amount will be declined.
     • Offline swipe limit: the maximum transaction amount up to which swiped cards are accepted offline.

   • For Store and Forward, the following limits:

     • Store-and-forward max. amount: the maximum transaction amount that the terminal accepts for a store-and-forward transaction. Transactions above this amount will be declined.
     • Max. payments: the maximum number of store-and-forward transactions per terminal that you can process while offline.

   • For Store and Forward, the Supported card types: normally, store-and-forward settings apply to all credit, debit, and prepaid cards in your account. If you want to exclude some of them, inform our Support Team.

2. After offline payments have been enabled, check the settings in your Customer Area:

   1. Go to In-person payments > Terminal settings > Payment features.
   2. For offline EMV, check the settings under Offline processing.
   3. For Store and Forward, check the settings under Store-and-forward payments.

3. Take care of any extra configuration on your side to reconcile payments that are made offline.

Recognize the offline payment response

Compared to an online payment response, the Terminal API response for an offline payment differs in some respects. Data that is generated by the Adyen payments platform, such as the PSP reference, is missing because your integration is unable to connect to Adyen. Authorisation data is missing as well, because the issuer hasn't authorized the payment yet. The response also includes some values to indicate the payment took place offline.

These differences are important because:

• They have consequences for refunding and reconciling offline payments.
• If your POS system normally uses the PSP reference, you need to make sure it is also able to handle responses that do not include a PSP reference.

To recognize store-and-forward payments in your Customer Area, under Transactions > Payments, use the gear icon to show the Store and forward column.

Offline payment response details

The PaymentResponse for an offline transaction has the following characteristics:

• POIData.POITransactionID.Transaction.ID: misses the PSP reference. Only contains the tender reference.

• PaymentResult.AuthenticationMethod: OfflinePIN

• PaymentResult.OnlineFlag: false

• PaymentResult.PaymentAcquirerData: misses the AcquirerTransactionID and ApprovalCode parameters.

• Response.AdditionalResponse includes:

  • offline: true

  • offlineAuthCode: indicates the type of offline payment.

    • Offline approved indicates an offline EMV payment.

    • Failed go online offline declined indicates a store-and-forward transaction.

  • unconfirmedBatchCount: the number of payments that the terminal hasn't been able to send to the Adyen payments platform.

• There are also fields missing from the Response.AdditionalResponse. The most important missing data are:

  • authorization data: authCode, authorisationMID, authorisedAmountCurrency, authorisedAmountValue, refusalReasonRaw
  • PSP reference: pspReference, transactionReferenceNumber

Below is an example of an offline EMV or store-and-forward payment response.

The next example shows the AdditionalResponse (converted to JSON format) for an offline EMV payment.

The next example shows the AdditionalResponse (converted to JSON format) for a store-and-forward payment.

Refunding while offline

While your integration is offline, it is possible to issue refunds. However, there are some restrictions:

• You can only make unreferenced refunds. Referenced refunds are not supported.
• The payment terminal will try to process the refund as an offline EMV transaction. This means that the request may be declined. Processing the refund as a store-and-forward transaction is not supported.
• To allow making refunds while offline, you need to contact our Support Team to set an Offline refund maximum transaction amount.

To refund a payment when there is no internet access:

• Make an unreferenced refund using a PaymentRequest with PaymentType Refund. To make reconciliation easier, we recommend including the tender reference of the original payment in SaleData.SaleTransactionID.TransactionID.

Refunding offline payments when back online

If your internet connection is restored and you want to refund a payment that was completed offline, you need to manage the fact that the response for the offline payment doesn't contain the PSP reference.

Use one of these options, taking into account that referenced refunds are safer than unreferenced refunds:

• Make an unreferenced refund using a PaymentRequest with PaymentType Refund. To make reconciliation easier, we recommend including the tender reference of the original payment in SaleData.SaleTransactionID.TransactionID.

• Make a referenced refund using a ReversalRequest with the tender reference of the offline payment and the POIID of the payment terminal that was used for the offline payment. Even though you don't know the PSP reference, you can still make a referenced refund in this way.

• Find the PSP reference for the offline payment in your Customer Area or in the webhook (if you set that up). Then make a regular referenced refund using a ReversalRequest with the PSP reference.

Reconcile offline payments

Because the PSP reference is generated by the Adyen payments platform, the Terminal API response for an offline transaction does not have a PSP reference.
If you are using the PSP reference for reconciliation, we recommend you set up webhooks. When your integration is online again, you will receive webhooks for the stored payments, and these webhooks include the PSP reference.
As an alternative, you can use the tender reference, which is generated by the terminal, to reconcile your payments.
Also note that you can add the POS Store and Forward indicator column to your Received payment details report.

Because offline payments can be declined by the issuer, your financial operations specialist needs to set up a method of handling this type of declines. This would mean the goods are provided to the shopper and the money is not received for this type of payment. This is the inherent risk of processing store-and-forward transactions.

Test offline payments

To test an offline payment, proceed as follows.

1. Make sure offline payments are configured.
2. Send a payment request to your test terminal and force an internet connection failure.
   The most convenient way to force an internet connection failure depends on your network setup. For example, you could unplug the Ethernet cable from a switch. Or if you're using the P400 plus, you could unplug the Ethernet cable from the payment terminal.
3. Complete the offline payment using your test card. The test card enforces the configured offline limits.
4. Verify that you are handling the offline payment response correctly.
5. Re-enable the internet connection.

6. Verify the result:

   • View the details of the test payment in your test Customer Area under Transactions > Payments.
   • View the webhooks received for the test payment (if you set up webhooks).
   • View the Received payment details report.

   This information should help your financial operations specialist to adapt your financial system to offline payments.

See also