KYT decision webhook

Endpoint health and suspension

Auto-suspension, SUSPENDED behaviour, and reactivation.

Tekmerion tracks consecutive failures per KYT endpoint configuration. A consecutive failure is any invocation that results in:

  • No valid response within the SLA window (timeout).
  • A non-2xx HTTP status.
  • An HTTP 2xx response with an invalid or malformed JSON body.
  • A network-level error (connection refused, DNS failure, TLS error).

A successful invocation resets the consecutive-failure counter for that endpoint configuration.

Auto-suspension

After a consecutive failure threshold is reached, Tekmerion automatically transitions the endpoint configuration to SUSPENDED status.

On suspension:

  1. No further KYT invocations are dispatched against this configuration.
  2. All active payment attempts for the merchant that are pending a KYT decision enter hold state.
  3. Funds for those attempts are neither swept nor refunded until the endpoint is reactivated.

Behavior during suspension

While an endpoint is SUSPENDED:

  • New payment attempts that would trigger a KYT invocation are held immediately.
  • No further automatic re-invocation occurs for any held attempt.
  • All affected payments require merchant or ops action to proceed.

Reactivation

A suspended endpoint is reactivated by restoring the configuration to ACTIVE status through the dashboard or API. After reactivation:

  • Tekmerion resumes KYT invocations for pending attempts.
  • The consecutive-failure counter is not automatically reset; recovery invocations contribute to or reset the counter as they complete.

Merchants SHOULD investigate and resolve the root cause of endpoint failures before reactivating to avoid immediate re-suspension.

On this page