All Systems Operational

Updated a few seconds ago

REPAY Gateway API




Operational

REPAY Gateway Admin




Operational

REPAY ACH Backend (RAB) Processing




Operational

REPAY ACH Backend (RAB) Portal




Operational

EBPP




Operational

Hosted Payment Page




Operational

IVR




Operational

Email System




Operational

Data Extract Service




Operational

Lift (Ventanex)




Operational

TSYS Production




Operational

TSYS Certification




Operational

REPAY Payables Platform




Operational

Webhooks




Operational

REPAY ClickToPay




Operational

Payrazr/PayrazRx/Careview v4




Operational

Careview/XprsPay (Versions 1-3)




Operational

Stratus




Operational

REPAY Gateway API

100.00%




REPAY Gateway Admin

100.00%




REPAY EBPP/HPP

100.00%




REPAY Gateway API

100.00%




REPAY Gateway Admin

100.00%




REPAY EBPP/HPP

100.00%




REPAY Gateway API

100.00%




REPAY Gateway Admin

100.00%




REPAY EBPP/HPP

100.00%




Scheduled Maintenance

Schedule

June 28, 2023 9:00AM - 2:00PM EDT
June 28, 2023 1:00PM - 6:00PM UTC

Components

EBPP, Hosted Payment Page

Locations

AWS (Oregon)

Description

Dear Valued Customer, You are receiving this notification because your business uses one or more REPAY solutions which are hosted in Amazon Web Services (AWS). Effective June, 28, 2023, AWS is updating the TLS configuration for all AWS API endpoints and therefore sunsetting versions TLS 1.0 and TLS 1.1. Your action is required to ensure your environment supports this change. Who does this update impact? REPAY's solution already requires TLS 1.2 for our core payment application. But if your system accesses public assets we host (e.g., your logo), your application would need to use TLS 1.2 no later than the effective date. Why is AWS updating their TLS 1.0 and 1.1 configuration? AWS is updating their TLS configuration for all AWS API endpoints so that customers can benefit from the enhanced security provided by modern TLS encryption protocols. How will REPAY handle the TLS update? REPAY will be conducting a series of tests in the sandbox environment before introducing the change into production. You will receive a notification prior to these tests being conducted and should use the testing opportunity to ensure your system communicates properly with the change. REPAY will permanently disable TLS Versions 1.0 and 1.1 in production by June, 28, 2023 to comply with the AWS change.
Payrazr Network MaintenancePlanned Maintenance

Schedule

December 2, 2023 6:00PM - 11:59PM EST
December 2, 2023 11:00PM - 4:59AM UTC

Components

Payrazr/PayrazRx/Careview v4

Locations

Production, Payment Gateway

Description

REPAY’s IT team makes continuous improvements to security and performance of the Payrazr environment. We want to make you aware of the following activity: On Saturday, December 2, 2023, from 6:00pm until midnight EST, network maintenance will be performed. No outage is expected. However, there may be intermittent interruptions as services are configured.

Schedule

December 9, 2023 5:00PM - 8:00PM EST
December 9, 2023 10:00PM - 1:00AM UTC

Components

Payrazr/PayrazRx/Careview v4, Careview/XprsPay (Versions 1-3)

Locations

Production, Payment Gateway

Description

REPAY’s IT team makes continuous improvements to security and performance of the Careview and Payrazr environments. We want to make you aware of the following activity: On Saturday, December 9, 2023, beginning at 5:00pm EST and lasting up to three hours, the technology team will be upgrading part of our payment gateway. Clients whose payments are processed through Worldpay should expect an outage during this window. For questions, please contact customerservice@repay.com.

Schedule

December 11, 2023 9:00PM - 11:00PM EST
December 12, 2023 2:00AM - 4:00AM UTC

Components

EBPP, Hosted Payment Page, IVR, Email System, REPAY ClickToPay

Locations

AWS (Oregon), Production

Description

On Monday, December 11th, beginning at 9:00pm EDT and lasting approximately 2 hours, the Channels technology team will perform Production Database maintenance. The team expects approximately 30 minutes of downtime in addition to intermittent degraded performance within this window.

0

Days Until Next Maintenance

35

Days Since Last Incident

4

Upcoming Maintenances