01 · Context
The system receives bank-transfer notifications from Casso to update payments and trigger notifications, invoices and downstream synchronization.
Technical case study
Casso payment webhook
Extending post-payment processing with validation, reconciliation and decoupled events.
WebhookCassoEvent / ListenerSecure tokenReconciliation
02 · Problem
Webhooks can be duplicated or arrive out of order. Requests must be authenticated, transaction codes parsed, and amounts and states validated before recording payment.
03 · Architecture
Processing flow
01 Casso webhook
02 Token validation
03 Transaction matching
04 Payment update
05 Post-payment events
04 · Result
The extension runs in a live system and emits events for notifications, invoicing and post-payment synchronization.
05 · Ownership
I extended and operated the existing Casso flow; I do not claim the original core endpoint or direct MoMo/VNPay implementation.
06 · Trade-off
A shared secure token is not HMAC. Idempotency, unique constraints, reconciliation and unmatched-transaction handling are necessary to prevent double credit.
Want to go deeper?
I can walk through the technical decisions, constraints and alternatives in a conversation.
Email me