The webhook delivery channel. Nomba sends HTTP POST requests to the merchant webhook URL when subscribed events occur, such as payment completions, payout events, order updates, and reversals.
Provider:NombaAsyncAPI: v2.6.0Spec: Nomba Webhook EventsOperations: 1Messages: 7
Channel address
/webhook
Operations
publish
receiveWebhookEvent
Receive a webhook event notification
Messages
PaymentSuccess
Triggered when a payment is successfully received in the merchant account, including POS terminal payments, web transactions, app payments, and virtual account transfers.
Content-Type: application/json
PaymentFailed
Triggered when a payment attempt fails due to insufficient funds, expired cards, declined transactions, or other payment errors.
Content-Type: application/json
PayoutSuccess
Triggered when a payout (transfer to a bank account or wallet) is successfully completed.
Content-Type: application/json
PayoutFailed
Triggered when a payout attempt fails during processing.
Content-Type: application/json
OrderSuccess
Triggered when a checkout order is successfully completed and payment has been confirmed.
Content-Type: application/json
PaymentReversal
Triggered when a previously successful payment is reversed due to a dispute, chargeback, or system correction.
Content-Type: application/json
PayoutRefund
Triggered when a payout is refunded back to the merchant account, typically due to an invalid recipient or failed settlement.
Content-Type: application/json
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.