Ingenico Outage History

Started Jun 02, 2026, 08:08 AM UTC· resolved Jul 08, 2026, 09:03 AM UTC

1. identified Jun 02, 2026, 08:08 AM UTC

   Our systems have detected that the La Poste France transactions starting from 01/06/2026 have not been settled correctly. Due to this, the funds associated with the transactions concerned will be credited to your account later than usual. A dedicated team has been deployed to investigate the situation as a matter of urgency. We will update you as soon as more information becomes available. We regret any potential inconvenience and appreciate your understanding and patience.

2. monitoring Jun 04, 2026, 02:06 PM UTC

   As we have already informed you, our systems have detected that the La Poste France transaction settlement file dated from 02/06/2026 (with transactions dated from 01/06/2026) has been rejected by the acquirer. We are happy to confirm that most of the transactions were successfully resubmitted to the acquirer today (04/06/2026). The proceeds of the transactions involved will be credited to your account 2 days later than usual. The limited number of remaining transactions will be reposted and processed by the acquirer in the following days. We apologise for any inconvenience caused.

3. monitoring Jun 10, 2026, 09:18 AM UTC

   As we have already informed you, our systems have detected that the La Poste France transaction settlement file dated from 02/06/2026 (with transactions dated from 01/06/2026) has been rejected by the acquirer. Most of the transactions were successfully resubmitted to the acquirer on Thursday, 04/06/2026. However, some of the resubmitted transactions might have been processed twice. We are working closely with the acquirer to resolve it, so that all double settlements are adjusted and corrected accordingly. Thank you for your patience and we apologise for any inconvenience caused.

4. resolved Jul 08, 2026, 09:03 AM UTC

   This is an update regarding the issue with delayed settlements for La Poste France transactions. We confirm that the issue has been fully resolved. All the affected transactions have been successfully resubmitted and processed.

Read the full incident report →

Started Jun 01, 2026, 11:09 AM UTC· resolved Jun 01, 2026, 12:07 PM UTC

1. identified Jun 01, 2026, 11:09 AM UTC

   We would like to inform you about an ongoing issue with BNP transaction processing as from 12:55 CEST on 01/06/2026. We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. resolved Jun 01, 2026, 12:07 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via BNP on 01/06/2026 between 12:45 and 13:50 CEST. We confirm that as of 13:50 CEST on 01/06/2026, normal service has been resumed and your customers will now be able to make payments normally. We also confirm that the issue has an external responsibility (independent of Worldline).

Read the full incident report →

Started May 21, 2026, 07:10 AM UTC· resolved May 21, 2026, 12:35 PM UTC

1. resolved May 21, 2026, 01:01 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via Concardis acquirer on 21/05/2026 between 09:10 and 14:35 CEST. We confirm that as of 14:35 CEST on 21/05/2026, normal service has been resumed and your customers will now be able to make payments normally. We also confirm that the issue has an external responsibility (independent of Worldline).

Read the full incident report →

Started May 04, 2026, 10:35 AM UTC· resolved May 04, 2026, 10:50 AM UTC

1. resolved May 04, 2026, 11:53 AM UTC

   We would like to inform you that your customers may have experienced time-outs or higher than expected latency for processing transactions between 12:35 and 12:50 CEST (04/05/2026). All transactions that were not affected by a time-out have been successfully processed and have the correct statuses. The service has been restored to normal operating conditions. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

Read the full incident report →

Started Apr 14, 2026, 01:42 PM UTC· resolved Apr 14, 2026, 02:00 PM UTC

1. resolved Apr 14, 2026, 02:19 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via Worldpay on 14/04/2026 between 15:42 and 16:00 CEST. We confirm that as of 16:00 CEST on 14/04/2026, normal service has been resumed and your customers will now be able to make payments normally. We also confirm that the issue has an external responsibility (independent of Worldline).

Read the full incident report →

Started Mar 29, 2026, 03:02 AM UTC· resolved Mar 29, 2026, 03:57 AM UTC

1. identified Mar 29, 2026, 03:02 AM UTC

   We would like to inform you about an ongoing issue with BCC and Banksys transaction processing as from 03:00 CEST on 29/03/2026. We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. resolved Mar 29, 2026, 03:57 AM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via BCC and Banksys on 29/03/2026 between 03:00 and 05:00 CEST. We confirm that as of 05:00 CEST on 29/03/2026, normal service has been resumed and your customers will now be able to make payments normally. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Mar 25, 2026, 02:27 PM UTC· resolved Mar 25, 2026, 02:40 PM UTC

1. resolved Mar 25, 2026, 03:10 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via iDeal on 25/03/2026 between 15:27 and 15:40 CET. We confirm that as of 15:40 CET on 25/03/2026, normal service has been resumed and your customers will now be able to make payments normally. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Mar 24, 2026, 09:41 AM UTC· resolved Mar 24, 2026, 01:32 PM UTC

1. identified Mar 24, 2026, 09:41 AM UTC

   We would like to inform you about an ongoing issue with Maestro and ApplePay transaction processing as from 05:00 CEST Today, (24/03/2026). We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. resolved Mar 24, 2026, 01:32 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via Maestro & ApplePay on 24/03/2026 between 02:32 and 13:30 CET. We confirm that as of 13:30 CET on 24/03/2026, normal service has been resumed and your customers will now be able to make payments normally. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Mar 05, 2026, 07:26 AM UTC· resolved Mar 05, 2026, 01:31 PM UTC

1. identified Mar 05, 2026, 07:26 AM UTC

   We would like to inform you about an ongoing issue with Worldline Blue transaction processing as from 03:46 CET on 05/03/2026. We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. identified Mar 05, 2026, 08:19 AM UTC

   Please note that the service interruption with the processing of Bancontact and Worldline Acquiring transactions is still ongoing and new impact waves have been observed. Worldline technical experts keep investigating the situation with the highest priority. Thank you for your patience and we sincerely apologise for any potential inconvenience. Update will follow upon outcome of our further investigation.

3. identified Mar 05, 2026, 08:20 AM UTC

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

4. monitoring Mar 05, 2026, 10:26 AM UTC

   We would like to inform you that a fix has been implemented, and we are actively monitoring the situation to ensure full resolution. An update will be provided shortly. We apologise for any inconvenience caused.

5. resolved Mar 05, 2026, 01:31 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make Bancontact payments online via Worldline Acquiring on 05/03/2026 between 03:46 and 09:45 CET. We confirm that a workaround has been implemented by Worldline acquiring team and as of 09:45 CET on 05/03/2026, normal service has been resumed. Your customers are now able to make payments normally. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Mar 04, 2026, 11:00 PM UTC· resolved Mar 06, 2026, 07:00 AM UTC

1. investigating Mar 06, 2026, 01:15 AM UTC

   Please be informed that your customers might currently experience higher than expected latency in the processing of transactions and, potentially, a number of time-outs since 23:10 CET. Our dedicated teams are working hard on this with the aim to restore the activity to normal operating conditions. An update will be provided shortly. We sincerely regret any potential inconvenience and appreciate your understanding and patience.

2. resolved Mar 06, 2026, 07:00 AM UTC

   We would like to inform you that your customers may have experienced time-outs or higher than expected latency for processing transactions between 23:10 05/03/2026 and 03:35 CET 06/03/2026. All transactions that were not affected by a time-out have been successfully processed and have the correct statuses. The service has been restored to normal operating conditions. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

Read the full incident report →

Started Feb 25, 2026, 02:10 PM UTC· resolved Feb 25, 2026, 06:31 PM UTC

1. identified Feb 25, 2026, 02:10 PM UTC

   Please be informed that your customers might currently experience higher than expected latency in the processing of transactions and, potentially, a number of time-outs since 25/02/2026 at 14:50 CET. Our dedicated teams are working hard on this with the aim to restore the activity to normal operating conditions. An update will be provided shortly. We sincerely regret any potential inconvenience and appreciate your understanding and patience.

2. identified Feb 25, 2026, 03:37 PM UTC

   Please be reminded that your customers might still experience higher than expected latency in the processing of transactions and, potentially, a number of time-outs since 25/02/2026 at 14:50 CET. We would like to assure you that the investigation persists. Our dedicated teams are working hard on this with the aim to restore the activity to normal operating conditions as soon as possible. You will be updated on a regular basis. We sincerely regret any potential inconvenience and appreciate your understanding and patience.

3. identified Feb 25, 2026, 05:07 PM UTC

   We would like to inform you that the perturbation affecting the payment processing on the Worldline (WLOP) platform is still ongoing. Our dedicated team of experts is actively working with the utmost priority to restore the activity to normal operating conditions. We sincerely regret any potential inconvenience and appreciate your understanding and patience.

4. resolved Feb 25, 2026, 06:31 PM UTC

   Please be informed that your customers may have experienced perturbations performing transactions using the Worldline (WLOP) platform as from 14:50 CET on 25 Feb 2026. We are pleased to announce that the system returned to normal operating conditions at 18:08 CET. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

Read the full incident report →

Started Feb 21, 2026, 08:47 AM UTC· resolved Feb 21, 2026, 03:45 PM UTC

1. identified Feb 21, 2026, 08:04 AM UTC

   We would like to inform you about an ongoing issue with CB transaction processing as from 7:20 CET on 21-02-2026. We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. identified Feb 21, 2026, 08:47 AM UTC

   We have informed you earlier about a perturbation on our Worldline (WLOP) platform on 21-02-2026 as from 7:20 CET. Following investigation by our technical experts, please be informed that the perturbation concerns the CB service only. If you do not use this specific service, please note that this issue has no impact on your business and you can ignore these communications. You will not receive further notifications regarding this issue. However, if your business benefits from the CB service, we will provide you with more updates shortly. We also confirm that the issue has an external responsibility (independent of Worldline).

3. monitoring Feb 21, 2026, 08:52 AM UTC

   We have informed you earlier about a perturbation on our Worldline (WLOP) platform on 21-02-2026 as from 7:20 CET. Following investigation by our technical experts, please be informed that the perturbation concerns the CB service only. If you do not use this specific service, please note that this issue has no impact on your business and you can ignore these communications. You will not receive further notifications regarding this issue. However, if your business benefits from the CB service, we will provide you with more updates shortly. We also confirm that the issue has an external responsibility (independent of Worldline).

4. monitoring Feb 21, 2026, 09:53 AM UTC

   We have informed you earlier about a perturbation on our Worldline (WLOP) platform on 21-02-2026 as from 7:20 CET. Following investigation by our technical experts, please be informed that the perturbation concerns the CB service only. If you do not use this specific service, please note that this issue has no impact on your business and you can ignore these communications. You will not receive further notifications regarding this issue. However, if your business benefits from the CB service, we will provide you with more updates shortly. We also confirm that the issue has an external responsibility (independent of Worldline).

5. monitoring Feb 21, 2026, 10:29 AM UTC

   We have informed you earlier about a perturbation on our Worldline (WLOP) platform on 21-02-2026 as from 7:20 CET. Following investigation by our technical experts, please be informed that the perturbation concerns the CB service only. If you do not use this specific service, please note that this issue has no impact on your business and you can ignore these communications. You will not receive further notifications regarding this issue. However, if your business benefits from the CB service, we will provide you with more updates shortly. We also confirm that the issue has an external responsibility (independent of Worldline).

6. monitoring Feb 21, 2026, 11:22 AM UTC

   Please be informed that the perturbation impacting CB 3-D Secure Authentication is still ongoing. We are in contact with the responsible external party. An update will be provided shortly. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

7. monitoring Feb 21, 2026, 12:42 PM UTC

   Please be informed that the perturbation impacting CB 3-D Secure Authentication is still ongoing. We are in contact with the responsible external party. An update will be provided shortly. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

8. monitoring Feb 21, 2026, 01:29 PM UTC

   Please be informed that the perturbation impacting CB 3-D Secure Authentication is still ongoing. We are in contact with the responsible external party. An update will be provided shortly. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

9. monitoring Feb 21, 2026, 02:37 PM UTC

   Please be informed that the perturbation impacting CB 3-D Secure Authentication is still ongoing. We are in contact with the responsible external party. An update will be provided shortly. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

10. resolved Feb 21, 2026, 03:45 PM UTC

    Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via CB on 21-02-2026 between 07:20 and 16:06 CET. We confirm that as of 16:06 CET on 21-02-2026, normal service has been resumed and your customers will now be able to make payments normally. We also confirm that the issue has an external responsibility (independent of Worldline). We regret the situation and any potential inconvenience.

Read the full incident report →

Started Feb 05, 2026, 03:08 PM UTC· resolved Feb 05, 2026, 03:15 PM UTC

1. identified Feb 05, 2026, 03:08 PM UTC

   We would like to inform you about an ongoing issue with Bambora transaction processing as from 15:26 CET on 05/02/2025. We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. resolved Feb 05, 2026, 03:15 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via Bambora on 05/02/2026 between 15:24 and 15:55 CET. We confirm that as of 15:55 CET on 05/02/2026, normal service has been resumed and your customers will now be able to make payments normally. We also confirm that the issue has an external responsibility (independent of Worldline).

Read the full incident report →

Started Feb 05, 2026, 09:35 AM UTC· resolved Feb 06, 2026, 09:58 AM UTC

1. investigating Feb 05, 2026, 09:35 AM UTC

   Please be informed about an ongoing issue in our production environment causing duplicate refunds for the same transaction. Our initial investigation indicates this issue started before the end of November 2025. We are actively investigating and will provide updates as soon as possible. We apologise for any inconvenience caused.

2. resolved Feb 06, 2026, 09:58 AM UTC

   We informed you yesterday about a perturbation on our platform causing duplicate refunds for the same transaction. Following thorough investigation performed by our technical experts, we wish to inform you that the perturbation has not affected your business and you can ignore these communications. You will not receive further notifications regarding this event. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

Read the full incident report →

Started Jan 28, 2026, 10:34 AM UTC· resolved Jan 28, 2026, 11:20 AM UTC

1. investigating Jan 28, 2026, 10:34 AM UTC

   Please be informed that some of your customers might currently experience higher than expected latency in the processing of transactions and, potentially, a number of time-outs since Today, (28/01/2026) 09:57 CET. Our dedicated teams are working hard on this with the aim to restore the activity to normal operating conditions. An update will be provided shortly. We sincerely regret any potential inconvenience and appreciate your understanding and patience.

2. resolved Jan 28, 2026, 11:20 AM UTC

   We would like to inform you that some of your customers may have experienced time-outs or higher than expected latency for processing transactions Today, (28/01/2026) between 09:55 and 11:13 CET. All transactions that were not affected by a time-out have been successfully processed and have the correct statuses. The service has been restored to normal operating conditions. We sincerely regret any potential inconvenience and appreciate your understanding of the matter.

Read the full incident report →

Started Jan 26, 2026, 08:21 AM UTC· resolved Feb 11, 2026, 09:22 AM UTC

1. identified Jan 26, 2026, 08:21 AM UTC

   Our systems have detected that the PostFinance transactions starting from 23/01/2026, 17:00 CET have not been settled correctly. Due to this, the funds associated with the transactions concerned will be credited to your account later than usual. A dedicated team has been deployed to investigate the situation as a matter of urgency. We will update you as soon as more information becomes available. We regret any potential inconvenience and appreciate your understanding and patience.

2. resolved Feb 11, 2026, 09:22 AM UTC

   Our systems have detected that the PostFinance transaction settlement file dated from 23/01/2026, 17:00 CET has been rejected. We confirm that the settlement has been successfully resubmitted to the acquirer on 11/02/2026. The proceeds of the transactions involved will be credited to your account later than usual. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Jan 21, 2026, 03:47 PM UTC· resolved Jan 22, 2026, 10:44 AM UTC

1. identified Jan 21, 2026, 03:47 PM UTC

   Our systems have detected that the Collect transactions starting from 21/01/2026, 16:00 CET have not been settled correctly. Due to this, the funds associated with the transactions concerned will be credited to your account later than usual. A dedicated team has been deployed to investigate the situation as a matter of urgency. We will update you as soon as more information becomes available. We regret any potential inconvenience and appreciate your understanding and patience.

2. resolved Jan 22, 2026, 10:44 AM UTC

   Our systems have detected that the Collect transaction settlement file dated from 21/01/2026, 16:00 CET has been rejected. We confirm that the settlement has been successfully resubmitted to the acquirer Today, (22/01/2026). The proceeds of the transactions involved will be credited to your account 1 day later than usual. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Jan 21, 2026, 08:18 AM UTC· resolved Feb 03, 2026, 08:54 AM UTC

1. identified Jan 21, 2026, 08:18 AM UTC

   Our systems have detected that transactions starting from 20/01/2026, 13:37 CET have not been settled correctly. Due to this, the funds associated with the transactions concerned will be credited to your account later than usual. A dedicated team has been deployed to investigate the situation as a matter of urgency. We will update you as soon as more information becomes available. We regret any potential inconvenience and appreciate your understanding and patience.

2. identified Jan 23, 2026, 03:53 PM UTC

   UPDATE As communicated before, our systems have detected that transactions starting from 20/01/2026, 13:37 CET have not been settled correctly. This is our confirmation to you that this situation is still ongoing. As a result, the funds associated with the transactions concerned will be credited to your account later than usually. A dedicated team has been deployed to investigate the case as a matter of urgency and the investigation persists. We will update you again as soon as more information becomes available. We regret any potential inconvenience and appreciate your understanding and patience.

3. resolved Feb 03, 2026, 08:54 AM UTC

   Please be informed that some transactions appeared successful to merchants but were later rejected during settlement. This event took place between 20/01/2026 13:37 and 02/02/2026 10:04 CET. We confirm that the issue has been fixed and transactions have been reprocessed. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Dec 09, 2025, 05:52 PM UTC· resolved Dec 09, 2025, 08:33 PM UTC

1. identified Dec 09, 2025, 05:52 PM UTC

   We would like to inform you about an ongoing issue with BCMC transaction processing as from 13:06 CET on 09/12/2025. We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. resolved Dec 09, 2025, 08:33 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via Bancontact on 09/12/2025 between 13:06 and 20:53 CET. We confirm that as of 20:53 CET on 09/12/2025, normal service has been resumed and your customers will now be able to make payments normally. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Nov 24, 2025, 10:03 AM UTC· resolved Nov 24, 2025, 10:03 AM UTC

1. resolved Nov 24, 2025, 10:03 AM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via Bancontact Yesterday, (23/11/2025) between 19:29 and 22:33 CET. We confirm that as of 22:33 CET on 23/11/2025, normal service has been resumed and your customers will now be able to make payments normally. We regret the situation and any potential inconvenience.

Read the full incident report →

Started Nov 18, 2025, 12:34 PM UTC· resolved Nov 18, 2025, 03:12 PM UTC

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

   We would like to inform you about an ongoing issue with PayPal transaction processing as from 12:29 CET on 18/11/2025. We are investigating the situation with the highest priority. An update will be provided shortly. We appreciate your understanding of the matter.

2. identified Nov 18, 2025, 03:08 PM UTC

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

3. resolved Nov 18, 2025, 03:12 PM UTC

   Please be informed that due to a technical issue, some of your customers might have been unable to make payments online via PayPal on 18/11/2025 between 12:29 and 13:10 CET. We confirm that as of 13:10 CET on 18/11/2025, normal service has been resumed and your customers will now be able to make payments normally. We also confirm that the issue has an external responsibility (independent of Worldline).

Read the full incident report →

Started Oct 17, 2025, 12:09 PM UTC· resolved Oct 17, 2025, 04:08 PM UTC

1. identified Oct 17, 2025, 12:09 PM UTC

   We would like to inform you about an ongoing technical issue impacting 3-D Secure authentication as from 14:10 CEST (from 16/10/2025). The issue has reoccurred after the temporary resolution. Many different acquirers and payment methods are impacted. This issue results in a number of transactions receiving a status 0 (Incomplete/invalid) or status 2 (Authorisation declined) due to the impossibility of performing a 3-D Secure check. A dedicated team has been deployed to investigate the situation as a matter of urgency. An update will be provided shortly. We appreciate your understanding of the matter.

2. resolved Oct 17, 2025, 04:08 PM UTC

   Please be informed that a perturbation impacting 3-D Secure authentication occurred between 16/10/2025 14:10 CEST and 17/10/2025 12:54 CEST. As a result, during this time frame, some of your customers may have received an error message and their transaction may have ended in a status 0 (incomplete/invalid). Depending on your account configuration: - your customers may have returned to the previous page to reattempt the payment with a different payment method or - the transaction may have been processed without 3-D Secure.

Read the full incident report →