Where most complaints about this service are coming from, over the last 24 hours.
Shows where the service URL was unreachable during the detected outage periods. Percentages indicate the share of failed checks from monitoring locations in each country.
Tap what’s going wrong — one click helps thousands of others see the outage.
If the app freezes on launch or closes immediately, the first thing to check is whether you're running an outdated version. Head to the App Store or Google Play and update to the latest release. If that doesn't help, clear the app cache in your device settings, then restart your phone. A full reinstall fixes the issue in most cases.
This usually comes down to one of a few things:
Check your balance first, then confirm the limit in your profile settings. If everything looks fine, wait a few minutes and retry — brief processing delays are common.
The SMS verification code sometimes gets delayed by mobile network congestion. Wait up to two minutes before requesting a new one. If codes consistently don't arrive, check that your number is correctly registered and that your carrier isn't filtering the sender. Switching from Wi-Fi to mobile data can also resolve delivery issues.
When connecting a bank account fails, it's often because the bank's open banking interface is temporarily unavailable. Try again during off-peak hours. Also make sure your bank supports the connection method Satispay requires — some smaller institutions have limited compatibility.
A transfer that stays pending longer than expected is usually held for a routine security review. If it hasn't resolved within a few hours, check the transaction status inside the app and contact support through the in-app chat. Closing and reopening the app refreshes the status display, which sometimes shows the transfer has already completed.
Satispay relies on a stable internet connection for every action, including balance checks. On a weak signal, requests time out and the interface can freeze mid-action. Switch to a stronger Wi-Fi network or move to an area with better mobile coverage. If the issue persists on good connections, the service itself may be experiencing temporary server load — waiting 10–15 minutes usually resolves it.