All Systems Operational
About This Site
ProPay's home for current solution status, incidents, planned maintenance and solution release events.
ProPay regularly conducts maintenance at the following times:
Database: 3rd Thursday of the month between 3-3:30am MT
Infrastructure: Thursdays between 1am-3am Mountain Time.
xfer.propay.com: Last Thursday of each month between 1pm-3pm MT. This may include brief disconnects.
TEST environment patching: 1am-3am MT, typically on the 3rd or 4th Thursday.
TEST environment releases: 1600-1700MT, Tuesdays and Fridays.
Production Processing Solutions
Operational
Credit Card and ACH Processing
Operational
Websites, Mobile, and Card Readers
Operational
Production Supporting Solutions
Operational
xfer.propay.com - SFTP Reports
Operational
Batch File Processing & Commissions
Operational
Bank Transfers
Operational
Testing Environments
Operational
Integration TEST Environment
Operational
Sandbox Test Environment - Future Releases
Operational
Integrated Gateways
Operational
Chase Paymentech - Orbital Gateway
Operational
Network Merchants
Operational
Web Collect
Operational
Meritus
Operational
CyberSource
Operational
Other 3rd Party Gateways
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
ProPay Monthly DB Maintenance moved in August to 13th
Aug 13, 03:00-03:30 MDT
On 8/13 between 3:00-3:30am MT, ProPay will perform database maintenance requiring up to 15 min of downtime.
For the month of August, this replaces the normally-scheduled date of 8/20.
The date is being moved to give teams more time to implement, test and confirm the introduction of Availability Groups in September to enhance our high availability infrastructure.
Posted on Jul 22, 17:47 MDT
For the month of August, this replaces the normally-scheduled date of 8/20.
The date is being moved to give teams more time to implement, test and confirm the introduction of Availability Groups in September to enhance our high availability infrastructure.
Posted on Jul 22, 17:47 MDT
ProPay Production Environment Scheduled Update 20.08
Aug 18, 08:00-17:00 MDT
On Tuesday, August 18th, between 08:00 and 17:00 (MDT), ProPay will perform platform maintenance, upgrading to version 20.08 on the live production systems. We do not anticipate any interruption in service during this update.
NOTICE OF IMPORTANT CHANGES:
* As of Aug 1, 2020, ProPay discontinued merchant service offerings for Australia and New Zealand.
* On Oct 1, 2020, ProPay will decommission version 1 of the Hosted Payment Page (HPP).
-- For more details, see this page: https://status.propay.com/incidents/p68q5lmqc3fp
The 20.08 release includes the following change:
* The development work for this update focuses on internal improvements and groundwork for upcoming releases, with no changes to existing functionality.
For questions, you may contact Client Support (clientsupport@propay.com | 801-341-5312).
Posted on Aug 11, 16:46 MDT
NOTICE OF IMPORTANT CHANGES:
* As of Aug 1, 2020, ProPay discontinued merchant service offerings for Australia and New Zealand.
* On Oct 1, 2020, ProPay will decommission version 1 of the Hosted Payment Page (HPP).
-- For more details, see this page: https://status.propay.com/incidents/p68q5lmqc3fp
The 20.08 release includes the following change:
* The development work for this update focuses on internal improvements and groundwork for upcoming releases, with no changes to existing functionality.
For questions, you may contact Client Support (clientsupport@propay.com | 801-341-5312).
Posted on Aug 11, 16:46 MDT
ProPay Partner Integration (Test) Environment Scheduled Update 20.08
Aug 18, 15:00-17:00 MDT
On Tuesday, August 18th, between 15:00 and 17:00 (MDT), ProPay will perform an update on the partner integration test environment. All services and sites may be unavailable during this time frame.
NOTICE:
* As of Aug 1, 2020, ProPay discontinued merchant service offerings for Australia and New Zealand.
The 20.08 release includes the following changes:
* The development work for this update focuses on internal improvements and groundwork for upcoming releases, with no changes to existing functionality.
For questions, you may contact Client Support (clientsupport@propay.com | 801-341-5312).
Posted on Aug 11, 16:41 MDT
NOTICE:
* As of Aug 1, 2020, ProPay discontinued merchant service offerings for Australia and New Zealand.
The 20.08 release includes the following changes:
* The development work for this update focuses on internal improvements and groundwork for upcoming releases, with no changes to existing functionality.
For questions, you may contact Client Support (clientsupport@propay.com | 801-341-5312).
Posted on Aug 11, 16:41 MDT
Decommissioning Hosted Payment Page Version 1, Oct 1, 2020
Oct 1, 10:00-17:00 MDT
This maintenance only impacts integrations using the ProtectPay Hosted Payments Page V1.
Direct Communication has been sent to merchants and partners using this solution to inform them of the action required.
In order to provide optimal service and products, ProPay will discontinue the ProtectPay Hosted Payments Page v1 on 1 October 2020.
To avoid interruption in processing services, those partners using V1 (SignalR) should upgrade and migrate to the ProtectPay Hosted Payment Page v2 solution (released in 2018) prior to October 1, 2020. This can be done with some minor changes, described below.
The Hosted Payments Page (HPP) is a frame-able Payer Management Interface that allows merchants to collect, tokenize and process consumer payment information without having the sensitive data traverse their systems, thereby reducing PCI compliance burdens.
Actions required to convert:
1. The URL for the Hosted Payment Page should be updated
from
https://protectpay.propay.com/hpp/home/[HostedTransactionID]
to
https://protectpay.propay.com/hpp/v2/[HostedTransactionID]
2. The V2 page has its own submit button. Integrators should remove the submit button on the webpages that leverage the HPP.
3. Because the submit button is now on the hosted page, V2 requires that a “ReturnURL” is specified in the API request to create the HostedTransactionIdentifer (10.2 in the referenced manuals). ProPay’s system uses this to redirect the payer’s browser to a page specified in the Hosted Transaction Identifier so the client system can retrieve the results of the event and display them to the payer.
Links to Developer Resources, including TEST URLs:
Hosted Payment Page Processing Introduction
https://www.propay.com/en-US/Developer/processing-cc-protectpay-hpp
Hosted Payment Page V2 Manual
https://www.propay.com/en-US/Documents/API-Docs/ProtectPay-PMI-Hosted-Payment-Page-Manual
ProtectPay REST API Manual
https://www.propay.com/en-US/Documents/API-Docs/ProtectPay-API-Manual-REST
ProtectPay SOAP API Manual
https://www.propay.com/en-US/Documents/API-Docs/ProtectPay-API-Manual-SOAP
Please contact clientsupport@propay.com, or your relationship manager with any questions or assistance with making the conversion.
Posted on Jun 9, 16:50 MDT
Direct Communication has been sent to merchants and partners using this solution to inform them of the action required.
In order to provide optimal service and products, ProPay will discontinue the ProtectPay Hosted Payments Page v1 on 1 October 2020.
To avoid interruption in processing services, those partners using V1 (SignalR) should upgrade and migrate to the ProtectPay Hosted Payment Page v2 solution (released in 2018) prior to October 1, 2020. This can be done with some minor changes, described below.
The Hosted Payments Page (HPP) is a frame-able Payer Management Interface that allows merchants to collect, tokenize and process consumer payment information without having the sensitive data traverse their systems, thereby reducing PCI compliance burdens.
Actions required to convert:
1. The URL for the Hosted Payment Page should be updated
from
https://protectpay.propay.com/hpp/home/[HostedTransactionID]
to
https://protectpay.propay.com/hpp/v2/[HostedTransactionID]
2. The V2 page has its own submit button. Integrators should remove the submit button on the webpages that leverage the HPP.
3. Because the submit button is now on the hosted page, V2 requires that a “ReturnURL” is specified in the API request to create the HostedTransactionIdentifer (10.2 in the referenced manuals). ProPay’s system uses this to redirect the payer’s browser to a page specified in the Hosted Transaction Identifier so the client system can retrieve the results of the event and display them to the payer.
Links to Developer Resources, including TEST URLs:
Hosted Payment Page Processing Introduction
https://www.propay.com/en-US/Developer/processing-cc-protectpay-hpp
Hosted Payment Page V2 Manual
https://www.propay.com/en-US/Documents/API-Docs/ProtectPay-PMI-Hosted-Payment-Page-Manual
ProtectPay REST API Manual
https://www.propay.com/en-US/Documents/API-Docs/ProtectPay-API-Manual-REST
ProtectPay SOAP API Manual
https://www.propay.com/en-US/Documents/API-Docs/ProtectPay-API-Manual-SOAP
Please contact clientsupport@propay.com, or your relationship manager with any questions or assistance with making the conversion.
Posted on Jun 9, 16:50 MDT