Provider health
Test a provider connection, read its health and diagnosis, check webhook deliveries and failures, and know when a payment method stops being offered.
On this page
Health in Control Center is measured, never assumed: it comes from the instance's configuration and from the last connection test that HyoNova actually ran.
Test a connection#
On the instance card, Test connection (providers.manage) makes one authenticated, read-only call to the provider from HyoNova's servers and stores a safe diagnosis with its time and latency. For bank transfer it checks that the bank details are complete.
| Diagnosis | Meaning |
|---|---|
live_connected | An authenticated call to the live account succeeded |
sandbox_connected | An authenticated call to the test (sandbox) account succeeded |
native_ready | Bank transfer: all bank details are present |
missing_credential | A required credential is not entered |
configuration_incomplete | A required setting is missing (the card lists which) |
auth_failure | The provider rejected the credentials |
endpoint_unavailable | The provider did not answer |
rate_limited | The provider is limiting requests |
disabled | The instance is turned off |
Health#
| Health | Meaning | Route usable |
|---|---|---|
| Not configured | Disabled and never given credentials | No |
| Disabled | Turned off by an operator (Stripe's state) | No |
| Configuration incomplete | Enabled, but a required field is missing | No |
| Configured | Complete and enabled, not tested since the last change | Yes |
| Healthy | Last test: live_connected, sandbox_connected or native_ready | Yes |
| Degraded | Last test: auth_failure, missing_credential or configuration_incomplete | No |
| Unavailable | Last test: endpoint_unavailable or rate_limited | No |
Because every save clears the last test, run the test again after each change.
Webhooks#
Each instance card also shows the webhook URL and the events to enable at the provider, when the last webhook arrived and whether its signature was valid, the last event processed successfully, and the number of failed webhook events in the last 7 days.
The provider event log in Payments & billing lists every received provider event with its provider, type, company, attempts and outcome, and can be filtered by outcome, provider and company:
| Outcome | Meaning |
|---|---|
processed | Applied to HyoNova's records |
duplicate | Already received; nothing applied twice |
ignored | Not relevant, or could not be matched to a company (unmatched), or a test event sent to a live instance (environment_mismatch) |
ignored_old | Older than a change already applied; never moves a subscription back |
failed | Processing failed; the provider retries, and reconciliation lists it for attention |
A request with an invalid signature is refused and nothing is stored; the card then shows the last webhook as not verified.
Status#
| Feature | Status | Notes |
|---|---|---|
| Payment providers and routing | Requires setupBuilt, but works only after a supporting service is configured for your workspace. | Configure payment provider instances, test their connections and route each payment method to one of them. |
Was this page helpful?
Thanks. Page ratings are not collected yet, so nothing was sent. If something is missing or wrong, see the Get help page.