order.createdBuyer-initiatedOrder created
A buyer completed checkout and Paystack confirmed payment.
When this fires
A buyer finished checkout and Paystack confirmed the payment. This is the canonical 'new order' signal.
High frequency
This event is buyer-initiated, which means it can fire at checkout-traffic volume during busy periods. Make sure your handler responds in under ten seconds; queue any heavy work.
Sample payload
This is the exact envelope shape we POST to your endpoint — outer wrapper plus the per-event data payload. Field values are randomised on each render so you see the general shape, not a fixed example.
json
{
"id": "666ae41c-944e-416c-bd10-297836dd9e19",
"event": "order.created",
"created": "2026-07-29T11:24:57.845Z",
"data": {
"id": "c5skgduvjp190000000000000",
"number": "TY-ZZOMU1X",
"totalKobo": 12133304,
"itemCount": 4,
"customer": {
"name": "Folake Adebayo",
"email": "folake.adebayo69@yahoo.com",
"phone": "+2347021366327"
},
"shippingAddress": {
"line": "Allen Avenue, Ikeja",
"city": "Lagos",
"state": "Lagos",
"country": "NG"
},
"currency": "NGN"
}
}Use cases
- Print or send a packing slip to the merchant's fulfilment desk.
- Push the order into your ERP / accounting system in real time.
- Notify a Slack channel so the team knows a high-value order just landed.
Subscribe in the dashboard
To start receiving this event, add it to a webhook's subscription list in Developers → Webhooks. Wildcard subscriptions ( order.*) work too — see the webhooks guide for the matching rules.