Use Encryption with Latest Crypto APIs

Oracle Payments upgrades its security infrastructure to use newer Crypto APIs for sensitive payment data.

When you initiate a system key change, a concurrent program is launched to re-encrypt credit card and bank account data using the new Crypto APIs. This supports current security standards for stored payment instruments.

Steps to enable and configure

1. Apply the required Oracle Payments release update or patch level for the feature.
2. Confirm the related Payables, Receivables, Cash Management, and Payments responsibilities and function security are assigned to the users who will configure or operate the process.
3. Validate the setup in a test environment with representative banks, payment files, and customer or supplier bank accounts before using the feature in production.
4. Plan the system key change with database, security, and application administrators, including backup, maintenance window, and rollback procedures.
5. Initiate the supported system key change process and monitor the concurrent program that re-encrypts credit card and bank account data.
6. Validate payment instrument entry, authorization, funds capture, and funds disbursement flows after re-encryption completes.

Tips and considerations

• Treat this as a sensitive security maintenance activity and restrict access to key-management functions.
• Schedule the re-encryption process during a maintenance window if payment instrument volume is high.
• Do not interrupt the re-encryption concurrent program; retain request logs and completion evidence for audit.