Skip to main content
Beta version

Welcome to the beta version of the Global Payments 2 API! For the generally available Global Payments API, refer to Global Payments.

Changelog

Global Payments 2 API

This page contains updates introduced in Global Payments 2 API.

Version 2.0.11 | November 6, 2024

This section outlines updates in Global Payments 2.0.11 API compared to Global Payments 1.1.26 API.

New

What's new in Global Payments 2.0.11 API
Summary Description
Expanded availability of ACH and Wire.

ACH credit payments are available in the following countries:

  • Brazil 
  • Canada
  • Chile
  • Single Euro Payments Area (SEPA)
  • United Kingdom
  • United States

ACH debit payments are available in the following countries:

  • Canada
  • SEPA
  • United Kingdom
  • United States (includes IAT)

Same-currency wire payments are available in the following countries:

  • Brazil
  • Canada
  • Germany
  • Switzerland
  • United Kingdom
  • United States
Reordered schema by objects. The reordered schema logically uses objects as the building blocks for making payments. This ensures that the information is expandable, context-aware, and sustainable in terms of API evolution.
Added support for Wire. Wire supports low-value and high-value payments in the same currency. 
Added idempotency key.
An idempotency key enhances duplicate checks of payments.

Change

What changed in Global Payments 2.0.11 API
Summary Description
Enhanced data capture. The API schema captures broader upstream payment information for the following:
  • Mandate information
  • Regulatory reporting
  • Settlement information

The API schema supports multi-party flows that accommodate information for the following:

  • Additional creditor
  • Additional debtor
  • Initiating party
  • Instructed agent
  • Intermediary agents
Improved granular error reporting.

The API schema supports different types of error codes to facilitate payment processing, including, but not limited to, the following:

  • J.P. Morgan proprietary Unified Codes, which are granular to the nature of the error. 
  • ISO codes, which ensure industry compatibility.
  • Clearing codes, which support Nacha codes for United States ACH transactions.

.