Payworks Status

All Systems Operational

Uptime over the past 90 days. View historical uptime.

Payworks Live Platform Operational

90 days ago

100.0 % uptime

Today

API Operational

Gateway Manager Operational

Transaction Processing Operational

Webhook Service Operational

90 days ago

100.0 % uptime

Today

Connectors Operational

Alipay Operational

Cybersource Operational

Stripe Operational

SIX DCC Operational

Fexco DCC Operational

Concardis Operational

AMEX (via ACI) Operational

Barclaycard APACS (via ACI) Operational

Barclaycard HISO (via ACI) Operational

Barclaycard HISO Operational

Concardis (via ACI) Operational

CREDORAX (via ACI) Operational

Ecentric Operational

Elavon (via ACI) Operational

Evry (via ACI) Operational

First Data Merchant Services (via ACI) Operational

First Data Rapid Connect (via ACI) Operational

Mercantile (via ACI) Operational

Privatbank (via ACI) Operational

SIX (via ACI) Operational

Stripe (via ACI) Operational

TSYS (via ACI) Operational

Zenith Bank (via ACI) Operational

Global Payments (via Omnipay) Operational

UCP (via GlobalPayments) Operational

Payworks Test Platform Operational

API Operational

Gateway Manager Operational

Transaction Processing Operational

Incident Notification Dry Runs Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

TLS 1.2 maintenance window Jul 12, 09:00-10:00 CEST

Payworks is constantly improving the security of the platform.

As part of this effort, we will enforce TLS 1.2 communication by the 12th of July (7-8am UTC) from server side.
No impact on clients is expected as our analysis showed that all client are already using TLS 1.2 for communication even though TLS 1.1 is still supported by the server.
We have enforced the TLS 1.2 protocol on our test environment already. The test environment can be used to perform some client side regression testing if needed.

The following set of ciphers will be supported to establish a HTTPS connection:

ECDHE-RSA-AES128-GCM-SHA256
ECDHE-RSA-AES128-SHA256
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-RSA-AES256-SHA384
AES128-GCM-SHA256
AES256-GCM-SHA384
AES128-SHA256
Posted on Jun 29, 11:58 CEST

Past Incidents

Jul 8, 2020

No incidents reported today.

Jul 7, 2020

No incidents reported.

Jul 6, 2020

No incidents reported.

Jul 5, 2020

No incidents reported.

Jul 4, 2020

No incidents reported.

Jul 3, 2020

No incidents reported.

Jul 2, 2020

Processing DCC through Fexco disrupted

Resolved - This incident has been resolved.
Jul 2, 14:53 CEST

Update - The issue seems to be fixed. We will continue to monitor the situation.
Jul 2, 14:43 CEST

Update - We monitor the situation
Jul 2, 14:35 CEST

Update - We contacted Fexco and continue to monitor the issue
Jul 2, 14:13 CEST

Update - We saw health endpoint as unavailable, but currently we cannot see any affected transactions. We continue to monitor the situation.
Jul 2, 14:07 CEST

Investigating - We are investigating connectivity issues with Fexco
Jul 2, 13:54 CEST

Jul 1, 2020

No incidents reported.

Jun 30, 2020

Transaction being disrupted

Resolved - This incident has been resolved.
Jun 30, 12:47 CEST

Update - We are continuing to monitor for any further issues.
Jun 30, 12:33 CEST

Update - We are continuing to monitor for any further issues.
Jun 30, 12:32 CEST

Monitoring - The situation seems to be stable now and we are monitoring the transactions
Jun 30, 12:26 CEST

Update - We are continuing to investigate this issue.
Jun 30, 12:25 CEST

Investigating - HSM transaction processing being disrupted. We are monitoring the issue intensively
Jun 30, 12:20 CEST

Jun 29, 2020

No incidents reported.

Jun 28, 2020

No incidents reported.

Jun 27, 2020

No incidents reported.

Jun 26, 2020

No incidents reported.

Jun 25, 2020

ACI Critical Event: UP eCommerce Payments

Resolved - Resolved — Thursday, June 25, 2020 11:33 PM Central European Summer Time
ACI can confirm all messages have been caught up. The webhooks are now current and processing as normal. ACI has declared the issue resolved and will start its root cause assessment. We apologize for the impact to your business and your customer base. A fully documented RCA will be delivered in due course
Jun 25, 23:37 CEST

Monitoring - Fix In Progress — Thursday, June 25, 2020 11:20 PM Central European Summer Time
ACI can confirm the progression remains stable and the delayed messages are being processed. The webhook delay has been reduced to an estimate of about 10 minutes. ACI continues to monitor the system and the progress it is making. We expect all messages to be caught up and running current in about 20 minutes. We will report back when that would change.
Jun 25, 23:30 CEST

Update - Thursday, June 25, 2020 09:26 PM Central European Summer Time

ACI continuous to investigate the delay. Webhooks are currently processing but at a much lower throughput as normal. ACI is trying to determine how this can be accelerated to reduce customer impact as soon as possible. There is currently no ETA on resolution.
Jun 25, 22:31 CEST

Update - Thursday, June 25, 2020 09:49 PM Central European Summer Time

ACI continuous to triage the incident. The triage team is attempting to accelerate remaining webhooks pending in the message queue. The team has attempted to restart several application services and is now monitoring for improvement. There is currently no ETA on resolution.
Jun 25, 21:54 CEST

Update - Latest communication from ACI:

Investigating — Thursday, June 25, 2020 09:26 PM Central European Summer Time
ACI continuous to investigate the delay. Webhooks are currently processing but at a much lower throughput as normal. ACI is trying to determine how this can be accelerated to reduce customer impact as soon as possible. There is currently no ETA on resolution.
Jun 25, 21:31 CEST

Investigating - We received the following notification from ACI: Customers experience delay in receiving webhooks . Our incident response teams are actively working to restore the service, and we will ensure to provide regular updates on resolution activities. Please note that there is no impact to transaction-processing services as a result of this incident.
Jun 25, 21:22 CEST

Jun 24, 2020

No incidents reported.

Related