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
Virtual Terminal Operational
Traditional API & Secure Checkout Operational
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
EFTchecks (GETI) 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
Branded Site Uptime
Fetching
Virtual Terminal | Traditional API | Secure Checkout Uptime
Fetching
JSON API Uptime
Fetching
Past Incidents
Jan 22, 2017

No incidents reported today.

Jan 21, 2017

No incidents reported.

Jan 20, 2017

No incidents reported.

Jan 19, 2017

No incidents reported.

Jan 18, 2017

No incidents reported.

Jan 17, 2017
Completed - The scheduled maintenance has been completed.
Jan 17, 16:00 PST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 17, 14:01 PST
Update - **REMINDER**

Detailed Info

If you are currently using either TLS v1.0 or v1.1 you need to upgrade your operating system and or internet browser to a version that supports TLS v1.2.
--------------------------------------------------
PayTrace Virtual Terminal and API Integrations could be impacted by this change.
If you're a virtual terminal user and uncertain whether your operating system and/or browser supports TLS v1.2, please test it by navigating to: https://beta.paytrace.com If you're able to get to the URL without an SSL error your operating system is successfully connecting via TLS 1.2.

--------------------------------------------------
If you have an integration with a PayTrace API, please send a test API request to the endpoint URL below that corresponds with the API you are using.
JSON API - https://apibeta.paytrace.com
Traditional API - https://beta.paytrace.com/api/default.pay
Jan 11, 15:47 PST
Update - **REMINDER**

Detailed Info

If you are currently using either TLS v1.0 or v1.1 you need to upgrade your operating system to a version that supports TLS v1.2.

PayTrace Virtual Terminal and API Integrations could be impacted by this change.
If you're a virtual terminal user and uncertain whether your system supports TLS v1.2, please test it by navigating to: https://beta.paytrace.com. If you're able to get to the URL without an SSL error your operating system is successfully connecting via TLS 1.2.

If you have an integration with a PayTrace API, please send a test API request to the endpoint URL below that corresponds with the API you are using. These endpoints will not exist after 1/17/2017.
JSON API - https://apibeta.paytrace.com
Traditional API - https://beta.paytrace.com/api/default.pay
Nov 4, 09:54 PST
Update - Thanks for the feedback! We do our best to make merchants happy.
You asked and you got it. We're allowing additional time for users to make updates by extending the timeline for disabling TLS v1.0 & TLS v1.1 from June 15th, 2016 to January 17th, 2017 at 8:00-10:00 PDT.

If you are currently using either TLS v1.0 or v1.1 you need to upgrade your operating system to a version that supports TLS v1.2.
PayTrace Virtual Terminal and API Integrations could be impacted by this change.

If you're a virtual terminal user and uncertain whether your system supports TLS v1.2, please test it by navigating to: https://beta.paytrace.com. If you're able to get to the URL without an SSL error your operating system is successfully connecting via TLS 1.2.

If you have an integration with a PayTrace API, please test it by sending your API request to https://beta.paytrace.com/api/default.pay
Jun 1, 11:50 PST
Update - In order to allow additional time for users to make necessary updates, we’re extending the timeline for disabling TLS v1.0 & TLS v1.1 to June 15th. It’s necessary for PayTrace to disable TLS v1.0 & TLS v1.1 in order to stay in-line with processing networks & PCI requirements for TLS v1.2 only connections. Therefore, we won’t be able to delay this timeline further.

Connections to the Virtual Terminal and API by Merchants, Resellers & Integrators may be affected by this change.

If you’re uncertain whether your system supports TLS v1.2, please test it by navigating to: https://beta.paytrace.com. If you’re able to get to the URL without an SSL error your operating system is successfully connecting via TLS 1.2.
Apr 5, 16:42 PST
Update - You may now test TLS 1.2 on your computer and/or server by going to: https://beta.paytrace.com If you are able to get to the URL without an SSL Error your Operating System is successfully connecting via TLS 1.2
Dec 21, 12:05 PST
Update - Due to environment and SSL constraints, TLS v1.0 & TLS v1.1 will both be combined in the maintenance window on April 15th, 2016.
Dec 2, 11:32 PST
Scheduled - Due to PCI requirements PayTrace is discontinuing service to TLS v1.1 users. If you are currently using TLS v1.1 you need to upgrade your operating system to a version that supports TLS v1.2.
TLS v1.1 will no longer be in service on April 15th, 2016.
Oct 12, 10:25 PST
Jan 16, 2017

No incidents reported.

Jan 15, 2017

No incidents reported.

Jan 14, 2017

No incidents reported.

Jan 13, 2017

No incidents reported.

Jan 12, 2017

No incidents reported.

Jan 11, 2017
Resolved - This incident has been resolved.
Jan 11, 16:42 PST
Monitoring - A few SecureCheckout clients encountered an error. We have isolated the issue, we made adjustments & we will continue to monitor the service.
Jan 11, 12:26 PST
Jan 10, 2017

No incidents reported.

Jan 9, 2017

No incidents reported.

Jan 8, 2017

No incidents reported.