All Systems Operational

About This Site

ProPay's home for current solution status, incidents, planned maintenance and solution release events.

Regular Maintenance Windows (Mountain Time)
──────────────────────────────
Database: Every 2nd to last Thursday of the month, 03:00-3:30 (am)
Infrastructure: Every Thursday, 01:00-3:00 (am)
xfer.propay.com: last Thursday of each month, 13:00-15:00
TEST environment: Every Tuesday, 15:00-17:00

Production Processing Solutions Operational
Direct Credit Card and ACH Processing Operational
Websites, Mobile, and Card Readers Operational
Payment Facilitation - Heartland, Portico Operational
Payment Facilitation - Global Payments API (GP API) Operational
Payment Facilitation - Cayan Genius Operational
Production Supporting Solutions Operational
xfer.propay.com - SFTP Reports Operational
Bank Transfers Operational
Phones Operational
Regulatory Updates Operational
Testing Environments Operational
Integration TEST Environment Operational
Integrated Gateways Operational
3rd Party Providers Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

ProPay September 2026 Database Maintenance Reminder Sep 17, 2026 03:00-03:05 MDT

At 3:00 a.m. (MT) on Thursday, September 17th, the database system will undergo its monthly maintenance. We anticipate no more than 5 minutes of service interruption during this time frame.
Posted on Sep 03, 2026 - 13:24 MDT

ACH Authorization Compliance Reminder Oct 1, 2026 00:00-00:15 MDT

Global Payments Inc. has been asked to remind all partners and their sub-merchants that NACHA rules require obtaining authorization to originate ACH entries on customer’s bank account and to retain that authorization for a period of at least 2 years.

We have been provided a breakdown to remind merchants of their requirements and the potential fines that may be assessed should they be found not to be compliant.

That document can be found here:

https://support.propay.com/en/support/solutions/articles/33000315573-ach-authorization-reminder
Posted on Jul 10, 2026 - 08:01 MDT

Propay October 2026 Card Brand Regulatory Notice - Reminder Oct 1, 2026 00:00-00:05 MDT

As a reminder, Global Payments Inc. has received notification of changes to the operating regulations effective October 2026 by Visa®, Mastercard®, Discover® Network and American Express®. Global Payments Inc. has reviewed and analyzed the changes and is providing documentation.

Our proprietary systems will be updated and certified by the required release dates. These updates may require changes to your authorization and/or settlement systems and your internal business processes and procedures. Regulatory items listed below may not apply to all business types.

You can review the regulatory notice document here:

https://support.propay.com/en/support/solutions/articles/33000315754-october-2026-card-brand-regulatory-update
Posted on Jul 31, 2026 - 12:42 MDT

Sep 5, 2026

No incidents reported today.

Sep 4, 2026

AMEX Processing and AMEX Account Requirements Update
Resolved - This incident has been resolved.
Sep 4, 08:15 MDT
Update - We will be reaching out to the impacted accounts directly and if they need additional information to reach out to their account contacts.
Jun 25, 07:07 MDT
Update - Quick Update: We have rebuilt the file that goes out to AMEX on a daily basis. We are hoping that the file is accepted tonight, so any account that has been recently updated and contains all of the required AMEX fields will board as expected on the Amex side. We will keep you updated and we apologize for the inconvenience.
Jun 24, 14:37 MDT
Update - Quick Update: We have no further updates at this time to share with you. Remediation is underway and next steps will be communicated further from our SPM team.
Jun 24, 10:55 MDT
Update - Quick Update: We are waiting for an update from Amex. They opened a case with their development team. We will update you as soon as we hear back.
Jun 23, 15:31 MDT
Update - “Our next update will be shared no later than 6:00 PM CT. We will communicate sooner if any new developments arise.”
Jun 23, 10:02 MDT
Update - Quick Update: "We are seeing continued declines with American Express and continue to work with AMEX on remediation. We will update this status page as we have more information."
Jun 23, 09:36 MDT
Update - Update: The fix has been implemented now, and we are continuing to monitor the situation with this update.

Our Strategic Partner Management team will be reaching out to partners to ensure that their accounts are being updated with correct data as well, to ensure that all accounts are compliant with AMEX's requirements.

Ongoing review of impacted accounts and remediation is underway and next steps will be communicated further from our SPM team.
Jun 18, 14:54 MDT
Update - The ProPay Development Team has been working with AMEX and has identified the errors which have been preventing accounts from boarding on the AMEX side.

A fix is being implemented today to address and correct this.

Our Strategic Partner Management team will be reaching out to partners to ensure that their accounts are being updated with correct data as well, to ensure that all accounts are compliant with AMEX's requirements.

Ongoing review of impacted accounts and remediation is underway and next steps will be communicated further from our SPM team.
Jun 18, 12:48 MDT
Update - Update: We are working closely with AMEX and our Development team is investigating why the accounts are not boarding on the AMEX side. That is the reason why the AMEX transactions are declining. This issue is due to new logic that rolled out on the AMEX side. We will keep you updated and we apologize for the inconvenience.
Jun 17, 13:52 MDT
Update - Update: We are working closely with AMEX and our Development team is investigating why the accounts are not boarding on the AMEX side. That is the reason why the AMEX transactions are declining. This issue is due to new logic that rolled out on the AMEX side. We will keep you updated and we apologize for the inconvenience.
Jun 17, 13:51 MDT
Monitoring - Effective May 28th, AMEX made some changes to required data that they need to receive from the processor for compliance reasons:

*Requirement: American Express requires that any merchant processing American Express transactions must be boarding at American Express.

Before changes made on May 28 AMEX allowed merchants transactions to process without registration.

*After Changes: New merchants: American Express will allow transactions to process for 10 days, after the 10 days merchants will start receiving declines on transactions.

Existing merchants: Any merchant that did not get boarded with American Express will start receiving declines on transactions.

AMEX current issues:

Compliance was working on a project to identify accounts who processed AMEX transactions that did not meet the new AMEX data requirements.

In essence, we made changes to accounts and inadvertently changed the data on incorrect accounts by accident, in an effort to get the accounts in compliance for AMEX. The data has since been corrected.

Below fields need to be added via TT 42, for any account that is not able to process AMEX transactions:

Required AMEX fields:

Account ID
Business Legal Name
Doing Business As (DBA) Name
Business Address
Business email address (cannot contain any special characters, except for "@")
Business City
Region
Business Postal Code
Business Country Code
Currency Code
Merchant Category Code (MCC)
Authorized Signer First Name
Authorized Signer Last Name
Authorized Signer Country Code
business Phone number
Fed TAX ID or SS#

Any account that does not meet these new requirements, will see that their processing has been disabled by AMEX.
Jun 16, 10:36 MDT

Sep 3, 2026

No incidents reported.

Sep 2, 2026

No incidents reported.

Sep 1, 2026

No incidents reported.

Aug 31, 2026

No incidents reported.

Aug 30, 2026

No incidents reported.

Aug 29, 2026

No incidents reported.

Aug 28, 2026

No incidents reported.

Aug 27, 2026

ProPay Production Environment Scheduled Release Update 26.PI18.R2 (August Release)
Completed - The scheduled maintenance has been completed.
Aug 27, 05:00 MDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 27, 00:00 MDT
Scheduled - On Thursday, August 27th, between 00:00 and 05:00 (MT), ProPay will perform an upgrade to the production environment 26.PI18.R2 (August Release)

*** All services and sites may be unavailable during this time frame. ***

* We have enhanced the chargeback management experience by increasing the supported character length for chargeback reason code descriptions. This ensures that the chargeback reason code descriptions are stored in full without truncation to make it easier to clearly parse the reason for the chargeback.

* We have modernized the chargeback action experience within the Merchant Portal and Partner Portal to improve usability, maintainability, and overall user experience in managing chargebacks

*We have improved the reliability and accuracy of the Transaction Type 07 Void/Refund API call by applying correct default handling for the voidOnly parameter and returning precise failure response codes for non-US currency (multi-currency) refund transactions.

*We have enhanced the Comprehensive Transaction Detail Report (CTDR) to pull data for up to 10 Days: this extends the CTDR beyond the current fixed 7-day rolling window by introducing a configurable Rolling Days parameter (for example, 10 days) to improve accuracy.

This addresses cases where transaction lifecycle events such as authorization to capture occur after Day 7, improving end-to-end transaction visibility and reconciliation accuracy.

*We have made adjustments to the allowed characters and values that can be passed in the Authorized Signer First and Last Name fields.

Allowed Characters/Values:

-Letters (A-Z, a-z)
-Accented characters / international letters (e.g., é, ü, ñ, ø, ł)
-Spaces
-Hyphens (-)
-Apostrophes (')

Not Allowed
-Periods (.)
-Numbers
-Asterisks (*)
-Other special symbols
-Emojis
-Any character outside the approved character set

Minimum Length

-Authorized Signer First Name: Minimum 2 characters
-Authorized Signer Last Name: Minimum 2 characters

Restricted Placeholder Values

-Name
-Owner
-Manager
-First
-Authorized

These limits apply to any updates made or values passed in any of the following methods:

-XML API (TT01 & TT42)
-REST API
-ePay Website
-Merchant Portal
-Partner Portal

This validation can be toggled off/on at the partner level if requested.

*We have made adjustments to the allowed characters and values that can be passed in the seller DBA and seller city fields.

Allowed Characters/Values:

Seller DBA Name
-Asterisk (*) is not allowed.

Seller City
-Numeric characters (0-9) are not allowed.

These limits apply to any updates made or values passed in any of the following methods:

-XML API (TT01 & TT42)
-REST API
-ePay Website
-Merchant Portal
-Partner Portal

This validation can be toggled off/on at the partner level if requested.
Aug 21, 11:20 MDT

Aug 26, 2026

No incidents reported.

Aug 25, 2026

No incidents reported.

Aug 24, 2026

No incidents reported.

Aug 23, 2026

No incidents reported.

Aug 22, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage