Payment transactions and the provider webhook events that create them.
Payments in ledger
99
Replaying a duplicate webhook never changes this number.
Succeeded
87
Failed
10
Refunded
2
Showing 99 of 99
| pay_0098 | Ruwi Street Food | OMR 4.095 | Succeeded | 27 Jan, 02:44 pm |
| pay_0099 | Bahla Clay Oven | OMR 4.095 | Succeeded | 27 Jan, 02:44 pm |
| pay_0097 | Doha Pearl Kitchen | OMR 15.645 | Succeeded | 26 Jan, 02:44 pm |
| pay_0096 | Dar Al Qahwa Cafes | OMR 15.645 | Succeeded | 25 Jan, 02:44 pm |
| pay_0095 | Seeb Family Kitchen | OMR 8.295 | Succeeded | 22 Jan, 02:44 pm |
| pay_0093 | Dubai Marina Brasserie | OMR 50.400 | Succeeded | 21 Jan, 02:44 pm |
| pay_0094 | Al Hail Roastery | OMR 8.295 | Succeeded | 21 Jan, 02:44 pm |
| pay_0091 | Al Majlis Restaurant | OMR 15.645 | Succeeded | 20 Jan, 02:44 pm |
1–8 of 99
Each delivery carries a provider event id, which is the idempotency key. The processor verifies the signature, records the id, and ignores any repeat of an id it has already applied, so a replay can never create a second payment.
Replay an event to see how duplicates are handled. The ledger count above shows whether a payment was created.
| Actions | |||
|---|---|---|---|
evt_dm_ivzmfhfntcp7invoice.payment_succeeded | Verified | Pending | |
evt_dm_9ansudwmf57sinvoice.payment_succeeded | Verified | Pending | |
evt_dm_8saryt3l3tu5invoice.payment_succeeded | Invalid | Rejected | |
evt_dm_3oauiiqwusu1invoice.payment_succeeded | Verified | Duplicate ignored | |
evt_dm_p7lsk07ryaxvinvoice.payment_succeeded | Verified | Processed | |
evt_dm_3oauiiqwusu1invoice.payment_succeeded | Verified | Processed |
1–6 of 17
Demo time: 31 Jan, 02:30 pm. Replays are simulated locally and never contact a payment provider.