Skip to content
Last updated

Webhooks reference

Webhooks are the source of truth for final transaction outcomes. For the concept and handling rules, see the Webhooks guide.

Configure

In the Omno Dashboard, go to Developers → Webhooks → Create Webhook, set a Name and Webhook URL, choose Hook Type: Transaction, select the events you want, optionally pick an authorization method, and save. Monitor delivery under the same page: request payloads, your responses, and per-attempt status.

Confirmed delivery behaviour

  • Omno retries a failed delivery up to 10 times.
  • Process webhooks idempotently — the same transaction can arrive more than once.
  • Handle statuses out of order — never downgrade a final status, with the one exception TIMEOUT → SUCCESS for a pay-in (a late provider callback).
  • On any doubt, GET the transaction for the authoritative status.

ℹ️ Note: Your Omno integration team shares the full event list, the pay-in and payout payload schemas, signature/authorization options, the retry schedule and delivery details during integration.

Identify test transactions

A transaction processed by a test provider is identified by its test-provider ID (merchantPspId / processorPspId). Never credit or debit real balances for test-provider transactions. See Testing in production.

Build it →