AsyncAPI channel · Nomba
· Nomba Webhook Events
/webhook
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.
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/jsonPaymentFailed
Triggered when a payment attempt fails due to insufficient funds, expired cards, declined transactions, or other payment errors.
Content-Type:
application/jsonPayoutSuccess
Triggered when a payout (transfer to a bank account or wallet) is successfully completed.
Content-Type:
application/jsonPayoutFailed
Triggered when a payout attempt fails during processing.
Content-Type:
application/jsonOrderSuccess
Triggered when a checkout order is successfully completed and payment has been confirmed.
Content-Type:
application/jsonPaymentReversal
Triggered when a previously successful payment is reversed due to a dispute, chargeback, or system correction.
Content-Type:
application/jsonPayoutRefund
Triggered when a payout is refunded back to the merchant account, typically due to an invalid recipient or failed settlement.
Content-Type:
application/jsonAbout 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.
Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.