Upcoming Updates

Stay informed about our upcoming API changes and enhancements. We’ll announce these updates as they become available. If you have any questions, please contact your Corpay representative.

IP Whitelisting

ETA: Q1 2026

We are enhancing IP Whitelisting to improve security, flexibility, and performance across our API services.

Key updates include:

• Whitelisting at both client and partner levels
• Support for IPv4, IPv6, and valid CIDR ranges (for example, 192.0.2.0/24)
• Removal of SQL LIKE syntax (wildcards such as % will no longer be supported)
• Improved access control with cached authentication for faster performance

Confirmation of Payee (CoP) and Verification of Payee (VoP)

ETA: Q1 2026

UK and EU payment regulatory bodies have introduced new name-checking protocols requiring banks, financial institutions, and payment service providers like Corpay to validate that payee details are correct and exactly match the associated bank account information. On Corpay's internal workflow, we have now enabled:

• UK’s Confirmation of Payee (CoP) protocol for all incoming and outgoing GBP payments made via FPS, Bacs, and CHAPS.
• EU’s Verification of Payee (VoP) protocol for all incoming and outgoing EUR payments made via SEPA Credit Transfer (CT) or SEPA Instant eligible BICs (for clients whose payment accounts are governed under our Ireland entity and its branches).

We are now integrating CoP and VoP protocols into our REST API workflows. Key updates include:

• Migration to updated versions of our existing beneficiary creation endpoints.
• Introduce new verification endpoints.

We'll keep you informed about the new endpoints and sample responses as we roll out the updates.

Beneficiary Rules (Template Guide) Endpoint Update

ETA: Q2 2026

An updated version of the GET Beneficiary Rules endpoint will be released. Key updates include:

• Introduce new endpoints - api/template-guide-rules and api/{clientCode}/{clientDivisionId}/template-guide-rules
• The API response will now return a list of accepted region values based on the specified destinationCountry and bankCountry parameters, ensuring compliance when creating or editing beneficiaries via the POST Create/Edit Bene.
• A new optional routingCode parameter will support accurate beneficiary rule retrieval for CAD (Canada), addressing issues caused by varying account number digit lengths across Canadian banks and institutions.

We'll keep you informed about the new endpoints and sample responses as we roll out the updates.

Multi-Currency Accounts (MCA) Reporting Enhancements

ETA: Q2 2026

To improve our MCA reporting, we'll introduce new bank-style statements via an MCA Statement endpoint, which will eventually replace the existing GET Multi-Currency Accounts History endpoint. Both endpoints will run in parallel during the transition period to support integration updates. We'll keep you informed about the detailed specifications, sample responses, and API deprecation timelines as we roll out the updates.