Peach Payments Outage History

Started May 15, 2026, 09:19 AM UTC· resolved May 15, 2026, 10:02 AM UTC

1. investigating May 15, 2026, 09:19 AM UTC

   Capitec Pay is currently experiencing timeouts. Our team is liaising with them, 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 May 15, 2026, 09:30 AM UTC

   The issue has been resolved and we are monitoring the traffic.

3. resolved May 15, 2026, 10:02 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 30, 2026, 05:34 AM UTC· resolved Apr 30, 2026, 03:45 PM UTC

1. investigating Apr 30, 2026, 05:34 AM UTC

   Peach in-store and card processing service is currently experiencing degraded performance. Our team is working on resolving this 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. investigating Apr 30, 2026, 05:40 AM UTC

   We are continuing to investigate this issue.

3. investigating Apr 30, 2026, 09:53 AM UTC

   We are continuing to investigate on the issue. This does not affect E-commerce card processing.

4. monitoring Apr 30, 2026, 11:06 AM UTC

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

5. resolved Apr 30, 2026, 03:45 PM UTC

   This incident has been resolved. But we continue to monitor for stability

Read the full incident report →

Started Apr 28, 2026, 09:26 AM UTC· resolved Apr 29, 2026, 08:04 AM UTC

1. identified Apr 28, 2026, 02:05 PM UTC

   We are currently experiencing a delay in transactions reflecting on the sandbox dashboard. Please note that this does not affect transactions processing, transactions are being processed successfully, and our team is actively working to resolve this. This does not impact the live environment. We apologise for any inconvenience caused and we 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 Apr 29, 2026, 01:04 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 18, 2026, 03:12 PM UTC· resolved Apr 23, 2026, 03:52 PM UTC

1. investigating Apr 18, 2026, 03:12 PM UTC

   EFT is currently unavailable for Standard Bank account holders. Our teams are engaging Standard Bank in this regard and will update of changes.

2. resolved Apr 23, 2026, 03:52 PM UTC

   Only EFT secure impacted - not Pay By Bank

Read the full incident report →

Started Apr 09, 2026, 11:39 PM UTC· resolved Apr 13, 2026, 05:21 AM UTC

1. investigating Apr 09, 2026, 11:39 PM UTC

   We are currently experiencing intermittent rejections with in-store card processing, which may cause some transactions to fail unexpectedly. Our team is actively investigating the problem and working to resolve it as quickly as possible. We apologize for any inconvenience and appreciate your patience. If you have any queries or concerns, please reach out to your Account Manager or send a email to [email protected]

2. investigating Apr 10, 2026, 02:42 AM UTC

   We are working with the acquirer to restore this connection, we will continue to update as the status is updated.

3. investigating Apr 10, 2026, 06:19 AM UTC

   We are still working with the acquirer to restore this connection and we 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.

4. monitoring Apr 10, 2026, 06:42 AM UTC

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

5. resolved Apr 13, 2026, 05:21 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 09, 2026, 07:51 AM UTC· resolved Apr 09, 2026, 11:48 AM UTC

1. investigating Apr 09, 2026, 07:51 AM UTC

   We are currently observing failures on Mobicred transactions with the error: “Failed (900.100.100) – unexpected communication error with connector/acquirer.” This has been escalated to Mobicred for investigation, and we will provide updates as soon as more information becomes available. If you have any questions or concerns, please contact [email protected] or your account

2. monitoring Apr 09, 2026, 08:40 AM UTC

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

3. identified Apr 09, 2026, 09:35 AM UTC

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

4. resolved Apr 09, 2026, 11:48 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 07, 2026, 09:56 AM UTC· resolved Apr 07, 2026, 11:01 AM UTC

1. investigating Apr 07, 2026, 09:56 AM UTC

   Please note that Capitec are currently experiencing an issue with their Capitec App push notifications. The teams are working on the issue and we will update accordingly. Date: Tuesday 7 April 2026 Time: From 10:30AM and ongoing Impacted Applications: APP, Capitec Pay and Secure Data APIs

2. resolved Apr 07, 2026, 11:01 AM UTC

   Please note that the issue with the Capitec App push notifications has been resolved. Capitec will continue to monitor.

Read the full incident report →

Started Mar 24, 2026, 02:58 PM UTC· resolved Mar 24, 2026, 03:21 PM UTC

1. investigating Mar 24, 2026, 02:58 PM UTC

   We are currently investigating an incident impacting the transactions details "tab" in dashboard. Transactions are not affected, only the underlying detail is not being surfaced when clicking for additional information. We will update as we continue to investigate.

2. investigating Mar 24, 2026, 03:21 PM UTC

   This incident has been resolved.

3. resolved Mar 24, 2026, 03:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 16, 2026, 03:39 PM UTC· resolved Jun 11, 2026, 09:56 AM UTC

1. investigating Mar 16, 2026, 03:39 PM UTC

   Our team is investigating an issue affecting Samsung Pay and is working to resolve it as soon as possible. This will affect merchants processing transactions. Samsung Pay sandbox and live checkout If you have any questions or concerns, please contact [email protected] or your account manager.

2. investigating Mar 16, 2026, 03:41 PM UTC

   We are continuing to investigate this issue.

3. investigating Mar 16, 2026, 03:41 PM UTC

   Our team is investigating an issue affecting Samsung Pay and is working to resolve it as soon as possible. This will affect merchants processing transactions. Customers are not able to see Samsung Pay sandbox and live checkout If you have any questions or concerns, please contact [email protected] or your account manager.

4. resolved Jun 11, 2026, 09:56 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 04, 2026, 06:44 PM UTC· resolved Mar 04, 2026, 08:02 PM UTC

1. investigating Mar 04, 2026, 06:44 PM UTC

   Our team is investigating an issue affecting Peach In-store card processing and refund via Peach card processing platform and is working to resolve it as soon as possible. This will affect merchants processing transactions to Nedbank and cause degraded service/all transactions to fail. We apologise for any loss of service 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 Mar 04, 2026, 08:02 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 27, 2026, 04:00 AM UTC· resolved Feb 27, 2026, 08:00 AM UTC

1. investigating Feb 27, 2026, 04:00 AM UTC

   We are currently investigating an issue impacting A+ transactions. Our team is working to identify the cause with the provider and restore normal service as quickly 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 Feb 27, 2026, 08:00 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 20, 2026, 01:16 PM UTC· resolved Feb 23, 2026, 06:08 AM UTC

1. investigating Feb 20, 2026, 01:16 PM UTC

   We are currently investigating an issue affecting card transactions on Checkout in the Sandbox environment, where transactions may fail with an “invalid card number” 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] reach out to your Account Manager.

2. resolved Feb 23, 2026, 06:08 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 18, 2026, 07:58 AM UTC· resolved Feb 18, 2026, 08:14 AM UTC

1. investigating Feb 18, 2026, 07:58 AM UTC

   We are currently experiencing an issue where WhatsApp messages are not being sent for Payment Links. Our team is investigating 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 Feb 18, 2026, 08:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 02, 2026, 11:25 AM UTC· resolved Feb 02, 2026, 11:25 AM UTC

1. investigating Feb 02, 2026, 10:45 AM UTC

   Peach instore service is currently experiencing intermittent connectivity issue leading to timeouts. Our team is working on resolving this 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 Feb 02, 2026, 10:48 AM UTC

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

3. resolved Feb 04, 2026, 11:11 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 26, 2026, 07:42 AM UTC· resolved Jan 26, 2026, 08:18 AM UTC

1. investigating Jan 26, 2026, 07:51 AM UTC

   The Peach Payouts service provider is currently experiencing intermittent downtime, resulting in timeouts when accessing the payout portal. The team is actively working to resolve the issue and we will provide updates as progress is made. If you have any questions or concerns, please contact [email protected] or reach out to your account manager.

2. monitoring Jan 26, 2026, 07:54 AM UTC

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

3. resolved Jan 26, 2026, 08:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 15, 2026, 05:57 AM UTC· resolved Jan 15, 2026, 01:25 PM UTC

1. investigating Jan 15, 2026, 05:57 AM UTC

   We are currently experiencing an issue with latency on recurring payment. 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 Jan 15, 2026, 07:54 AM UTC

   The issue is resolved. We are currently monitoring.

3. resolved Jan 15, 2026, 01:25 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 30, 2025, 06:47 AM UTC· resolved Jan 22, 2026, 09:16 AM UTC

1. investigating Dec 30, 2025, 06:47 AM UTC

   We are currently experiencing Maucas transaction failures with error response from connector/acquirer. Our team has raised the issue with Maucas and actively working to resolve it as soon as possible. We apologies 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 Jan 22, 2026, 09:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 23, 2025, 10:11 AM UTC· resolved Jan 22, 2026, 09:16 AM UTC

1. investigating Dec 23, 2025, 10:11 AM UTC

   We are currently experiencing M-Pesa transaction failures with error response from connector/acquirer. Our team has raised the issue with Mpesa and actively 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. investigating Dec 23, 2025, 10:12 AM UTC

   We are continuing to investigate this issue.

3. resolved Jan 22, 2026, 09:16 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 19, 2025, 02:04 PM UTC· resolved Dec 19, 2025, 03:39 PM UTC

1. investigating Dec 19, 2025, 02:04 PM UTC

   Tyme Bank is currently experiencing degraded performance resulting in merchants' customers not being able to pay using Tyme bank issued cards. Our team is investigating the issue with Tyme bank's team and will advise further once we have update. 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 Dec 19, 2025, 03:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 09:06 AM UTC· resolved Dec 05, 2025, 11:30 AM UTC

1. investigating Dec 05, 2025, 09:06 AM UTC

   Our platforms and services might experience intermittent downtime as a result of the global Cloudflare connectivity issue. Please note that we are available on our support line, as we wait for the fix on cloudflare side. Our Eng teams are actively working on this. Please contact your KAM or send a email to our [email protected]

2. investigating Dec 05, 2025, 09:07 AM UTC

   We are continuing to investigate this issue.

3. monitoring Dec 05, 2025, 09:21 AM UTC

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

4. monitoring Dec 05, 2025, 09:42 AM UTC

   We are continuing to monitor for any further issues.

5. monitoring Dec 05, 2025, 10:08 AM UTC

   We are continuing to monitor for any further issues.

6. resolved Dec 05, 2025, 11:30 AM UTC

   The issue has been resolved and all services affected by Cloudflare outage has been restored. If you have any questions or concerns, please contact [email protected] or your account manager.

7. postmortem Jan 27, 2026, 01:12 PM UTC

   What was affected? On 5 December 2025, we experienced a service disruption affecting Checkout and Payments API authentication between 08:47 and 09:12 UTC. During this period, merchants were unable to generate new authentication credentials required for these services. The incident was caused by a global outage at Cloudflare, a major internet infrastructure provider. This outage affected our identity provider \(Auth0\), which relies on Cloudflare for DNS and endpoint protection. The disruption prevented our systems from communicating with Auth0 to issue and verify authentication tokens. Our Server-to-Server integration \([card.peachpayments.com](http://card.peachpayments.com)\) was unaffected by this incident, as it does not depend on the same authentication infrastructure. ‌ What was the root cause? Cloudflare experienced a significant outage broadly affecting their global HTTP traffic. Auth0, our identity provider for merchant authentication, uses Cloudflare for both DNS resolution and endpoint protection. When Cloudflare’s services became unavailable, our checkout systems could not reach Auth0 to generate or verify the JSON Web Key Set \(JWKS\) credentials required for secure authentication. This created a single point of failure: our authentication flow was entirely dependent on the availability of both Auth0 and its upstream provider, Cloudflare. Impact to Merchants During the incident window, merchants using Checkout or the Payments API experienced the following issues: • Unable to generate new authentication credentials • New payment transactions could not be initiated via affected services • Existing authenticated sessions continued to function until token expiry Merchants using our Server-to-Server integration \([card.peachpayments.com](http://card.peachpayments.com)\) were not affected and could continue processing transactions normally throughout the incident. Additionally, some payment methods and platforms experienced independent disruptions due to their own Cloudflare dependencies. Capitec Pay via the Payments API and Shopify integrations were temporarily unavailable as these partners experienced separate downstream impacts from the same Cloudflare outage. Additionally users that did not have an active dashboard session were unable to log-in and perform dashboard operations. Once service was restored, all pending operations resumed normally with no data loss. Immediate response Upon detecting the outage, our engineering team immediately attempted to route authentication traffic directly to Auth0’s regional endpoints, bypassing Cloudflare’s infrastructure. While this mitigation was being deployed, Cloudflare resolved the underlying issue, restoring full service.

Read the full incident report →

Started Dec 03, 2025, 12:03 PM UTC· resolved Dec 03, 2025, 02:20 PM UTC

1. investigating Dec 03, 2025, 12:03 PM UTC

   Our Payment Links service is currently experiencing intermittent connectivity issues. Our team is working to resolve this 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 Dec 03, 2025, 12:35 PM UTC

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

3. resolved Dec 03, 2025, 02:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 28, 2025, 11:20 AM UTC· resolved Nov 28, 2025, 11:39 AM UTC

1. investigating Nov 28, 2025, 11:20 AM UTC

   We are currently experiencing an issue where with Nedbank card acquiring. Our team is investigating the issue with our 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 Nov 28, 2025, 11:27 AM UTC

   The issue has been resolved.

3. resolved Nov 28, 2025, 11:39 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 28, 2025, 09:58 AM UTC· resolved Nov 28, 2025, 03:06 PM UTC

1. monitoring Nov 28, 2025, 09:58 AM UTC

   We are actively monitoring a technical incident affecting FNB-issued cards. Issue Summary: Customers may experience debits on their accounts, followed by a transaction decline from FNB with the response code “05: Do Not Honor.” Current Status: FNB has confirmed that their systems are currently undergoing recovery. We remain in close communication with their team and will update this status page as soon as full resolution and stability are confirmed. Thank you for your patience and understanding as we work through this external issue.

2. resolved Nov 28, 2025, 03:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 12:14 PM UTC· resolved Nov 19, 2025, 05:17 AM UTC

1. identified Nov 18, 2025, 12:14 PM UTC

   Our platforms and services are experiencing intermittent downtime as a result of a widespread Cloudflare connectivity issue. Among the affected Services/Platforms: Dashboard Freshdesk Payout Services Payment processing Reconciliation services Please note that we are available on our support line, as we wait for the fix on cloudflare side.

2. identified Nov 18, 2025, 01:43 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Nov 18, 2025, 02:56 PM UTC

   Monitoring - Cloudflare has implemented a fix. We are continuing to monitor for errors to ensure all services are back to normal.

4. resolved Nov 19, 2025, 05:17 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 18, 2025, 12:05 PM UTC· resolved Nov 19, 2025, 05:17 AM UTC

1. investigating Nov 18, 2025, 12:05 PM UTC

   Peach in-store service is currently experiencing intermittent connectivity issue. Our team is working on resolving this 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 Nov 18, 2025, 12:17 PM UTC

   The issue has been resolved and transaction processing restored for all merchants. 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. identified Nov 18, 2025, 12:39 PM UTC

   The service is intermittently down due to the global Cloudflare network issue.

4. monitoring Nov 18, 2025, 02:57 PM UTC

   Monitoring - Cloudflare has implemented a fix. We are continuing to monitor for errors to ensure all services are back to normal.

5. identified Nov 18, 2025, 04:07 PM UTC

   We have observed that the service is intermittently down due to the global Cloudflare network issue. We are monitoring and will continue to update this status page as we make progress.

6. monitoring Nov 18, 2025, 05:43 PM UTC

   Monitoring - Cloudflare has implemented a fix. We are continuing to monitor for errors to ensure all services are back to normal.

7. resolved Nov 19, 2025, 05:17 AM UTC

   This incident has been resolved.

Read the full incident report →