Fidel incident
Elevated Duplicate Authorizations via Mastercard Network
Fidel experienced a minor incident on March 19, 2026, lasting 7d 23h. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Mar 19, 2026, 06:20 PM UTC
We are investigating an issue regarding an elevated volume of duplicate authorizations originating exclusively from the Mastercard network. While the influx of duplicate authorizations has ceased, we are keeping this incident open while we await further information. Impact: Between May 19th (18:20 UTC) and May 20th (23:22 UTC), several clients experienced an elevated number of duplicate authorization events for Mastercard transactions. Actions Taken: We have formally escalated the issue to Mastercard to determine the root cause of the duplicate events on their network. Our engineering team is currently monitoring our systems to evaluate if the behavior recurs.
- resolved Mar 27, 2026, 05:33 PM UTC
Update: Mastercard has concluded their investigation into the duplicate authorization events and provided a final update. The root cause was identified as a gateway error on their network, which incorrectly generated duplicate notification messages for single authorizations. Crucially, because these duplicate messages were sent with the exact same unique identifiers (which normally determine the uniqueness of a transaction), they bypassed standard deduplication checks. This is why the duplicate events were surfaced to our clients. Mastercard has confirmed the following key points: No Duplicate Transactions: This issue was limited strictly to message duplication. Actual authorization records, clearing files, and transactions were not duplicated. Mastercard considers this a one-time occurrence, and the issue has not recurred since March 20th. Normal service is fully restored, and we are marking this incident as resolved.