What providers send after checkout.

Every playground on this site runs against a real test merchant account, which means real notifications arrive at a real endpoint. Rather than logging them and moving on, they are stored and published here.

Each feed shows the notification body exactly as the provider sent it. No renaming, no unified schema, no cleaned-up version. Providers disagree about what to call things and how to structure them, and that disagreement is part of what makes integrating more than one of them work.

The two feeds below are the same panel reading different data, which makes the disagreement easy to see. Adyen sends an event code alongside a separate success field, so one event name covers both an approval and a decline. Stripe puts the outcome in the name instead, so a failure arrives as its own event type and there is no flag to check. Neither is wrong, and a handler written for one will quietly mishandle the other.