All Systems Operational

About This Site

All PayTrace systems are being actively monitored and any issues will be reported here. If you are having trouble and don't see any updates here, please email our support team at support@paytrace.com

Transaction Processing Operational
JSON API Operational
90 days ago
100.0 % uptime
Today
Virtual Terminal Operational
90 days ago
99.98 % uptime
Today
Traditional API & Secure Checkout Operational
90 days ago
99.98 % uptime
Today
Reports - Billing | Invoicing Operational
Branded Site ? Operational
Documentation ? Operational
5-Star Support ? Operational
Processing Networks Operational
TSYS (Vital) Operational
Global Payments (GBL) Operational
First Data North (FDT) Operational
Chase Paymentech (CPT) Operational
Heartland Payments (HRT) Operational
Trident (MES) Operational
NGT TDC (NPT) ? Operational
Magensa (MAG) Operational
Payliance TransfusionBOC (CYBR) Operational
Sage Payment Solutions (EFT) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
System Metrics Month Week Day
Virtual Terminal | Traditional API | Secure Checkout Uptime
Fetching
JSON API Uptime
Fetching
Branded Site Uptime
Fetching
Past Incidents
Aug 22, 2017

No incidents reported today.

Aug 21, 2017
Resolved - Issues have not resurfaced, we will provide a post mortem once the root cause is identified.
Aug 21, 13:34 PDT
Monitoring - PayTrace is now successfully connecting to all Processing Platforms. Our Team is still monitoring the issue to figure out what caused the problem. More information will be available shortly.
Aug 21, 10:15 PDT
Identified - We are currently investigating an issue connecting to multiple processing platforms. We will provide more information when it becomes available.
Aug 21, 09:55 PDT
Aug 20, 2017

No incidents reported.

Aug 19, 2017

No incidents reported.

Aug 18, 2017
Resolved - TSYS has officially stated the negative impacts to all their endpoints are now resolved.
PayTrace is waiting for official cause of the outage from TSYS.
Aug 18, 14:22 PDT
Update - TSYS is still working on getting all endpoints stable for all processing transactions (swipe, keyed, chip, etc...).
Intermittent outages are still occurring for processing transactions.
Aug 18, 13:34 PDT
Update - TSYS is still working on getting all endpoints stable for all processing transactions (swipe, keyed, chip, etc...).
Merchants using the TSYS platform are currently still experiencing intermittent responses to all transaction requests.
Aug 18, 12:49 PDT
Monitoring - We are in contact with TSYS and waiting for their resolution.
Aug 18, 12:13 PDT
Identified - We are currently investigating an issue connecting to the TSYS processing platform.
All TSYS processing endpoints are going offline and online, we noticed errors and attempting to failover traffic as endpoint become online.
Merchants using the TSYS platform are currently experience intermittent responses to transaction requests.
We are investigating with TSYS NOC.
Aug 18, 11:37 PDT
Aug 17, 2017

No incidents reported.

Aug 16, 2017

No incidents reported.

Aug 15, 2017

No incidents reported.

Aug 14, 2017
Completed - Validated endpoint SaaS are online.
Aug 14, 15:38 PDT
Verifying - Database is now running optimal.
Aug 14, 15:33 PDT
Update - We are working on a database issue
Aug 14, 15:16 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 14, 14:30 PDT
Scheduled - On August 14th, 2017, PayTrace will be rolling out a mandated change to the User Time Out Settings, reducing the maximum allowed value from 9,999 seconds to 900 seconds (15 minutes). This change is mandated by the PCI Security Standards Council in PCI DSS Section 8.1.8. "If a session has been idle for more than 15 minutes, require the user to re-authenticate to re-activate the terminal or session."

This change will have the following impacts:

Limits the maximum value for Time Out setting in the Security Settings to 900 seconds.

Updates all PayTrace accounts that currently have a Time Out value over 900 seconds, to have the maximum value of 900 seconds.

If a user remains idle for longer than 900 seconds/15 minutes, they will be automatically logged out and be required to log back in before using PayTrace again.

We thank you for your understanding, as we make the changes necessary to comply with the PCI Security Standards Council regulations. If you have any questions regarding this upcoming change, please contact PayTrace Support.
Aug 7, 10:10 PDT
Aug 13, 2017

No incidents reported.

Aug 12, 2017

No incidents reported.

Aug 11, 2017

No incidents reported.

Aug 10, 2017
Completed - All maintenance has been implemented, monitored and verified.
Aug 10, 15:26 PDT
Update - At 1130am PDT Implemented HSTS (HTTP Strict Transport Security)
Aug 10, 11:32 PDT
Verifying - At 7:10am PDT implemented PCI TLS Cipher Maintenance changes.
Aug 10, 07:19 PDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 10, 07:00 PDT
Scheduled - On Thursday August 10th, 2017 PayTrace will be performing TLS Cipher Maintenance which will involve removal of TLS Weak/Vulnerable Ciphers per mandated PCI DSS Compliance requirement 4.1 and 6.2.

The change will have the follow impacts:

1) Strengthen the available secure communication across the public internet. PayTrace always desires to select the strongest TLS Ciphers available with a client.

2) Removal of TLS Weak/Vulnerable Ciphers.
**Low impact connection issue case** If a client only supports weak Ciphers you may experience issues connecting to PayTrace, you may need to download the security updates to acquire the stronger TLS Ciphers. This case is very limited as mainstream browsers and operating systems already support the strong TLS Ciphers.


We thank you for your understanding, as we make the changes necessary to comply with the PCI Security Standards Council regulations. If you have any questions regarding this upcoming change, please contact PayTrace Support.
Aug 8, 15:28 PDT
Aug 9, 2017

No incidents reported.

Aug 8, 2017

No incidents reported.