- If you are using TLS 1.0 or 1.1 for local communications<\/a>, terminals on software versions v1.81 and later will not be able to process transactions.<\/li>
- Note, that in case of loss of internet connectivity<\/a> offline payments are only available for integrations that use local communications<\/a>.<\/li><\/ul><\/td>\n<\/tr>\n
\n Setup steps<\/strong><\/td>\n Before you begin: - Optionally, contact our Support Team<\/a> if you want to be informed about IP address changes<\/a> in a local communication. Provide them with:<\/li>
- The URL to an endpoint where you want to receive the new IP address of a terminal.<\/li>
- The access credentials of the endpoint.<\/li><\/ul><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
Network communications flow<\/h2>\n
When you make a transaction, your integration uses one of the following communications flows:<\/p>\n
- \n
- Local communications<\/a>.<\/li>\n
- Cloud communications<\/a>.<\/li>\n<\/ul>\n
Local communications<\/h3>\n
\n
![\"\"](\"\/user\/pages\/docs\/03.point-of-sale\/04.design-your-integration\/07.network-and-connectivity\/01.network-configuration\/Local_network.png\")
\n<\/a><\/p>\nCloud communications<\/h3>\n
\n
![\"\"](\"\/user\/pages\/docs\/03.point-of-sale\/04.design-your-integration\/07.network-and-connectivity\/01.network-configuration\/Cloud_network.png\")
\n<\/a><\/p>\nCommunications security<\/h2>\n
In accordance with PCI-DSS requirements, we use Transport Layer Security (TLS) 1.2 for secure data transmission over the internet.<\/p>\n
TLS 1.0 and 1.1 deprecation<\/h3>\n
In September 2022, with terminal software version 1.81, we deprecated TLS 1.0 and 1.1. This means that if you are still using TLS 1.0 or 1.1 for local communications<\/a>, terminals on software versions v1.81 and later will not be able to process transactions.<\/p>\n
\nIf you are using cloud communications<\/a>, nothing changes because our cloud endpoints do not accept TLS versions below 1.2.<\/p>\n<\/div>\n
Check your current TLS library version and cipher suite<\/h4>\n
If you are using the latest version of your operating system, you are probably already using TLS 1.2 or 1.3 protocols. For non-Android terminals on software version 1.80 and later, you can check the current TLS version, cipher, and URL by running the Local communications TLS test<\/a>.
\nYou can also check the TLS library version and cipher suites of your operating system:<\/p>\n- \n
- Windows: to list the supported cipher suites, open the PowerShell terminal and use the command \n
Get-TlsCipherSuite<\/code>\n<\/a>. For TLS versions supported on your Windows OS, refer to TLS protocol version support<\/a>.<\/li>\n- OS X \/ iOS: for supported TLS protocol versions and cipher suites, refer to Apple Platform Security<\/a> documentation.<\/li>\n
- Linux \/ Unix: to list the cipher suites with the supported TLS protocol version, open a shell terminal and use the command
openssl ciphers -v | column -t<\/code>.<\/li>\n<\/ul>\n\nYou can use websites like ciphersuite.info<\/a> to learn more about ciphers suites. For example, you can filter the list of cipher suites by TLS Version<\/strong>.<\/p>\n<\/div>\n
Supported ciphers<\/h4>\n
When you upgrade to TLS protocol version 1.2, make sure you use one of the following ciphers:<\/p>\n
- \n
- TLS 1.2 AES256-GCM-SHA384<\/li>\n
- TLS 1.2 AES256-SHA256<\/li>\n
- TLS 1.2 AES128-GCM-SHA256<\/li>\n
- TLS 1.2 AES128-SHA256<\/li>\n<\/ul>\n
Configuring your network<\/h2>\n
To configure your network for point of sale communications:<\/p>\n
- \n
- \n
If you need to allowlist IP addresses, add Adyen's in-person payments URLs to your firewall's allowlist.<\/p>\n
- \n
- Add Adyen's domains to your firewall's allowlist.
\nConfigure your firewall to allow outgoing HTTPS traffic from the IP addresses of your POS apps and terminals to:\n- \n
*.adyen.com<\/code><\/li>\n*.adyenpayments.com<\/code><\/li>\n<\/ul><\/li>\n<\/ol>\nAllowlisting should be based on the DNS name of these URLs. Your firewall should dynamically check for IP address updates, at least every 60 seconds.<\/p>\n
\nDo not hard-code Adyen's IP addresses, because these can change over time. We do not share a list of our IP addresses publicly.<\/p>\n<\/div>\n<\/li>\n
- \n
Open the ports:<\/p>\n
- \n
- tcp\/443<\/strong><\/span> to the internet.<\/li>\n
- \n
tcp\/8443<\/strong><\/span> on your LAN.<\/p>\n\n<\/li>\n<\/ul>\n<\/li>\n
- \n
If your integration uses local communications<\/a>:<\/p>\n
- \n
- Make sure that your terminal and POS app are connected to the same local network.<\/li>\n
- Protect the communications<\/a> between your POS app and the terminal.<\/li>\n<\/ul>\n<\/li>\n
- \n
If you are using a legacy setup where the cash register and the terminal communicate over a serial connection, use hardware flow control.<\/p>\n<\/li>\n<\/ol>\n
Configuring the terminal IP address<\/h2>\n
To send payments for online authorization, the terminal must have a valid IP address. There are several ways to assign an IP address to a terminal:<\/p>\n
- \n
- Dynamic IP<\/strong>: your DHCP server issues an IP address to the terminal on the fly.<\/li>\n
- DHCP reservation<\/strong>: on the DHCP server, you bind an IP address to the terminal's MAC address. The DHCP server then assigns the exact same IP address to the terminal each time. This is an alternative to using static IP addresses, especially if you are dealing with a large number of terminals.<\/li>\n
- Static IP<\/strong>: you enter the IP address and other network configuration details manually on the terminal.<\/li>\n<\/ul>\n
It is not possible to configure an IP address from the Customer Area.<\/p>\n
You cannot use a mix of dynamic and static IPs. The IP address of the terminal and the IP addresses of the DNS server and router must be either all dynamic, or all static.<\/p>\n
By default, DHCP is enabled on the payment terminal. With this setting, your DHCP server issues an IP address to the terminal, either dynamically or through DHCP reservation (if you have set that up). If you are using a V400m with a Bluetooth base station, the base station too has DHCP enabled and receives an IP address from your DHCP server.<\/p>\n
Recommendations<\/h3>\n
- \n
- \n
If it is possible to set the DHCP lease time on the DHCP server, set this to 24 hours or more. The lease time is the time that the terminal keeps an IP address before the DHCP server renews the terminal's lease on the IP address.<\/p>\n<\/li>\n
- \n
In an integration with cloud communications<\/em>, you should use dynamic IP addresses without DHCP reservation.<\/p>\n<\/li>\n
- \n
In an integration with local communications<\/em>, you should either use DHCP reservation, or manually configure static IP addresses.<\/p>\n<\/li>\n<\/ul>\n
Get notified about IP address changes<\/h3>\n
When a terminal's IP address changes in a local communication because of an issue or because it connected to a different access point, there is a risk of losing connection to your POS app. When this happens, you can configure your terminal to automatically send you the new IP address when it is back online.
\nTo configure this, you need to contact our Support Team<\/a> and provide them with:<\/p>\n- \n
- The URL to an endpoint where you want to receive the new IP address of a terminal.<\/li>\n
- The access credentials of the endpoint. <\/li>\n<\/ul>\n
When this feature is enabled, the terminal sends a webhook to that endpoint with the
uniqueTerminalId<\/code> and thenew_ip<\/code> address of the terminal. <\/p>\n\n<\/code-sample>\n<\/div>\n You can then use the terminals ID and the new IP address to reestablish the connection to the terminal from your POS app.<\/p>\n
Defining a static IP address<\/h3>\n
If you have an integration with local communications and cannot use a DHCP server with DHCP reservation, you need to disable DHCP and define a static IP address for the terminal.<\/p>\n
- \n
- On the connected terminal, open the Admin menu<\/a>.<\/li>\n
- Select Network<\/strong> and enter the Admin & Settings<\/a> passcode.<\/li>\n
- Open the settings for the network you are connected to.\n
\nThe terminal UI for network settings depends on the operating system version. You may need to long-press the network name or select the gear icon to access advanced settings.<\/p>\n<\/div><\/li>\n
- Under IP Settings<\/strong>, turn off DHCP<\/strong> or select Static<\/strong>.<\/li>\n
- Enter your network details:\n
- \n
- IP address of the terminal - this must be unique in the network<\/li>\n
- Subnet mask of the network<\/li>\n
- IP address of the router<\/li>\n
- IP addresses of the preferred DNS server (DNS1<\/strong><\/span>) and the alternate DNS server (DNS2<\/strong><\/span>)<\/li>\n<\/ul><\/li>\n
- Select Save<\/strong> or Apply<\/strong> to confirm.<\/li>\n<\/ol>\n
<\/li>\n<\/ol>\n
General networking recommendations<\/h2>\n
To prevent network issues from interfering with your point of sale transactions, we recommend that you:<\/p>\n
- \n
- \n
Use a segmented network, dedicated to point of sale communications.<\/p>\n<\/li>\n
- \n
Make a DNS server accessible from your local network. This should be able to resolve
*.adyen.com<\/code> and*.adyenpayments.com<\/code>.<\/p>\n\nIf you use a caching name-server, the Time to live (TTL) set by Adyen must be honored (60 seconds for Disaster Recovery).<\/p>\n<\/div>\n<\/li>\n
- \n
Follow our guidelines for IP address configuration<\/a>.<\/p>\n<\/li>\n
- \n
If you use intrusion detection (IDS) and prevention systems (IPS), ensure they are using up-to-date firmware and signatures. If these are out of date, the encrypted communications used by your integration may be disrupted.<\/p>\n<\/li>\n
- \n
Connect the whole POS system, including the terminals, to an uninterrupted power supply (UPS).<\/p>\n<\/li>\n
- \n
Use a cellular backup connection by:<\/p>\n
- \n
- Having an automatic cellular failover on your main router.<\/li>\n
- \n
Using terminals that have a built-in cellular connection, such as a portable or mobile terminal.<\/p>\n\n<\/li>\n<\/ul>\n<\/li>\n
- \n
If the network connection is fine but you are noticing issues with terminals and payments that seem to point to network connection problems, see Dropped network packets when the internet connection is available<\/a>.<\/p>\n<\/li>\n<\/ul>\n
Wi-Fi recommendations<\/h2>\n
To connect your payment terminals over Wi-Fi, your access point needs to support:<\/p>\n
- \n
- WPA\/WPA2-Enterprise encryption, or WPA\/WPA2-Personal encryption.<\/li>\n
- 2.4Ghz or 5Ghz frequencies.<\/li>\n<\/ul>\n
In addition, we recommend that you:<\/p>\n
- \n
- Configure a remote Wi-Fi profile<\/a>.\n\n
To use Enterprise encryption, using a remote Wi-Fi profile is mandatory.<\/p>\n<\/div><\/li>\n
- Use a dedicated private wireless network.<\/li>\n
- If your integration uses local communications<\/a>, disable the Wireless Isolation<\/em>, AP Isolation<\/em>, Client Isolation<\/em>, or other similar features on your access point.<\/li>\n
- Check what Wi-Fi frequencies and channels<\/a> your payment terminal supports in your region. <\/li>\n<\/ul>\n
Note that when the terminal indicates it is connected to your Wi-Fi network, this doesn't necessarily mean that it is connected to the internet. There can be issues with the connection from your Wi-Fi network to the internet.<\/p>\n
Handling loss of internet connectivity<\/h2>\n
\nWhen a transaction is declined because of a network connection issue, the error condition you receive for the transaction is UnreachableHost<\/strong><\/span>.<\/p>\n<\/div><\/div>\n
There are several ways you can continue making transactions when your primary internet connection is unavailable. These are:<\/p>\n
- \n
- Use a cellular failover connection<\/a>. When your primary internet connection fails, transactions are processed using the cellular connection of either a 3G\/4G payment terminal or a cellular router.<\/li>\n
- \n
Enable offline transactions<\/a>. This will allow you to continue processing transactions when your store has no internet connection.<\/p>\n
\nOffline payments are only available for integrations that use local communications<\/a>.<\/p>\n<\/div>\n
\nYou are fully liable for the risk of failed captures, chargebacks, and disputes related to offline payments.<\/p>\n<\/div>\n<\/li>\n<\/ul>\n
Using a proxy<\/h2>\n
Adyen-supplied payment terminals do not support proxy connections. If your network uses a proxy, allow your terminals to bypass the proxy and connect directly to the Adyen payments platform.<\/p>\n
See also<\/h2>\n
\n- \n Local communications\n <\/a><\/li>
- \n Protecting local communications\n <\/a><\/li>
- \n Cloud communications\n <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/point-of-sale\/design-your-integration\/network-and-connectivity\/network-configuration","articleFields":{"description":"Recommendations for configuring your network.","last_edit_on":"07-10-2020 09:29","page_id":"e0811c52-e107-4727-ba2b-21c486dce38c","feedback_component":true,"filters_component":false,"decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/point-of-sale\/design-your-integration\/network-and-connectivity\/network-configuration","title":"Network configuration","content":"When you make a point-of-sale transaction, your POS app, terminal, and Adyen need to be able to communicate with one another. The flow of this communication depends on whether your integration uses local or cloud communications. To enable this communication, you need to configure your network to allow access to specific ports and addresses.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nA Terminal API integration with payment terminals.\n\n\nLimitations\nTake into account the following limitations: If you are using TLS 1.0 or 1.1 for local communications, terminals on software versions v1.81 and later will not be able to process transactions.Note, that in case of loss of internet connectivity offline payments are only available for integrations that use local communications.\n\n\nSetup steps\nBefore you begin: Optionally, contact our Support Team if you want to be informed about IP address changes in a local communication. Provide them with:The URL to an endpoint where you want to receive the new IP address of a terminal.The access credentials of the endpoint.\n\n\n\nNetwork communications flow\nWhen you make a transaction, your integration uses one of the following communications flows:\n\nLocal communications.\nCloud communications.\n\nLocal communications\n\n \n\nCloud communications\n\n \n\nCommunications security\nIn accordance with PCI-DSS requirements, we use Transport Layer Security (TLS) 1.2 for secure data transmission over the internet.\nTLS 1.0 and 1.1 deprecation\nIn September 2022, with terminal software version 1.81, we deprecated TLS 1.0 and 1.1. This means that if you are still using TLS 1.0 or 1.1 for local communications, terminals on software versions v1.81 and later will not be able to process transactions.\n\nIf you are using cloud communications, nothing changes because our cloud endpoints do not accept TLS versions below 1.2.\n\nCheck your current TLS library version and cipher suite\nIf you are using the latest version of your operating system, you are probably already using TLS 1.2 or 1.3 protocols. For non-Android terminals on software version 1.80 and later, you can check the current TLS version, cipher, and URL by running the Local communications TLS test.\nYou can also check the TLS library version and cipher suites of your operating system:\n\nWindows: to list the supported cipher suites, open the PowerShell terminal and use the command \n Get-TlsCipherSuite\n. For TLS versions supported on your Windows OS, refer to TLS protocol version support.\nOS X \/ iOS: for supported TLS protocol versions and cipher suites, refer to Apple Platform Security documentation.\nLinux \/ Unix: to list the cipher suites with the supported TLS protocol version, open a shell terminal and use the command openssl ciphers -v | column -t.\n\n\nYou can use websites like ciphersuite.info to learn more about ciphers suites. For example, you can filter the list of cipher suites by TLS Version.\n\nSupported ciphers\nWhen you upgrade to TLS protocol version 1.2, make sure you use one of the following ciphers:\n\nTLS 1.2 AES256-GCM-SHA384\nTLS 1.2 AES256-SHA256\nTLS 1.2 AES128-GCM-SHA256\nTLS 1.2 AES128-SHA256\n\nConfiguring your network\nTo configure your network for point of sale communications:\n\n\nIf you need to allowlist IP addresses, add Adyen's in-person payments URLs to your firewall's allowlist.\n\nAdd Adyen's domains to your firewall's allowlist.\nConfigure your firewall to allow outgoing HTTPS traffic from the IP addresses of your POS apps and terminals to:\n\n*.adyen.com\n*.adyenpayments.com\n\n\nAllowlisting should be based on the DNS name of these URLs. Your firewall should dynamically check for IP address updates, at least every 60 seconds.\n\nDo not hard-code Adyen's IP addresses, because these can change over time. We do not share a list of our IP addresses publicly.\n\n\n\nOpen the ports:\n\ntcp\/443 to the internet.\n\ntcp\/8443 on your LAN.\n\n\n\n\n\nIf your integration uses local communications:\n\nMake sure that your terminal and POS app are connected to the same local network.\nProtect the communications between your POS app and the terminal.\n\n\n\nIf you are using a legacy setup where the cash register and the terminal communicate over a serial connection, use hardware flow control.\n\n\nConfiguring the terminal IP address\nTo send payments for online authorization, the terminal must have a valid IP address. There are several ways to assign an IP address to a terminal:\n\nDynamic IP: your DHCP server issues an IP address to the terminal on the fly.\nDHCP reservation: on the DHCP server, you bind an IP address to the terminal's MAC address. The DHCP server then assigns the exact same IP address to the terminal each time. This is an alternative to using static IP addresses, especially if you are dealing with a large number of terminals.\nStatic IP: you enter the IP address and other network configuration details manually on the terminal.\n\nIt is not possible to configure an IP address from the Customer Area.\nYou cannot use a mix of dynamic and static IPs. The IP address of the terminal and the IP addresses of the DNS server and router must be either all dynamic, or all static.\nBy default, DHCP is enabled on the payment terminal. With this setting, your DHCP server issues an IP address to the terminal, either dynamically or through DHCP reservation (if you have set that up). If you are using a V400m with a Bluetooth base station, the base station too has DHCP enabled and receives an IP address from your DHCP server.\nRecommendations\n\n\nIf it is possible to set the DHCP lease time on the DHCP server, set this to 24 hours or more. The lease time is the time that the terminal keeps an IP address before the DHCP server renews the terminal's lease on the IP address.\n\n\nIn an integration with cloud communications, you should use dynamic IP addresses without DHCP reservation.\n\n\nIn an integration with local communications, you should either use DHCP reservation, or manually configure static IP addresses.\n\n\nGet notified about IP address changes\nWhen a terminal's IP address changes in a local communication because of an issue or because it connected to a different access point, there is a risk of losing connection to your POS app. When this happens, you can configure your terminal to automatically send you the new IP address when it is back online.\nTo configure this, you need to contact our Support Team and provide them with:\n\nThe URL to an endpoint where you want to receive the new IP address of a terminal.\nThe access credentials of the endpoint. \n\nWhen this feature is enabled, the terminal sends a webhook to that endpoint with the uniqueTerminalId and the new_ip address of the terminal. \n\n \n\nYou can then use the terminals ID and the new IP address to reestablish the connection to the terminal from your POS app.\nDefining a static IP address\nIf you have an integration with local communications and cannot use a DHCP server with DHCP reservation, you need to disable DHCP and define a static IP address for the terminal.\n\nOn the connected terminal, open the Admin menu.\nSelect Network and enter the Admin & Settings passcode.\nOpen the settings for the network you are connected to.\n\nThe terminal UI for network settings depends on the operating system version. You may need to long-press the network name or select the gear icon to access advanced settings.\n\nUnder IP Settings, turn off DHCP or select Static.\nEnter your network details:\n\nIP address of the terminal - this must be unique in the network\nSubnet mask of the network\nIP address of the router\nIP addresses of the preferred DNS server (DNS1) and the alternate DNS server (DNS2)\n\nSelect Save or Apply to confirm.\n\n\n\nGeneral networking recommendations\nTo prevent network issues from interfering with your point of sale transactions, we recommend that you:\n\n\nUse a segmented network, dedicated to point of sale communications.\n\n\nMake a DNS server accessible from your local network. This should be able to resolve *.adyen.com and *.adyenpayments.com.\n\nIf you use a caching name-server, the Time to live (TTL) set by Adyen must be honored (60 seconds for Disaster Recovery).\n\n\n\nFollow our guidelines for IP address configuration.\n\n\nIf you use intrusion detection (IDS) and prevention systems (IPS), ensure they are using up-to-date firmware and signatures. If these are out of date, the encrypted communications used by your integration may be disrupted.\n\n\nConnect the whole POS system, including the terminals, to an uninterrupted power supply (UPS).\n\n\nUse a cellular backup connection by:\n\nHaving an automatic cellular failover on your main router.\n\nUsing terminals that have a built-in cellular connection, such as a portable or mobile terminal.\n\n\n\n\n\nIf the network connection is fine but you are noticing issues with terminals and payments that seem to point to network connection problems, see Dropped network packets when the internet connection is available.\n\n\nWi-Fi recommendations\nTo connect your payment terminals over Wi-Fi, your access point needs to support:\n\nWPA\/WPA2-Enterprise encryption, or WPA\/WPA2-Personal encryption.\n2.4Ghz or 5Ghz frequencies.\n\nIn addition, we recommend that you:\n\nConfigure a remote Wi-Fi profile.\n\nTo use Enterprise encryption, using a remote Wi-Fi profile is mandatory.\n\nUse a dedicated private wireless network.\nIf your integration uses local communications, disable the Wireless Isolation, AP Isolation, Client Isolation, or other similar features on your access point.\nCheck what Wi-Fi frequencies and channels your payment terminal supports in your region. \n\nNote that when the terminal indicates it is connected to your Wi-Fi network, this doesn't necessarily mean that it is connected to the internet. There can be issues with the connection from your Wi-Fi network to the internet.\nHandling loss of internet connectivity\n\nWhen a transaction is declined because of a network connection issue, the error condition you receive for the transaction is UnreachableHost.\n\nThere are several ways you can continue making transactions when your primary internet connection is unavailable. These are:\n\nUse a cellular failover connection. When your primary internet connection fails, transactions are processed using the cellular connection of either a 3G\/4G payment terminal or a cellular router.\n\nEnable offline transactions. This will allow you to continue processing transactions when your store has no internet connection.\n\nOffline payments are only available for integrations that use local communications.\n\n\nYou are fully liable for the risk of failed captures, chargebacks, and disputes related to offline payments.\n\n\n\nUsing a proxy\nAdyen-supplied payment terminals do not support proxy connections. If your network uses a proxy, allow your terminals to bypass the proxy and connect directly to the Adyen payments platform.\nSee also\n\n\n Local communications\n \n Protecting local communications\n \n Cloud communications\n \n","type":"page","locale":"en","boost":16,"hierarchy":{"lvl0":"Home","lvl1":"In-person payments","lvl2":"Design your integration","lvl3":"Network and connectivity","lvl4":"Network configuration"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/point-of-sale","lvl2":"https:\/\/docs.adyen.com\/point-of-sale\/design-your-integration","lvl3":"https:\/\/docs.adyen.com\/point-of-sale\/design-your-integration\/network-and-connectivity","lvl4":"\/point-of-sale\/design-your-integration\/network-and-connectivity\/network-configuration"},"levels":5,"category":"In-person payments","category_color":"green","tags":["Network","configuration"]},"articleFiles":{"Cloud_network.png":"
![\"\"](\"https:\/\/docs.adyen.com\/user\/pages\/docs\/03.point-of-sale\/04.design-your-integration\/07.network-and-connectivity\/01.network-configuration\/Cloud_network.png\")
","Local_network.png":"![\"\"](\"https:\/\/docs.adyen.com\/user\/pages\/docs\/03.point-of-sale\/04.design-your-integration\/07.network-and-connectivity\/01.network-configuration\/Local_network.png\")
"}}
- \n Protecting local communications\n <\/a><\/li>
- \n
- Configure a remote Wi-Fi profile<\/a>.\n
- \n
- Select Save<\/strong> or Apply<\/strong> to confirm.<\/li>\n<\/ol>\n
- Select Network<\/strong> and enter the Admin & Settings<\/a> passcode.<\/li>\n
- On the connected terminal, open the Admin menu<\/a>.<\/li>\n
- \n
- DHCP reservation<\/strong>: on the DHCP server, you bind an IP address to the terminal's MAC address. The DHCP server then assigns the exact same IP address to the terminal each time. This is an alternative to using static IP addresses, especially if you are dealing with a large number of terminals.<\/li>\n
- \n
- \n
- Add Adyen's domains to your firewall's allowlist.
- \n
- OS X \/ iOS: for supported TLS protocol versions and cipher suites, refer to Apple Platform Security<\/a> documentation.<\/li>\n
- Cloud communications<\/a>.<\/li>\n<\/ul>\n
- Local communications<\/a>.<\/li>\n
- Note, that in case of loss of internet connectivity<\/a> offline payments are only available for integrations that use local communications<\/a>.<\/li><\/ul><\/td>\n<\/tr>\n