Webhooks
Plan for asynchronous payment notifications while the merchant webhook product is finalized.
Merchant webhooks
Merchant-facing webhooks are coming soon. A saved webhook URL backend and provider callback handlers exist internally, but the current visible Settings page does not expose webhook configuration and the code does not implement a complete public delivery contract.
Do not use internal callback routes
Provider and WooCommerce callback endpoints are implementation details. They are not general-purpose merchant webhook URLs and must not be configured manually.
Planned documentation structure
- Purpose and supported event names.
- Versioned JSON payload examples.
- Signature verification and replay protection.
- Delivery timeouts, retry schedule, and idempotency.
- Endpoint health, logs, and error handling.
Design safely now
Treat provider results as asynchronous, make order updates idempotent, and retain a mapping between your order identifier and EasyMoPay transaction identifier. Wait for the public signing and retry specification before accepting webhook traffic.