KORT Payments Outage History

KORT Payments is up right now

KORT Payments had 2 outages in the last 2 years totaling 26h 37m of downtime, averaging 0.1 incidents per month.

There were 2 KORT Payments outages since August 20, 2026 totaling 26h 37m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.kortpayments.com

Minor September 15, 2026

Delay in Funding to Payfacto Merchants

Detected by Pingoru
Sep 15, 2026, 03:55 PM UTC
Resolved
Sep 16, 2026, 06:02 PM UTC
Duration
1d 2h
Affected: PayFacto
Timeline · 4 updates
  1. investigating Sep 15, 2026, 03:55 PM UTC

    We are currently investigating this issue.

  2. investigating Sep 15, 2026, 03:57 PM UTC

    The PayFacto has reported a delay in funding: We have been notified by our banking partner that there may be a potential funding delay for the September 15 deposit of transactions processed on September 14. If this delay occurs, the deposit for these transactions will be completed before the end of the day. We are closely monitoring the processing, and we will inform you if the timeline needs to be adjusted. We sincerely apologize for any inconvenience this may cause. Thank you for your understanding. PayFacto

  3. monitoring Sep 16, 2026, 12:58 AM UTC

    PayFacto has confirmed that all the Payments for 14th will be deposited by EOD Sep 15th. Merchant Services are monitoring the situation.

  4. resolved Sep 16, 2026, 06:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 20, 2026

PXP response payloads returning double 'PostDate' error

Detected by Pingoru
Aug 20, 2026, 04:03 PM UTC
Resolved
Aug 20, 2026, 04:33 PM UTC
Duration
30m
Affected: Webhost and ACH Processing API's
Timeline · 4 updates
  1. investigating Aug 20, 2026, 04:03 PM UTC

    We are currently investigating this issue.

  2. identified Aug 20, 2026, 04:03 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Aug 20, 2026, 04:25 PM UTC

    The change which caused the issue is rolled back. The team is monitoring the situation and validating to see if the issue still exsists.

  4. resolved Aug 20, 2026, 04:33 PM UTC

    This incident has been resolved.

Read the full incident report →