Changelog
Global Payments API
This page contains updates introduced in Global Payments API.
Version 1.2.3 | June 8, 2026
This section contains updates introduced in Global Payments API 1.2.3.
1.2.3
| Summary | Description |
|---|---|
| Updated SEPA Instant postal address guidance | Refined PostalAddress requirements and guidance for SEPA Instant, including additional rules for structured address usage and future rulebook constraints (for example, requiring townName and country when PostalAddress is present). |
| Added CBPR+/SEPA mock request examples | Added CBPR+/SEPA sample payloads to POST /payments request examples (Ultimate Debtor hybrid address, Creditor address, Ultimate Creditor address) to support CBPR+ and SEPA rulebook testing. |
Version 1.2.0 | April 1, 2026
This section contains updates introduced in Global Payments 1.2.0 API.
Enhanced
| Summary | Description |
|---|---|
Introduced PENDING_JPM_REVIEW payment status |
Added a new payment status to support workflows where a payment may require additional review before completion. |
Support for additionalparties in payment instruction |
Enhanced payment instructions to include additionalparties (e.g., initiating party) for better representation of multi-party payment flows. |
Changes
| Summary | Description |
|---|---|
| Updated product naming/positioning | Changed product naming/positioning to “Global Payments” and refreshed the API description for clarity. |
| Expanded data requirements for tax information | Explicitly documented required fields for relevant payment types/markets (e.g., Brazil PIX and Chile ACH). |
| Minor documentation refinements | Improved documentation across payment flows, statuses, and examples to enhance developer usability. |
Version 1.1.34 | March 31, 2026
This section contains updates introduced in Global Payments 1.1.34 API.
| Summary | Description |
|---|---|
| Added additional parties | Included a new section of fields to provide details about additional parties. |
Version 1.1.33 | May 21, 2025
This section contains updates introduced in Global Payments 1.1.33 API.
| Summary | Description |
|---|---|
| Removed all mock examples | Removed all mock examples. |
Version 1.1.32 | March 16, 2025
This section contains updates introduced in Global Payments 1.1.32 API.
| Summary | Description |
|---|---|
| Added WPI kill switch changes | Included a new response header Retry-After and a new GCA code - GCA-200 added to the 503 response for payment initiation response. |
Version 1.1.31 | January 30, 2025
This section contains updates introduced in Global Payments 1.1.31 API.
Change
What changed in Global Payments 1.1.31 API
| Summary | Description |
|---|---|
| Updated Push to Wallet payloads | Updated the payload examples for Venmo and PayPal to match production. |
Version 1.1.29 | December 20, 2024
This section contains updates introduced in Global Payments 1.1.29 API.
Change
| Summary | Description |
|---|---|
| Updated JPM Coin System to Kinexys Digital Payments | Updated the naming of JPM Coin System to Kinexys Digital Payments to reflect product rebranding. |
Version 1.1.26 | September 25, 2024
This section contains updates introduced in Global Payments 1.1.26 API.
Change
| Summary | Description |
|---|---|
| Updated sample code in mocks. | Several payment rails got mocks with updated sample code that demonstrates how to initiate payments, and get their statuses and details. |
Version 1.1.23 | June 25, 2024
This section contains updates introduced in Global Payments 1.1.23 API.
Enhanced
| Summary | Description |
|---|---|
| Added Interac e-Transfer® | Interac e-Transfer supports payments to users of the Interac network in Canada. |
| Added Push to Wallet | Push to Wallet supports payments to users of PayPal and Venmo in the United States. |
| Added Zelle® | Zelle® supports payments to users of the Zelle® network in the United States. |
| Added mocks | Interac e-Transfer, Push to Wallet, and Zelle® got mocks with sample code that demonstrates how to initiate payments, and get their statuses and details. |
Added WAREHOUSED payment status |
A WAREHOUSED payment status is part of the ENUM for future-dated transactions. A callback or GET request to the /payments/status endpoint can receive a WAREHOUSED status. |
Changes
| Summary | Description |
|---|---|
| Updated Real-Time Payments SEPA specification and ISO rule book | This enhancement provides specification updates for Real-Time Payments SEPA Zone (SEPA Instant). Specification fields that were previously disabled have now been optionally enabled. Refer to the Payment Parameters page for additional information. Additionally, SEPA Zone (SEPA Instant) examples have been added to reflect ISO rule book updates. |
| Added TCH 3.0 fields for Real-Time Payments | This enhancement provides updates that support TCH 3.0 fields for US Real-Time Payments. |
| Enhanced mock compatibility | This enhancement provides updates that support backward compatibility for mocks. |
| Enhanced payment initiation mocks | This enhancement provides a better overall experience with payment initiation mocks. |