QryptoPay health monitoring
The BeAdmin cloud can monitor whether your QryptoPay server is working correctly. If the server goes down, it usually can't report that itself — but the cloud will notice: it shows the status with an incident history in your cloud account, and emails you both when there's an outage and when service is restored.
ℹ️ Why this matters
An outage on your QryptoPay server also goes unnoticed for payments: customers simply won't be able to pay, and you won't know unless you check yourself. Monitoring reports the problem almost right away — you get a chance to react before customers notice.
How it works
When you connect the option on your QryptoPay server, you choose which merchants to watch. The cloud polls the server every 5 minutes, and if any service fails, it sends a notification to your email.
Monitoring can detect the following:
- the server is unreachable;
- the panel isn't responding;
- the module can't accept or process payments;
- internal services of the QryptoPay module have failed;
- the merchant's payment page isn't working.
Monitoring registers an outage right away, but the email notification is sent only after the third failed check in a row — at an interval of 5 minutes, that's roughly 10 minutes from the first failure. This keeps monitoring from raising a false alarm over a one-off network glitch or a delay reaching your server.
A problem service is likewise considered recovered only after the second successful check in a row — another 5 minutes or so. Same principle: monitoring notifies you of recovery only once the service is genuinely back, not stuck in a loop of recovering and failing again.
Because of these delays, the status shown in your cloud account can lag slightly behind reality, and the "Check now" button in your cloud account lets you send a check manually, ahead of schedule. This is handy if you've already restored the server and don't want to wait for the next scheduled check to confirm everything's working.
If you turn monitoring off or its licence expires, the incident history isn't lost — it stays available in your cloud account. It's kept for 90 days, then deleted.
Notifications
An email arrives when an outage of one of the services is confirmed, or when services are restored; if some services have recovered and others haven't, you'll get a partial-recovery email listing which services are back and which are still down.
You won't get a notification in the following cases:
- during a scheduled panel update;
- if the merchant's payment page is intentionally disabled or the merchant itself is excluded from checks;
- if the module doesn't have any networks configured for accepting payments yet;
- if you've turned monitoring off yourself.
⚠️ Don't confuse this with other notifications
Licence-expiry notifications are sent separately — monitoring isn't involved there, though the licence expiry date is visible both on the monitoring page in your cloud account and in the corresponding module settings section on the server.
An outage notification goes to the email address of the cloud account owner whose licence covers monitoring. That address can differ from the one set up in the module's own notifications (see Set up email notifications in QryptoPay).
ℹ️ One notification per incident
Each incident gets one notification when it starts and one when it's resolved — there won't be repeated "still down" reminders.
How to connect monitoring
Monitoring is a paid licence option. It's purchased separately for each server, but within that server you can monitor several merchants at once (for how to add a licence option, see How to get a licence).
💡 The option stays paid for
Turning monitoring off stops the checks themselves, but it doesn't cancel the licence option you bought — it stays active and paid for until the end of its term.
You can add monitoring to your licence in one of two ways:
- in your cloud account — on the server page, "Monitoring" tab;
- in the panel — QryptoPay → "Settings" → "Monitoring".
After paying for the licence, go to QryptoPay → "Settings" → "Monitoring" on the server, check that monitoring is turned on, and select the merchants you want to watch.