From 9218484c46eba957125d39d57c6a07a59f31ec2f Mon Sep 17 00:00:00 2001 From: xaxxoo Date: Tue, 1 Sep 2026 21:34:47 +0100 Subject: [PATCH] docs(payments): document webhook-delivered payment events in README Add a section to the README documenting how internal payment domain events (payment.created, payment.completed, payment.failed) are bridged to the outbound webhook system via PaymentWebhookListener. The listener and wiring code already exist; this commit adds the missing documentation to satisfy the acceptance criteria. Closes #771 Co-Authored-By: Claude Opus 4.6 --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index c1b7162..142402e 100644 --- a/README.md +++ b/README.md @@ -160,6 +160,22 @@ Set `FEATURE_MAINNET_PAYMENT_SUBMIT=true` in your production environment only af See [Mainnet Payment Feature Flag](docs/MAINNET-PAYMENT-FEATURE-FLAG.md) for full operational guidance. +### Webhook-Delivered Payment Events + +Payment domain events are bridged to the outbound webhook system via +`PaymentWebhookListener`. When the `PaymentsService` emits an internal event, +the listener forwards it to `WebhookEventEmitterService` for delivery to +registered webhook endpoints. + +| Internal event | Webhook event type | Trigger | +|--------------------|----------------------|---------| +| `payment.created` | `payment.created` | New payment created | +| `payment.completed`| `payment.completed` | Payment confirmed | +| `payment.failed` | `payment.failed` | Payment failed | + +Webhook dispatch errors are logged but never propagated to the caller, so +payment operations are not blocked by downstream webhook failures. + ### 🧠 Account Abstraction Layer * User identity mapped to blockchain accounts