[INCIDENT] FLOA Partial Funding - accounting files
Identified - Madam, Sir,

We encountered a partial malfunction in the creation of accounting files.
We confirm that no incidents have been reported on transmission of funds.

This incident does not impact your production.

The missing accounting files will be transmitted along with today's.

We apologize for the inconvenience caused.

Regards,
The Floa Pay Support Team
________________________________________________________

Madame, Monsieur,

Nous avons rencontré un dysfonctionnement partiel dans lé chaîne de constitution des fichiers de remises.
Nous vous confirmons qu'aucun incident n'est à déclaré sur la transmission des fonds.

Cet incident n’a pas d’impact sur votre production.

Les justificatifs comptables manquants seront transmis avec ceux du jour.

Nous vous prions de bien vouloir nous excuser pour la gêne occasionnée.

Cordialement,
L'équipe Support Floa Pay
Oct 06, 2026 - 12:09 CEST

About This Site

Rappel : Changement des IP sortantes Floa à partir du 4 mai 2026 pour les environnements de hors prod et à partir du 1er juin 2026 pour l'environnement de Production.

Reminder : Floa outgoing IP addresses will change. Starting May 4, 2026 for non‑production environments, and starting June 1, 2026 for production environment.

Uptime over the past 90 days. View historical uptime.
CB 1X/3X/4X Operational
CB 10X Operational
CNX Operational
CIRCLE PAY Operational
Reconciliation Report Partial Outage
Funding Operational
Partner Portal Operational
Integration Environment Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Oct 6, 2026

Unresolved incident: [INCIDENT] FLOA Partial Funding - accounting files.

Oct 5, 2026

No incidents reported.

Oct 4, 2026

No incidents reported.

Oct 3, 2026

No incidents reported.

Oct 2, 2026

No incidents reported.

Oct 1, 2026

[RESOLVED INCIDENT] Information on a past incident : Payment Service Disruption – September 30, 2026
Resolved - Dear Madam, Sir,

On September 30, 2026, an incident impacted part of the FLOA payment journey.

Incident Duration :

3:00 PM to 9:00 PM (CET)

Impact :
Approximately 3.4% of requests were affected.
Some applications experienced issues during the payment validation step, resulting in technical errors on the payment/imprint/complete process.
In some cases, payment journeys remained in a prolonged loading state or appeared to be blocked.
Several applications were eventually processed successfully and automatically validated once the incident was resolved.
Duplicate applications may have been created when merchants assumed that the initial application had failed and subsequently submitted a new one.

We sincerely apologize for the inconvenience caused.

Kind regards,
The Control Tower FLOA Team
_______________________________

Bonjour,

Le 30/09 un incident a affecté une partie du parcours de paiement FLOA.

Durée incident :
Entre 15:00 et 21:00

Impacts :
Environ 3.4% des appels sont impactés.
Certains dossiers ont rencontré un blocage lors de l'étape de validation du paiement avec des erreurs techniques sur le traitement payment/imprint/complete.
Certains parcours de paiement sont restés en chargement prolongé ou en apparence bloqués, plusieurs dossiers ont finalement poursuivi leur traitement et ont été validés automatiquement après résolution de l'incident.
Un second dossier pensant que le premier n'avait pas abouti a pu être créé, générant ainsi des doublons

Nous vous prions de nous excuser pour la gêne occasionnée.

Cordialement,
L'équipe Control Tower FLOA
Oct 1, 17:18 CEST

Sep 30, 2026

No incidents reported.

Sep 29, 2026

No incidents reported.

Sep 28, 2026

No incidents reported.

Sep 27, 2026

No incidents reported.

Sep 26, 2026

No incidents reported.

Sep 25, 2026

No incidents reported.

Sep 24, 2026

No incidents reported.

Sep 23, 2026

No incidents reported.

Sep 22, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage