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": "6a47e22f-3cad-4aac-b0d3-338c7e523a57",
"event": "order.created",
"created": "2026-06-12T02:18:47.751Z",
"data": {
"id": "ch6gh1v7e7ku0000000000000",
"number": "TY-AS9QGRS",
"totalKobo": 1537184,
"itemCount": 1,
"customer": {
"name": "Nkechi Okonkwo",
"email": "nkechi.okonkwo84@outlook.com",
"phone": "+2348134681170"
},
"shippingAddress": {
"line": "Adetokunbo Ademola Crescent, Wuse 2",
"city": "Abuja",
"state": "FCT",
"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.