Peach Payments Outage History

Started Oct 21, 2026, 10:32 AM UTC· resolved Oct 21, 2026, 12:45 PM UTC

1. investigating Oct 21, 2026, 10:32 AM UTC

   Mobicred is currently experiencing degraded performance, resulting in merchants' customers not being able to pay using Mobicred. Our team is investigating the issue and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Oct 21, 2026, 12:45 PM UTC

   A fix has been implemented by Mobicred, and the incident has been resolved, so customers can now use Mobicred.

Read the full incident report →

Started Oct 19, 2026, 04:24 AM UTC· resolved Oct 19, 2026, 10:31 AM UTC

1. investigating Oct 19, 2026, 04:24 AM UTC

   MCB Juice is currently experiencing degraded performance resulting in merchants' customers not being able to pay using Juice method. Our team is investigating the issue and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. monitoring Oct 19, 2026, 06:16 AM UTC

   A fix has been implemented by MCB team and merchants' customer can now pay using Juice method. We apologise for any inconvenience caused and thank you for your patience while our team worked on the issue. If you have any questions or concerns, please contact [email protected] or your account manager.

3. resolved Oct 19, 2026, 10:31 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 16, 2026, 08:52 AM UTC· resolved Oct 16, 2026, 08:59 AM UTC

1. investigating Oct 16, 2026, 08:52 AM UTC

   We are currently investigating an incident whereby Payflex transactions are rejecting, we are giving this our full attention and will update shortly.

2. resolved Oct 16, 2026, 08:59 AM UTC

   No incident identified, Kindly ignore this notification.

Read the full incident report →

Started Oct 12, 2026, 12:40 PM UTC· resolved Oct 12, 2026, 02:19 PM UTC

1. investigating Oct 12, 2026, 12:40 PM UTC

   A+ is currently experiencing an issue where transactions are failing. Our team has already reported the issue to the provider, and they are investigating and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. monitoring Oct 12, 2026, 12:54 PM UTC

   We have observed successful A+ transactions. Monitoring is in place while the provider continues to troubleshoot. If you have any questions or concerns, please contact [email protected] or your account manager.

3. resolved Oct 12, 2026, 02:19 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 07, 2026, 11:19 AM UTC· resolved Oct 07, 2026, 11:41 AM UTC

1. monitoring Oct 07, 2026, 11:19 AM UTC

   We have observed issues with Payflex transaction. We are now seeing recovery as transactions are processing successfully. Payflex team are working towards a fix. We apologise for any inconvenience caused and will continue to update once we receive updates from Payflex. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Oct 07, 2026, 11:41 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2026, 12:38 PM UTC· resolved Sep 30, 2026, 12:57 PM UTC

1. investigating Sep 30, 2026, 12:38 PM UTC

   We are currently experiencing issues with 1Voucher transaction processing. Our team has raised the issue with the provider and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Sep 30, 2026, 12:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 30, 2026, 08:28 AM UTC· resolved Sep 30, 2026, 08:54 AM UTC

1. investigating Sep 30, 2026, 08:28 AM UTC

   We are currently experiencing issues with Payflex transaction processing. Our team has raised the issue with the Payflex team and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Sep 30, 2026, 08:54 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 29, 2026, 02:14 PM UTC· resolved Sep 29, 2026, 02:38 PM UTC

1. investigating Sep 29, 2026, 02:14 PM UTC

   We are currently experiencing issues with A+ transaction processing. Our team has raised the the issue with the provider and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Sep 29, 2026, 02:38 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 25, 2026, 06:44 PM UTC· resolved Sep 25, 2026, 08:07 PM UTC

1. investigating Sep 25, 2026, 06:44 PM UTC

   We are currently experiencing issues with RCS transaction processing. Our team has raised the the issue with RCS partner and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. monitoring Sep 25, 2026, 07:47 PM UTC

   We have observed successful RCS transaction. Monitoring is in place while downstream third party partner continues to troubleshoot.

3. resolved Sep 25, 2026, 08:07 PM UTC

   This incident has been resolved. RCS transactions are processing successfully.

Read the full incident report →

Started Sep 25, 2026, 01:57 PM UTC· resolved Sep 26, 2026, 06:09 AM UTC

1. identified Sep 25, 2026, 01:57 PM UTC

   Nedbank has advised that they are observing higher than usual unsuccessful transactions for Nedbank issued cards due to 3DS authentication failures on Nedbank's digital channels. Nedbank technical teams are currently investigating the issue on their bridge. Further updates will follow as more information becomes available. If you have any questions or require assistance, please contact [email protected] or reach out to your Account Manager.

2. resolved Sep 26, 2026, 06:09 AM UTC

   Nedbank has confirmed the services are restored.

Read the full incident report →

Started Sep 21, 2026, 12:03 PM UTC· resolved Sep 22, 2026, 06:46 AM UTC

1. investigating Sep 21, 2026, 12:03 PM UTC

   We are currently investigating an issue affecting card transactions in the Sandbox environment, where transactions are failing with 100.390.111 Communication Error to Scheme Directory Server. Our teams are actively working to identify the root cause and resolve the issue. Further updates will be shared on this page as soon as more information becomes available. If you have any questions or require assistance, please contact [email protected] reach out to your Account Manager.

2. resolved Sep 22, 2026, 06:46 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 15, 2026, 11:37 AM UTC· resolved Sep 15, 2026, 07:04 PM UTC

1. investigating Sep 15, 2026, 11:37 AM UTC

   We are currently experiencing downtime affecting in-store card processing, TERMINAL=All in-store Card processing down Our team is actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any inconvenience caused and appreciate your patience while we work towards a resolution. If you have any questions or concerns, please contact your Account Manager or email [email protected].

2. monitoring Sep 15, 2026, 11:45 AM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Sep 15, 2026, 07:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 14, 2026, 07:25 PM UTC· resolved Sep 15, 2026, 07:41 AM UTC

1. investigating Sep 14, 2026, 07:25 PM UTC

   A+ is currently experiencing an issue where all transactions are failing. Our team has already reported the issue to the provider, and they are investigating and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. monitoring Sep 14, 2026, 09:35 PM UTC

   We have observed successful A+ transactions. Monitoring is in place while the provider continues to troubleshoot. If you have any questions or concerns, please contact [email protected] or your account manager.

3. resolved Sep 15, 2026, 07:41 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 12, 2026, 09:52 PM UTC· resolved Sep 12, 2026, 11:03 PM UTC

1. investigating Sep 12, 2026, 09:52 PM UTC

   We have escalated to partner for MCB juice transaction rejecting.

2. identified Sep 12, 2026, 09:59 PM UTC

   MCB juice are under maintenance until 1am SAST This is a planned maintenance window

3. identified Sep 12, 2026, 10:03 PM UTC

   MCB Juice, MCB JuicePro et Internet Banking seront hors ligne le dimanche 13 septembre de 00:00 à 03:00.

4. resolved Sep 12, 2026, 11:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 02:20 PM UTC· resolved Sep 09, 2026, 03:15 PM UTC

1. investigating Sep 09, 2026, 02:20 PM UTC

   We are currently experiencing an issue where merchants cannot access the settings page on the Peach Dashboard. Our team is investigating the issue and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. identified Sep 09, 2026, 02:21 PM UTC

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

3. resolved Sep 09, 2026, 03:15 PM UTC

   This incident has been resolved. The Settings page on the Peach Dashboard can now be accessed.

Read the full incident report →

Started Sep 09, 2026, 08:28 AM UTC· resolved Sep 09, 2026, 08:28 AM UTC

1. resolved Sep 09, 2026, 08:28 AM UTC

   Peach Payments' Pay by Bank payment option has temporarily discontinued support for Old Mutual Bank. This change follows Old Mutual Bank’s decision to discontinue the internet banking services required to process EFT transactions. If you have any questions or concerns, please contact [email protected] or reach out directly to your account manager.

Read the full incident report →

Started Sep 03, 2026, 07:45 PM UTC· resolved Sep 04, 2026, 02:11 AM UTC

1. investigating Sep 03, 2026, 07:45 PM UTC

   We have raised an incident to our 1Voucher partner to investigate an incident causing 1Voucher transactions to fail.

2. resolved Sep 04, 2026, 02:11 AM UTC

   The issue has been resolved. Merchants' customer can now pay using 1Voucher. We apologise for any inconvenience caused and thank you for your patience while our team worked on the issue. If you have any questions or concerns, please contact [email protected] or your account manager.

Read the full incident report →

Started Sep 03, 2026, 05:32 AM UTC· resolved Sep 03, 2026, 10:01 AM UTC

1. investigating Sep 03, 2026, 05:32 AM UTC

   MCB Juice is currently experiencing an issue where some transactions are failing. Our team has already reported the issue to the provider, and they are investigating and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Sep 03, 2026, 10:01 AM UTC

   This issue has been resolved. Merchants' customers can now pay using MCB Juice. We apologise for any inconvenience caused and thank you for your patience while our team worked on the issue. If you have any questions or concerns, please contact [email protected] or your account manager.

Read the full incident report →

Started Sep 01, 2026, 04:39 PM UTC· resolved Sep 01, 2026, 06:00 PM UTC

1. investigating Sep 01, 2026, 04:39 PM UTC

   1Voucher is currently experiencing an issue where transactions are failing. Our team has already reported the issue to the provider, and they are investigating and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Sep 01, 2026, 06:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 01, 2026, 02:20 PM UTC· resolved Sep 01, 2026, 03:09 PM UTC

1. investigating Sep 01, 2026, 02:20 PM UTC

   We are currently experiencing a delay of up to 25 minutes in transactions appearing on the dashboard. Please rest assured that transaction processing is fully operational and unaffected. Our engineering team is actively investigating the issue to restore real-time dashboard updates. We apologise for the inconvenience and will provide further updates here as we make progress.

2. monitoring Sep 01, 2026, 02:58 PM UTC

   A fix has been implemented, and dashboard updates are stabilising. We are closely monitoring system performance and will provide further updates as needed.

3. resolved Sep 01, 2026, 03:09 PM UTC

   The dashboard delay has been fixed, and all transactions are now updating normally.

Read the full incident report →

Started Aug 31, 2026, 11:39 AM UTC· resolved Aug 31, 2026, 11:51 AM UTC

1. investigating Aug 31, 2026, 11:39 AM UTC

   FNB is currently experiencing intermittent connectivity issues which is impacting the following services: Collections AVS EFT E-wallet As a result, some transactions may be delayed or take longer than usual to process. FNB's technical teams are actively investigating the issue and working to restore normal service as quickly as possible. We are closely monitoring the situation and will provide further updates as soon as additional information becomes available, including confirmation once services have been fully restored. We apologise for any inconvenience caused and appreciate your patience and understanding.

Read the full incident report →

Started Aug 30, 2026, 05:03 AM UTC· resolved Aug 30, 2026, 05:26 AM UTC

1. investigating Aug 30, 2026, 05:03 AM UTC

   We are currently experience downtime on our Peach Payments checkout, whereby cardholders are unable to checkout.

2. resolved Aug 30, 2026, 05:26 AM UTC

   This incident has been resolved - an RCA will be shared by Monday 31 August 2026

3. postmortem Sep 01, 2026, 05:51 AM UTC

   **Checkout Outage** **Issued: 31 August 2026** **What was affected?** On Sunday 30 August 2026, checkout requests failed or timed out from 04:03:46 until 07:19:30 SAST \(3 hours 16 minutes\). Shoppers attempting to complete payment via standard Checkout or Checkout v2 experienced failures and hung requests until the request timeout was reached. **What was the root cause?** Checkout maintains session and merchant data in a managed cache. During a scheduled weekly provider maintenance window \(opened 04:00:00 SAST\), the provider replaced the primary node in the cluster and completed a failover to the replica at 04:03:46.312 SAST. Our services were unable to detect the stale connection and remained connected to the failing node. Warm application instances retained hanging connections to the replaced node, causing every new checkout request to reuse the stale connection and wait out the full request timeout. The service interruption persisted until we manually failed over to a healthy node, which restored services at 07:19:30 [SAST.At](http://SAST.At) 08:01:35 SAST we attempted to fail over to an alternative cache service which was assumed to be more reliable. However, this cache service was incompatible with our cache client. Warm application instances were still reusing the original cluster connection so checkout requests succeeded for several minutes after the switch to the alternate cluster. At 08:49:04 SAST we saw intermittent errors as our application instances started using the alternate cluster causing a second outage. At this point we swapped back to the original cache service which began restoration of traffic at 09:12:00 SAST with all traffic succeeding by 09:13:39 SAST.Furthermore, an observability gap existed where initial alerts failed to page the relevant teams, leading to delayed incident response. **Resolution and Remediation** **Incident Timeline & Response:** **04:00:00 SAST**: Provider maintenance window opened. **04:03:46 SAST**: Provider failover completed; first write errors landed on replaced node. **04:03:46 SAST**: First failed request to checkout v1 **04:03:49 SAST**: First failed request to checkout v2 **04:07:01 SAST:** SEV-1 Alarm fired for escalating checkout issues **06:08:00 SAST**: Support reported a spike in Internal server errors **06:19:00 SAST**: Teams started investigating the cause of the outage **07:12:40 SAST**: Temporary manual failback to the remaining healthy node was initiated. **07:19:30 SAST**: Last checkout requests timed out. Service restored **07:20:00 SAST**: Latency returned to normal \(~385 ms\) with zero remaining errors. **08:01:35** **SAST**: Attempt to reconfigure a more reliable cache cluster **08:49:04 SAST**: Observed an increase in checkout errors **09:12:00 SAST**: Revert to original cache service **09:13:39 SAST**: Last checkout requests timed out. Full service restored ‌ **Mitigation Actions** **Stale connection detection**: Configure explicit timeouts on our cache client so dead node connections fail quickly rather than exhausting the full request duration. **Connection Pool Recycling**: Ensure connections are closed or rebuilt on errors/timeouts so subsequent requests establish new connections to the active primary node. **Improved alerting**: We are implementing more comprehensive system monitoring to detect checkout-related errors faster. **If you have any questions concerning the content of this RCA, please open a case via** [**[email protected]**](mailto:[email protected]) **Alternatively, please contact your relevant Account Managers for alternative methods of contacting emergency support.**

Read the full incident report →

Started Aug 28, 2026, 02:35 AM UTC· resolved Aug 28, 2026, 06:13 AM UTC

1. investigating Aug 28, 2026, 02:35 AM UTC

   We are experiencing a high number of transactions being unsuccessful for Capitec Pay. We have escalated to Capitec for investigation and will update accordingly as we receive further information.

2. monitoring Aug 28, 2026, 03:53 AM UTC

   Capitec have advised that this incident is resolved, we are currently monitoring.

3. resolved Aug 28, 2026, 06:13 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 26, 2026, 12:48 PM UTC· resolved Aug 27, 2026, 03:26 AM UTC

1. investigating Aug 26, 2026, 12:48 PM UTC

   We are currently experiencing issues with RCS transaction processing. Our team has raised the the issue with RCS partner and working to resolve it as soon as possible. We apologise for any inconvenience caused and will continue to update this status page as we make progress. If you have any questions or concerns, please contact [email protected] or your account manager.

2. resolved Aug 27, 2026, 03:26 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 25, 2026, 07:03 AM UTC· resolved Aug 27, 2026, 03:25 AM UTC

1. investigating Aug 25, 2026, 08:03 AM UTC

   We are currently investigating an intermittent issue affecting card transactions in the Sandbox environment, where transactions may fail with an "unexpected communication error with connector/acquirer" response. Our teams are actively working to identify the root cause and resolve the issue. Further updates will be shared on this page as soon as more information becomes available. If you have any questions or require assistance, please contact [email protected] or reach out to your Account Manager.

2. monitoring Aug 25, 2026, 01:43 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Aug 27, 2026, 03:25 AM UTC

   This incident has been resolved.

Read the full incident report →