#PaymentReceived
🌐💼 Boost your SEO rankings with
serpclix.com/users/referr...
Real clicks from real people. Check out their referral program and start earning today!
#SerpClix #SEOBoost
#MonumentalMarketingLLC #SerpClix #PaymentReceived #PayPal #ExtraIncome #ReferralCommission #OnlineEarning #WorkFromHome
February 22, 2024 at 6:44 PM
📦 samdevxuz/algorix-pay v0.2.0

Userbot-based P2P payment receiver for Laravel — listen to bank notification bots (Click, Payme, Uzum) via MTProto and emit PaymentReceived events.

🔗 https://github.com/SamDevXuz/algorix-pay
May 1, 2026 at 6:14 PM
Event sourcing and BDD share the same pattern: we can only capture what has happened, not what hasn't.

No more "Given I have not paid"—instead, "Given seven days have passed."

What events has your system captured?

lassala.net/2026/02/11/e...

#BDD #EventSourcing
Event Sourcing and the Past Tense of Given
I was thinking about event sourcing and event storming the other day, and something clicked. Events in these systems are always named in past tense: “OrderPlaced,” “PaymentReceived,” “InvoiceAged.”…
lassala.net
February 11, 2026 at 7:29 PM
Your Process Manager (thing coordinating multiple services) can ITSELF be Event Sourced!

Events IN: OrderPlaced, PaymentReceived
Events OUT: ReservationRequested, ShipmentScheduled

Orchestration with full history and testable like any aggregate

It's events all the way down
October 24, 2025 at 8:24 AM
Internal Events:
- CustomerAgeCalculated
- InventoryReserved
Private domain implementation. Can change anytime

External Events:
- OrderPlaced
- PaymentReceived
Published API. Version instead.

Exposing internals creates distributed coupling.

Keep them separate.
October 11, 2025 at 8:24 AM