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, 2026 - 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, 2026 - 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, 2026 - 10:36 MDT

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

Planned Maintenance – Security Credential Refresh Jun 25, 2026 00:00-05:00 MDT

We are completing a planned security credential refresh for several partner-facing services. This maintenance helps keep our systems secure and does not require any action from business users or partners.

What This Means For You:

*No action is required

*Users can continue accessing the portal and related services as usual

*There are no expected changes to business workflows, integrations, or transaction processing

Expected Experience:

Services are expected to remain available, including portal access, onboarding, risk checks, device setup, notifications, tax processing, and transaction-related workflows

We will continue to monitor services during the maintenance window. If you notice an unexpected sign-in or authentication issue, please contact support through the normal channels and include the time of the issue and any available reference or correlation ID.

Posted on Jun 18, 2026 - 09:31 MDT

Notice: Upcoming Changes to Stored PAN TEST Data in Propay Partner Integration Environment (part 2) Jun 25, 2026 15:00-16:00 MDT

On Thursday, June 25th, we will be implementing the first phase to address a security issue in the Partner Integration (PI) test environment.

We will be updating test PAN data stored in the PI environment to ensure that no real PAN data can be present.

To enhance security, only the first six and last four digits of card data will remain the same in the partner environment.

All intervening digits will be replaced with the number one and the test PAN data will be re-encrypted at rest.

Posted on Jun 16, 2026 - 10:54 MDT

Important Update Regarding Downgraded Transaction Fees Jul 1, 2026 00:00-00:05 MDT

This update is to inform our partners of an upcoming change to our billing process related to downgraded payment transactions.

Global Payments recently identified that Downgraded Transaction Fees assessed by Visa, Mastercard, and Discover were not being passed through to partners. We have made the necessary updates to our billing system to ensure accurate and consistent handling of these fees going forward.

Beginning with the July 2026 monthly invoice, Downgraded Transaction Fees will be included and passed through accordingly.

What you need to know:

*These fees are strictly pass‑through charges from the card networks and do not include any markup from Global Payments.

*Contractually, network and processing‑related fees are the responsibility of the partner or merchant.

*No other pricing changes will occur as part of this update.

To support transparency, we will also be providing a new Downgrade Report with your July invoice, which will include detailed information to help you understand the transactions and fees associated with downgrades. The initial release of the report will contain the reason code returned by the networks. In a subsequent release, we will introduce a more detailed description associated with each code.

We truly value your partnership and appreciate your continued business. Should you have any questions or would like additional information regarding downgraded transactions or the new reporting, please contact your Global Payments SPM or our support team at clientsupport@propay.com.

Thank you for your continued trust and partnership.

Posted on Jun 05, 2026 - 10:05 MDT
Jun 18, 2026
Completed - The scheduled maintenance has been completed.
Jun 18, 03:05 MDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 18, 03:00 MDT
Scheduled - At 3:00 a.m. (MT) on Thursday, June 18th, the database system will undergo its monthly maintenance. We anticipate no more than 5 minutes of service interruption during this time frame.
Jun 16, 07:28 MDT
Jun 17, 2026
Jun 16, 2026
Completed - The scheduled maintenance has been completed.
Jun 16, 05:00 MDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 16, 00:00 MDT
Scheduled - On Tuesday, June 16th, between 00:00 and 05:00 (MT), ProPay will perform an upgrade to the production environment 26.PI17.R3 (June Release)

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

*New Retry KYC API Call has been added to the ProPay XML API. The intent of this call is to provide an improved systemic process to allow a ProPay merchant to be successfully onboarded even after first KYC failure.

Documentation will be available here: https://epay.propay.com/ProPayDocumentation/?fileTag=ProPay-API-Manual-XML

The documentation clearly explains the purpose and usage of the Retry KYC transaction and provides detailed definitions for all request elements, including account number, signer information, beneficial owner details, and business data along with their nested address structures.

It also outlines the response structure, including conditions under which different KYC response codes such as success or denial are returned, and describes the behavior of ActionCode for various entities involved in the KYC process.

Additionally, the documentation includes sample XML requests and responses for both successful and failed scenarios, ensuring consistency with existing API documentation standards and making it easier for partner developers to correctly implement and troubleshoot integrations.

*The ProPay Partner Portal has been updated to accurately reflect real-time chargeback status when viewing chargebacks and the Chargeback Report, and when using the “Take Action” option to accept or reject a chargeback

*Updates have been made to the epay.propay.com website to consolidate links and remove non-functional links, to improve customer experience

Jun 11, 12:39 MDT
Jun 15, 2026

No incidents reported.

Jun 14, 2026

No incidents reported.

Jun 13, 2026

No incidents reported.

Jun 12, 2026
Resolved - This incident has been resolved.
Jun 12, 19:39 MDT
Investigating - We are aware of an issue causing some account names to display incorrectly. Our teams working to identify and resolve the issue as quickly as possible.
Jun 12, 14:55 MDT
Jun 11, 2026

No incidents reported.

Jun 10, 2026

No incidents reported.

Jun 9, 2026

No incidents reported.

Jun 8, 2026

No incidents reported.

Jun 7, 2026

No incidents reported.

Jun 6, 2026

No incidents reported.

Jun 5, 2026

No incidents reported.

Jun 4, 2026

No incidents reported.