Wave Mobile Money

Wave Webhooks

Outbound event delivery channel for asynchronously notifying merchant systems when state changes on the Wave platform. Events include checkout.session.completed, checkout.session.payment_failed, b2b.payment_received, b2b.payment_failed, merchant.payment_received, and test.test_event for portal-triggered smoke tests. Every delivery carries a Wave-Signature header containing a Unix timestamp and one or more HMAC-SHA256 signatures over the raw body; receivers must validate the signature and reject deliveries older than five minutes to prevent replay. Event payloads use a Stripe-style envelope (id, type, data) and the id field should be used to enforce at-least-once-delivery idempotency.

GitHub

Documentation

📖
Documentation
https://docs.wave.com/webhook
📖
Documentation
https://docs.wave.com/business

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/wave-webhooks"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: wave-mobile-money:wave-webhooks
name: Wave Webhooks
description: Outbound event delivery channel for asynchronously notifying merchant systems when state
  changes on the Wave platform. Events include checkout.session.completed, checkout.session.payment_failed,
  b2b.payment_received, b2b.payment_failed, merchant.payment_received, and test.test_event for portal-triggered
  smoke tests. Every delivery carries a Wave-Signature header containing a Unix timestamp and one or more
  HMAC-SHA256 signatures over the raw body; receivers must validate the signature and reject deliveries
  older than five minutes to prevent replay. Event payloads use a Stripe-style envelope (id, type, data)
  and the id field should be used to enforce at-least-once-delivery idempotency.
humanURL: https://docs.wave.com/webhook
baseURL: https://api.wave.com
tags:
- Webhook
- Event
- HMAC
- Asynchronous
tags_raw:
- Webhooks
- Events
- HMAC
- Asynchronous
properties:
- type: Documentation
  url: https://docs.wave.com/webhook
- type: Documentation
  url: https://docs.wave.com/business