Skip to main content
Under Schedule Only Recovery, when a transaction made outside Hyperswitch is reported to POST /v2/recovery, Hyperswitch tells when to retry the invoice. After recording the transaction, it decides the invoice’s next retry and sends it to the profile’s webhook URL. A transaction that doesn’t change the next retry sends no webhook: for example, one made with the customer present, or a charge that recovers the invoice. Each webhook has its own event_id, and the request is signed in the X-Webhook-Signature-512 header, like every Hyperswitch outgoing webhook.

Webhook body

string
required
The provider merchant id (platform/business owner).
string
required
The unique event id for each webhook.
string
required
recovery_retry_scheduled or recovery_limits_exhausted.
object
required
string
The time at which the webhook was sent.
string | null
The merchant id of the merchant account whose connector credentials are used for payment processing.