Banking Circle Outage History

Started Sep 11, 2026, 10:44 AM UTC· resolved Sep 11, 2026, 11:33 AM UTC

1. identified Sep 11, 2026, 10:44 AM UTC

   We have identified an issue impacting some of our clients, that is causing delays in inbound payments being booked to clients accounts. We are currently in a process of deploying a fix that should mitigate this issue.

2. monitoring Sep 11, 2026, 11:02 AM UTC

   A fix has been implemented and we see payments are booking correctly now. We continue to monitor the results and we will confirm in the next update once the backlog is cleared.

3. resolved Sep 11, 2026, 11:33 AM UTC

   The backlog of messages has been processed and the incident has been resolved.

Read the full incident report →

Started Sep 04, 2026, 02:55 AM UTC· resolved Sep 04, 2026, 07:18 AM UTC

1. investigating Sep 04, 2026, 02:55 AM UTC

   We are currently experiencing a partial outage on our payment service, which is causing delays in the processing of outgoing SEPA Instant payments. All other Payments are being processed as normal. Our teams are actively investigating the issue and working to restore normal processing as quickly as possible. We will provide further updates as soon as more information becomes available. We apologise for any inconvenience this may cause and appreciate your patience while we work to resolve the issue.

2. monitoring Sep 04, 2026, 05:58 AM UTC

   We have implemented a fix and see payments are now processing. We will continue to monitor.

3. resolved Sep 04, 2026, 07:18 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 05, 2026, 05:53 AM UTC· resolved Aug 06, 2026, 06:14 AM UTC

1. investigating Aug 05, 2026, 05:53 AM UTC

   We are aware of an ongoing issue affecting our authorization process. Users may experience intermittent connectivity issues when accessing the Authorization API. Most authentication requests continue to process successfully, so the impact appears limited to a small percentage of requests. We are investigating this as a high priority and will provide an update as soon as possible.

2. investigating Aug 05, 2026, 06:51 AM UTC

   We are continuing to investigate this issue.

3. investigating Aug 05, 2026, 08:31 AM UTC

   We are continuing to investigate this issue.

4. monitoring Aug 05, 2026, 10:41 AM UTC

   Following internal investigation we see error rates have dropped significantly. Payments continue to process successfully, and transaction volumes appear comparable to normal levels. We can see the connectivity restored and we are actively monitoring the situation.

5. monitoring Aug 05, 2026, 11:33 AM UTC

   We are continuing to monitor for any further issues.

6. monitoring Aug 05, 2026, 12:34 PM UTC

   We are continuing to monitor for any further issues.

7. monitoring Aug 05, 2026, 02:24 PM UTC

   We have been working closely with our 3rd party provider regarding intermittent connectivity issues affecting a component of our Authorisation platform. Our vendor has identified the underlying cause and deployed corrective measures. Early verification shows a significant improvement and the service is operating normally while additional monitoring continues. As a precaution, we are completing further validation before restoring full infrastructure redundancy. There is currently no action required from clients, and we continue to monitor the platform closely together with our external provider. Further updates will be provided if required.

8. resolved Aug 06, 2026, 06:14 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 20, 2026, 01:49 PM UTC· resolved Jul 27, 2026, 03:04 PM UTC

1. identified Jul 20, 2026, 01:49 PM UTC

   Some of the clients may experience difficulties accessing BC Connect, with the login page remaining in a continuous loading state, as well as timeouts on some of our API's. Our engineering team is currently investigating the issue.

2. identified Jul 20, 2026, 01:53 PM UTC

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

3. monitoring Jul 20, 2026, 03:46 PM UTC

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

4. monitoring Jul 20, 2026, 06:01 PM UTC

   We are continuing to monitor for any further issues.

5. monitoring Jul 20, 2026, 08:21 PM UTC

   We are continuing to monitor for any further issues. Next update is planned for 06:00 UTC or in case of any major development.

6. identified Jul 21, 2026, 06:36 AM UTC

   Some of the clients may experience timeouts on some of our API's. Our engineering team is currently investigating the issue and monitoring further.

7. identified Jul 21, 2026, 07:50 AM UTC

   Some of the clients may experience difficulties accessing BC Connect, with the login page remaining in a continuous loading state, as well as timeouts on some of our API's. Our engineering team is currently investigating the issue.

8. identified Jul 21, 2026, 08:34 AM UTC

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

9. monitoring Jul 21, 2026, 10:50 AM UTC

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

10. monitoring Jul 21, 2026, 01:59 PM UTC

    We are aware some clients are reporting API Connectivity issues on certain end points. This is continually being monitored and we are aware of this. Updates to follow.

11. monitoring Jul 21, 2026, 06:40 PM UTC

    We are continuing to monitor for any further issues.

12. monitoring Jul 22, 2026, 10:08 AM UTC

    We are aware that some clients may still experience intermittent difficulties accessing the BC UI, as well as occasional timeouts on some of our APIs. The situation is being closely monitored, and our engineering team is continuously working to address each issue individually as soon as it arises. We appreciate your patience and understanding while we work to restore full stability

13. monitoring Jul 22, 2026, 12:37 PM UTC

    We are continuing to monitor for any further issues.

14. monitoring Jul 22, 2026, 06:28 PM UTC

    We are continuing to monitor for any further issues.

15. monitoring Jul 23, 2026, 07:34 AM UTC

    We are continuing to monitor for any further issues.

16. monitoring Jul 23, 2026, 01:50 PM UTC

    We are continuing to monitor for any further issues.

17. monitoring Jul 24, 2026, 05:34 AM UTC

    We are continuing to monitor for any further issues.

18. monitoring Jul 24, 2026, 11:16 AM UTC

    We are continuing to monitor for any further issues.

19. monitoring Jul 24, 2026, 12:34 PM UTC

    We are continuing to monitor for any further issues.

20. monitoring Jul 24, 2026, 04:11 PM UTC

    We are continuing to monitor for any further issues.

21. monitoring Jul 25, 2026, 06:52 AM UTC

    We are continuing to monitor for any further issues.

22. monitoring Jul 25, 2026, 08:28 PM UTC

    We are continuing to monitor for any further issues.

23. monitoring Jul 26, 2026, 07:27 AM UTC

    We are continuing to monitor for any further issues.

24. monitoring Jul 26, 2026, 08:09 PM UTC

    We are continuing to monitor for any further issues.

25. monitoring Jul 27, 2026, 08:56 AM UTC

    We are continuing to monitor for any further issues.

26. resolved Jul 27, 2026, 03:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Jul 17, 2026, 05:53 AM UTC· resolved Jul 17, 2026, 07:57 PM UTC

1. identified Jul 17, 2026, 05:53 AM UTC

   Users may experience difficulties accessing BC Connect, with the login page remaining in a continuous loading state. Our engineering team is currently investigating the issue.

2. identified Jul 17, 2026, 06:00 AM UTC

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

3. monitoring Jul 17, 2026, 06:44 AM UTC

   A fix has been implemented and we are monitoring the results. BC Connect login page is accessible again.

4. monitoring Jul 17, 2026, 08:34 AM UTC

   We are continuing to monitor for any further issues.

5. identified Jul 17, 2026, 09:58 AM UTC

   We are aware of some of the users may experience difficulties accessing BC Connect, with the login page remaining in a continuous loading state. Our engineering team is currently investigating the issue.

6. identified Jul 17, 2026, 12:09 PM UTC

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

7. identified Jul 17, 2026, 01:37 PM UTC

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

8. identified Jul 17, 2026, 03:20 PM UTC

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

9. identified Jul 17, 2026, 04:30 PM UTC

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

10. resolved Jul 17, 2026, 07:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Started Jul 16, 2026, 06:04 AM UTC· resolved Jul 16, 2026, 11:16 PM UTC

1. identified Jul 16, 2026, 06:04 AM UTC

   We are aware of an incident impacting connectivity via API and BCUI for some of our clients. We are currently investigating the issue.

2. identified Jul 16, 2026, 06:39 AM UTC

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

3. identified Jul 16, 2026, 07:15 AM UTC

   We are continuing to work on a fix for the issue. Updates will follow.

4. identified Jul 16, 2026, 07:32 AM UTC

   Please be advised the API is now working. Banking Circle Connect remains impacted and we are working on a fix.

5. identified Jul 16, 2026, 08:37 AM UTC

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

6. identified Jul 16, 2026, 09:06 AM UTC

   Banking Circle Connect remains impacted and we continue working on a fix.

7. identified Jul 16, 2026, 10:28 AM UTC

   We are currently investigating an issue with our external service provider. At this time, our API endpoints and internal processing capabilities remain available and operating as expected.

8. identified Jul 16, 2026, 12:03 PM UTC

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

9. identified Jul 16, 2026, 12:44 PM UTC

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

10. identified Jul 16, 2026, 01:39 PM UTC

    We are continuing to work on a fix for this issue with our external service provider.

11. identified Jul 16, 2026, 02:37 PM UTC

    We are continuing to work on a fix for this issue with our external service provider.

12. identified Jul 16, 2026, 03:57 PM UTC

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

13. identified Jul 16, 2026, 05:00 PM UTC

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

14. identified Jul 16, 2026, 07:40 PM UTC

    We are currently working with our external service provider on a fix that is scheduled to be deployed within the next 4-6 hours, aimed to restore Banking Circle Connect availability. Next update is planned for Friday 07:00 UTC or in case of new development"

15. resolved Jul 16, 2026, 11:16 PM UTC

    The incident is now resolved. Clients will now be able to log into the Banking Circle Connect UI.

Read the full incident report →

Started Jul 15, 2026, 11:28 AM UTC· resolved Jul 15, 2026, 07:29 PM UTC

1. identified Jul 15, 2026, 11:28 AM UTC

   We’re aware of a problem impacting WebHook delivery for some clients and are looking into it.

2. identified Jul 15, 2026, 11:35 AM UTC

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

3. identified Jul 15, 2026, 12:30 PM UTC

   We are still investigating the delays to webhooks delivery for some of the clients.

4. identified Jul 15, 2026, 01:21 PM UTC

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

5. identified Jul 15, 2026, 02:19 PM UTC

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

6. monitoring Jul 15, 2026, 03:55 PM UTC

   A fix has been deployed, and we are monitoring the results. We are currently processing the backlog of delayed webhooks. This incident will be considered resolved once all delayed webhooks have been processed.

7. resolved Jul 15, 2026, 07:29 PM UTC

   All delayed webhooks have been processed and the incident is resolved.

Read the full incident report →

Started Jul 02, 2026, 01:51 AM UTC· resolved Jul 02, 2026, 02:43 AM UTC

1. identified Jul 02, 2026, 01:51 AM UTC

   We are currently experiencing a technical issue affecting our core banking system. Real time instant payments are continuing to process as normal but balance updates in our online portal may be delayed or not reflect recent activity. FX bookings are temporarily unavailable. We are actively working to remediate this issue.

2. resolved Jul 02, 2026, 02:43 AM UTC

   A fix has been implemented, and the incident is resolved. We will continue to monitor the situation. Clients will gradually see balances updating for pending transactions.

Read the full incident report →

Started May 28, 2026, 06:57 AM UTC· resolved May 28, 2026, 08:57 AM UTC

1. identified May 28, 2026, 06:57 AM UTC

   We are aware of an issue that is impacting some client retrieving Account Information via Banking Circle Connect. We have identified the issue and are currently working on a fix.

2. identified May 28, 2026, 08:00 AM UTC

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

3. resolved May 28, 2026, 08:57 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 20, 2026, 05:20 AM UTC· resolved May 20, 2026, 06:01 AM UTC

1. investigating May 20, 2026, 05:20 AM UTC

   We are aware of an incident currently affecting payment bookings within the BC system. Payment processing is unaffected; however, there is currently a delay between payment receipt on inbound transactions and processing on outbound transactions, with the account balance updating. Rest assured that we are actively working to remediate this and will provide updates in due course.

2. monitoring May 20, 2026, 05:41 AM UTC

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

3. resolved May 20, 2026, 06:01 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 19, 2026, 10:07 AM UTC· resolved May 20, 2026, 10:37 AM UTC

1. identified May 19, 2026, 10:07 AM UTC

   We have identified the issue and we are working on a fix.

2. identified May 19, 2026, 11:03 AM UTC

   There is an ongoing scheme-wide incident impacting the processing of SEPA Instant Payments. Banking Circle is experiencing banks within the scheme are offline due to the incident. Payments to the counterparties who are offline remain in a pending processing state until the incident is resolved. Banking Circle will update the status page of any new developments

3. identified May 19, 2026, 01:24 PM UTC

   Banking Circle is still experiencing some banks within the scheme are offline due to the incident. Payments to the counterparties who are offline remain in a pending processing state until the incident is resolved. Banking Circle continues to monitor the situation and will update the status page in case of any further developments.

4. identified May 19, 2026, 06:40 PM UTC

   We are continuously seeing some banks coming back online and accepting payments. We are aware there are still delays in the scheme due to this issue and not all banks are online as of yet. We have experienced some rejections due to transactions exhausting the amount of retry attempts to the banks that are currently offline. Clients will be able to see the rejected payments.

5. identified May 20, 2026, 05:34 AM UTC

   Banking Circle has identified a small volume of Payments still in pending processing state while a limited numbers of banks remains offline. We expect the scheme to be fully operational later in the day.

6. resolved May 20, 2026, 10:37 AM UTC

   Banking Circle has observed a significant improvement, with the majority of previously affected banks now back online. Based on the current status, this external incident is considered resolved.

Read the full incident report →

Started May 12, 2026, 11:00 AM UTC· resolved May 12, 2026, 12:58 PM UTC

1. investigating May 12, 2026, 11:00 AM UTC

   We are investigating an issues that is resulting in Reporting & Balance updating delays. We are working on a fix and further updates will follow.

2. identified May 12, 2026, 11:09 AM UTC

   The issue has been identified and we are working on the fix.

3. monitoring May 12, 2026, 11:39 AM UTC

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

4. monitoring May 12, 2026, 12:29 PM UTC

   We are continuing to monitor for any further issues.

5. resolved May 12, 2026, 12:58 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 02, 2026, 02:17 PM UTC· resolved Apr 02, 2026, 03:59 PM UTC

1. investigating Apr 02, 2026, 02:17 PM UTC

   We’re aware of a problem impacting WebHook delivery for some clients and are looking into it.

2. identified Apr 02, 2026, 02:36 PM UTC

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

3. resolved Apr 02, 2026, 03:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 07, 2026, 04:19 PM UTC· resolved Mar 07, 2026, 05:05 PM UTC

1. investigating Mar 07, 2026, 04:19 PM UTC

   We are currently investigating a service degradation affecting parts of BC Connect. At this time: Core payment and transaction processing remains operational Some clients may experience issues with authorization‑dependent functions Specifically, a limited number of clients may be unable to perform token minting or redemption actions The issue appears related to network/DNS resolution affecting authorization services, and our technical teams are actively investigating together with platform and network specialists. We are continuing to monitor the situation closely and will provide further updates as soon as more information is available..

2. resolved Mar 07, 2026, 05:05 PM UTC

   The service degradation affecting authorization and API access for some BC Connect clients has been resolved. What happened: The issue was caused by an external DNS resolution problem impacting bankingcircleconnect.com, which led to intermittent failures when obtaining authorization tokens. This resulted in partial and client‑specific impact across some API integrations. Current status: DNS resolution has been restored Authorization token retrieval is functioning normally Core payment, FX, and reporting services are operating as expected Monitoring confirms service stability We will continue to monitor closely to ensure full stability. Thank you for your patience.

Read the full incident report →

Started Feb 19, 2026, 03:16 PM UTC· resolved Feb 19, 2026, 03:59 PM UTC

1. investigating Feb 19, 2026, 03:16 PM UTC

   We are experiencing an issue impacting Faster Payment processing for both inbound and outbound. We are investigating the issue and will keep you updated.

2. monitoring Feb 19, 2026, 03:58 PM UTC

   The issue has been identified and successfully resolved. We are actively monitoring the situation to ensure that faster payment processing has resumed to normal operation.

3. resolved Feb 19, 2026, 03:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 15, 2025, 08:46 PM UTC· resolved Dec 15, 2025, 10:51 PM UTC

1. investigating Dec 15, 2025, 08:46 PM UTC

   Please be advised that Danmarks Nationalbank has reported issues affecting the DKK payment schemes. As a result, delays in the processing of DKK payments may occur. This is a sector‑wide incident impacting most Danish banks. Banking Circle's infrastructure is not directly affected, and the delays have been caused by external factors. We are actively monitoring the situation and will inform you as soon as it has been resolved.

2. resolved Dec 15, 2025, 10:51 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 29, 2025, 07:27 AM UTC· resolved Sep 29, 2025, 10:56 AM UTC

1. investigating Sep 29, 2025, 07:27 AM UTC

   We are aware of an issue impacting statuses and updates of payments. We are currently investigating the data being out of sync.

2. investigating Sep 29, 2025, 07:54 AM UTC

   Investigations are ongoing and Banking Circle are working for a resolution. Updates will continue.

3. identified Sep 29, 2025, 09:20 AM UTC

   A fix has been implemented which has restored the syncing of new transactions. However, we are still working on the backlog of transactions impacted prior to the fix. We will keep you updated on the backlog.

4. monitoring Sep 29, 2025, 10:06 AM UTC

   A fix has been deployed for the backlog. Clients should start seeing their transactions synchronizing shortly. We will confirm once all transactions are cleared.

5. resolved Sep 29, 2025, 10:56 AM UTC

   This Incident has been resolved. All transactions are now cleared.

Read the full incident report →

Started Sep 03, 2025, 11:52 AM UTC· resolved Sep 03, 2025, 02:00 PM UTC

1. investigating Sep 03, 2025, 11:52 AM UTC

   We are aware of an issue with Inbound Payments not being applied to clients accounts. We are currently investigating the problem internally.

2. identified Sep 03, 2025, 12:08 PM UTC

   We believe that we have identified the underlying cause of the problem and are currently implementing a fix to mitigate the situation.

3. identified Sep 03, 2025, 01:32 PM UTC

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

4. monitoring Sep 03, 2025, 01:34 PM UTC

   We have implemented a corrective measure that has reduced the number of payments not appearing on client accounts. Efforts are ongoing to ensure that all affected transactions are fully reflected.

5. resolved Sep 03, 2025, 02:00 PM UTC

   We have now cleared the backlog of transactions. This incident has been fully resolved and there is no impact on clients accounts.

Read the full incident report →

Started Sep 01, 2025, 11:00 AM UTC· resolved Sep 01, 2025, 11:35 AM UTC

1. investigating Sep 01, 2025, 11:00 AM UTC

   We are aware of some delays in transactions being synced to clients accounts. Transactions are processing however the sync towards clients accounts and balances may be impacted. Investigation is ongoing and we are working on a resolution.

2. resolved Sep 01, 2025, 11:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 20, 2025, 01:38 AM UTC· resolved Jul 20, 2025, 04:23 PM UTC

1. investigating Jul 20, 2025, 01:38 AM UTC

   We are currently encountering an issue affecting both incoming and outgoing FPS. We are investigating the issue and will provide updates as soon as new information is available.

2. monitoring Jul 20, 2025, 07:41 AM UTC

   Operations have resumed, and we are diligently monitoring the situation.

3. identified Jul 20, 2025, 11:15 AM UTC

   Incoming Faster Payments are being delayed. The issue is being investigated with our service provider.

4. investigating Jul 20, 2025, 11:30 AM UTC

   Incoming and Outgoing Faster Payments are being delayed. The issue is currently being investigated with our service provider. We will share more updates once available.

5. resolved Jul 20, 2025, 04:23 PM UTC

   The issue is resolved; payment processing is back to normal.

Read the full incident report →

Started May 22, 2025, 06:59 AM UTC· resolved May 22, 2025, 07:34 AM UTC

1. identified May 22, 2025, 06:59 AM UTC

   We are investigating an issue that is impacting balances where clients are seeing there payment in a Missing Funding state. We are working on a solution and will update

2. monitoring May 22, 2025, 07:24 AM UTC

   A Fix has now been implemented and Missing Funding status should be resolved. We will continue to monitor the issue.

3. resolved May 22, 2025, 07:34 AM UTC

   This incident has been resolved.

Read the full incident report →

Started May 16, 2025, 07:54 AM UTC· resolved May 16, 2025, 10:22 AM UTC

1. identified May 16, 2025, 07:54 AM UTC

   We have identified an issue with clients reporting. Payments are processing normally, however reporting is impacted, with reports being stuck in Queued state.

2. identified May 16, 2025, 08:44 AM UTC

   Banking Circle are continuing the investigations into the issue and are working on a solution for the incident. Updates will be provided.

3. monitoring May 16, 2025, 09:58 AM UTC

   We have implemented a fix and are seeing reports are now being delivered as expected. Banking Circle will continue to monitor.

4. resolved May 16, 2025, 10:22 AM UTC

   Following on from a fix implemented and monitoring of this, Client have confirmed the reporting is now back to BAU.

Read the full incident report →

Started Apr 21, 2025, 08:57 AM UTC· resolved Apr 21, 2025, 12:03 PM UTC

1. identified Apr 21, 2025, 08:57 AM UTC

   Payments are processing normally, however reporting is experiencing issues which are causing delays.

2. monitoring Apr 21, 2025, 10:31 AM UTC

   We have implemented a fix to remediate the issue and are currently monitoring the situation.

3. resolved Apr 21, 2025, 12:03 PM UTC

   The issue is resolved.

Read the full incident report →

Started Apr 05, 2025, 07:34 AM UTC· resolved Apr 05, 2025, 05:39 PM UTC

1. investigating Apr 05, 2025, 07:34 AM UTC

   We are currently encountering an issue affecting both payment processing and reporting. We are actively investigating the matter and we will keep our clients informed of any updates.

2. monitoring Apr 05, 2025, 08:16 AM UTC

   The issue has been identified and a fix implemented. Payment processing operations have resumed. We are actively monitoring the situation to ensure a full return to normal operations.

3. monitoring Apr 05, 2025, 01:48 PM UTC

   Fixes have been implemented, and payment processing operations have resumed. However, we are still experiencing some delays in processing affecting reporting updates. The situation will be actively monitored until we return to normal operations.

4. monitoring Apr 05, 2025, 02:44 PM UTC

   Some delays may still occur. Clients may experience delays in bookings and report updates. The situation is expected to be rectified within 2 hours. We are monitoring the situation continuously and will provide updates.

5. monitoring Apr 05, 2025, 04:14 PM UTC

   Confirmations indicate that payments and reporting have returned to normal for our Clients. The issue is considered resolved, but we will continue to monitor the situation closely.

6. monitoring Apr 05, 2025, 04:16 PM UTC

   Confirmations indicate that payments and reporting have returned to normal for our Clients. The issue is considered resolved, but we will continue to monitor the situation closely.

7. resolved Apr 05, 2025, 05:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 01, 2025, 09:14 AM UTC· resolved Apr 01, 2025, 01:10 PM UTC

1. investigating Apr 01, 2025, 09:14 AM UTC

   We are investigating an issue regarding FX and Payment Processing. Payment may be showing as Pending Processing. We will provide updates as soon as new information is available.

2. investigating Apr 01, 2025, 09:23 AM UTC

   We are continuing to investigate this issue.

3. identified Apr 01, 2025, 09:36 AM UTC

   We are facing connectivity issues with an External Provider. They are aware of the issues. Currently all payments will be held in a Pending Processing Status. FX is also impacted. Our provider is working on a resolution, and we will update in due course.

4. monitoring Apr 01, 2025, 10:27 AM UTC

   The issue has now been resolved and we are now processing transactions. Banking Circle will continue to monitor this.

5. identified Apr 01, 2025, 12:08 PM UTC

   Whilst payments are processing, we are aware of some delays in Reporting and Status updates showing on BC UI. This is currently being worked on and Banking Circle are working on a fix to show the correct status and deliver reporting/notifications.

6. monitoring Apr 01, 2025, 12:50 PM UTC

   Reporting, notifications and balances should now be updating for clients. BC will continue to monitor.

7. resolved Apr 01, 2025, 01:10 PM UTC

   This incident has been resolved.

Read the full incident report →