Root Cause

• Invalid or missing encryption keys: The transaction request could not be securely processed due to missing or expired encryption certificates or keys.

• Corrupted or improperly formatted encrypted data: The data sent in the transaction payload was not correctly encrypted, leading to decryption failure at the gateway.

• Issues is date/time setup: Your server-side date/time is not set up correctly. For example, your server side is set to 1975 when it is 2020, or the date is not within 24 hours of the current time.

• Mismatch in encryption protocols: The client system and payment gateway are using incompatible or outdated encryption protocols.

• Security configuration errors: Incorrect configuration of encryption libraries or certificates on the client or server side.

Troubleshooting and Solutions

• Verify that all encryption keys and certificates used for transaction processing are valid, properly configured, and not expired.

• Ensure that transaction data is correctly encrypted before sending it to the gateway.

• Check the server-side date/time configuration.

• Confirm that both client systems and the gateway support compatible and up-to-date encryption protocols (e.g., TLS 1.2 or higher).

• Retry the transaction only after resolving encryption configuration issues.

• If the problem persists, contact support@chargebee.com to investigate and resolve any server-side encryption issues.