Identified - New incident: Identified

We are actively researching why some Canadian merchants are receiving incorrect bank transfer descriptors. Please note this is is only affecting
how the deposits are being displayed on the statements. The correct amounts are still being routed to the correct banking information on file. We have recently started transitioning our mechanism for Canadian transfers and we believe this is related. We will continue to investigate the root cause and solution to this issue.
Nov 26, 13:17 MST
Monitoring - Any ProPay partners using AnywhereCommerce-supplied CX Bluetooth readers manufactured by BBPOS will need to apply a firmware update to these devices before January 1st, 2022. Without the firmware update, the readers will cease to function for processing at the end of the year. You may review this knowledge base article for more details:
https://support.propay.com/a/solutions/articles/33000268568?portalId=33000065776
Nov 15, 13:49 MST
Identified - Beginning in October, Visa began sending more specific response codes for some types of declines, replacing the generic 05 ("do not honor") code. The ProtectPay system failed to properly cover these new decline codes, resulting in some processing attempts now returning status 207 responses ("Gateway Internal system error") instead of the proper updated decline codes. In these declines, the API response of such transactions attempts include ResultMessage "Gateway Internal System Error (account setup improperly)".

We will correct this problem in the 2021.12.1 release on December 7th.

The following codes are new:

46 -- Closed account.
59 -- Suspected fraud.
82 -- Negative online CAM, dCVV, iCVV, or CVV results, or Offline PIN authorization interrupted (Note: previously, ProPay mapped this to 99 ("generic decline (international merchants)").
143 -- Customer data failed (corresponds to "6P" from Visa)

We will update the ProtectPay-API-Appendix-A-Responses document (section 2.4, "Status Codes Returned by Payment Method Issuer") to include these new codes. Reference link: https://www.propay.com/en-US/Documents/API-Docs/ProtectPay-API-Appendix-A-Responses

For partner systems that treat all ProtectPay responses with Transaction.ResultCode.ResultCode other than 00 (success) as issuer declines/rejections, it may be unnecessary to make any adjustments, but we recommend confirming that with your development teams.

Sample ProtectPay response JSON for this type of decline:
"Transaction":{"AVSCode":"T","AuthorizationCode":"","CurrencyConversionRate":1.0,"CurrencyConvertedAmount":46,"CurrencyConvertedCurrencyCode":"USD","ResultCode":{"ResultValue":"FAILURE","ResultCode":"46","ResultMessage":"Closed Account"},"TransactionHistoryId":"987654","TransactionId":"1","TransactionResult":"Declined","CVVResponseCode":"NotPresent","GrossAmt":null,"NetAmt":null,"PerTransFee":null,"Rate":null,"GrossAmtLessNetAmt":null},"RequestResult":{"ResultValue":"FAILURE","ResultCode":"46","ResultMessage":"Closed Account"}}]}
Nov 4, 12:24 MDT

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
Phones ? 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
Past Incidents
Nov 29, 2021

No incidents reported today.

Nov 28, 2021

No incidents reported.

Nov 27, 2021

No incidents reported.

Nov 26, 2021
Resolved - This incident has been resolved.
Nov 26, 11:53 MST
Monitoring - We are aware of an issue that is preventing some transactions from being processed.

Our teams were able to identify an unhealthy application node. They were able to quickly address the problem by removing this problem node from the pool. We do not anticipate any more related problems, but will continue to monitor the situation before resolving this incident.

clientsupport@propay.com
801-341-5312
Nov 26, 10:35 MST
Nov 25, 2021

No incidents reported.

Nov 24, 2021

No incidents reported.

Nov 23, 2021

No incidents reported.

Nov 22, 2021

No incidents reported.

Nov 21, 2021

No incidents reported.

Nov 20, 2021

No incidents reported.

Nov 19, 2021

No incidents reported.

Nov 18, 2021

No incidents reported.

Nov 17, 2021

No incidents reported.

Nov 16, 2021
Completed - The scheduled maintenance has been completed.
Nov 16, 05:02 MST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 16, 00:00 MST
Scheduled - ProPay will perform platform maintenance overnight (tonight/tomorrow, Tuesday, November 16th, between 00:00 and 05:00 Mountain Time), upgrading to version 21.10.1.2 on the live production system.

*** We anticipate no interruption in service during this update. ***

This release only applies to future internal GPN integrations, and should have no impact to existing partners.
Nov 15, 13:28 MST
Nov 15, 2021

Unresolved incident: REQUIRED: AnywhereCommerce BBPOS Walker card readers need a firmware update by end of 2021.