Updated API Protocol and Cipher Support

Updated 1/8/25

OVERVIEW

Starting September 1st, 2024, PAR will begin updating all PAR POS™ API endpoints to the latest PCI-DSS compliant TLS 1.2/1.3 cipher suites.

This change will be applied to all testing environments (see table below) by August 5th, 2024. This provides time for testing and remediation of any issues before we begin our production roll out.

After this update we will only support TLS 1.2 and 1.3 protocols, with the following list of supported ciphers:

• TLS_AES_128_GCM_SHA256
• TLS_AES_256_GCM_SHA384
• TLS_CHACHA20_POLY1305_SHA256
• ECDHE-ECDSA-AES128-GCM-SHA256
• ECDHE-RSA-AES128-GCM-SHA256
• ECDHE-ECDSA-AES256-GCM-SHA384
• ECDHE-RSA-AES256-GCM-SHA384

For questions regarding this information, please contact API Support at api.support@partech.com.

TEST PLAN FOR API PARTNERS

PAR has extensively tested the following related to the new API changes:

• Positive API scenarios verified for all call types
• Negative API scenarios verified for all call types
• Client-specific test cases related to API
• Load testing of API calls

However, we encourage developers that utilize our API to verify their mission critical workflows and ensure they remain unchanged by performing the following tasks:

Who? Ideally all customers and API vendors understand the importance of performing independent testing of the APIs

What? Customers/API vendors are encouraged to:

1. Identify API calls, use cases, and workflows used with PAR POS.
2. Fully retest all API calls, use cases, and workflows in an environment utilizing the Updated APIs.
3. Verify you are still able to connect and make calls successfully.

Where? Environments with latest Protocols and Cipher Suites by 8/5/2024:

• APIInt
• Early Experience
• Customer-specific UAT environments