Currencycloud Outage History

Currencycloud experienced an issue where approximately 10 clients received Invalid SCA (Strong Customer Authentication) errors when creating payments or logging in due to problems with authentication checks. The issue was caused by a recent service change that affected authentication request processing. The problem was resolved by rolling back the white-label service to version 0.1.655, restoring normal service behavior after 7.3 hours.

Currencycloud experienced a 16.3-hour outage affecting SEPA Instant payments that caused local EUR payments to fail, experience delays, or be rejected. The issue was caused by an industry-wide EBA incident impacting SEPA Instant (RT1) processing from an external provider. The service was fully restored once the external provider resolved the issue, though customers with previously failed payments needed to resubmit their transactions.

Currencycloud experienced delays and missing details during EUR and USD account creation in their DEMO environment for 15.8 hours. The issue affected new account provisioning processes, causing incomplete or slow account setup for users testing the platform. Teams implemented a fix to restore normal processing and continued monitoring until the incident was fully resolved.

Currencycloud experienced extended planned platform maintenance that affected their API, Payments, Conversions, Paydirect.io/Direct, Notifications, Balances, and other components. The maintenance lasted 32 minutes before being resolved. All affected services have been restored to normal operation.

Currencycloud experienced a 4.7-hour issue where local EUR payment status updates were not displaying correctly, though the actual payments continued to process and settle normally without any functional impact. The status reporting system was restored, with some additional time needed for all outstanding payments to fully reflect their correct final status due to processing volumes during the incident.

Currencycloud experienced a phone support service outage that prevented customers from reaching support by telephone for 4.5 hours. Email and in-app support channels remained operational during the incident, providing alternative contact methods for customers. The phone support service was fully restored and all support channels returned to normal operation.

Currencycloud experienced intermittent issues with Authy-based two-factor authentication that prevented some customers from logging in to the Paydirect.io / Direct service. Customers were advised to use SMS-based verification as a temporary workaround during the 5-hour incident. The Authy 2FA issue was resolved and normal login functionality was restored.

Currencycloud experienced an issue with status updates for Erste payments, where payment confirmations appeared delayed due to pending acknowledgements from their Erste network partner. While payments continued processing normally, some transactions displayed as incomplete even though they were being processed successfully. The incident was resolved after 19.4 hours once the outstanding acknowledgements were received and payment statuses were updated.

Currencycloud experienced a service degradation that prevented users from creating CAD (Canadian Dollar) virtual accounts for 9.7 hours. The company worked with their banking partner to resolve the underlying issue. The problem was successfully mitigated and all pending virtual account creations were completed.

Currencycloud experienced an issue with status updates for RON (Romanian Leu) local payments, where payments displayed as incomplete despite processing normally due to delayed acknowledgements from their network partner. The payments themselves continued to function correctly, but status confirmations were temporarily delayed for 22.1 hours. The incident was resolved after working with the network partner to receive outstanding acknowledgements and update payment statuses.