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": "5c4d9666-df40-47dd-8586-8e1a78906a9d",
"event": "order.created",
"created": "2026-06-12T15:00:35.298Z",
"data": {
"id": "c44egt37c6fp0000000000000",
"number": "TY-1ZXWJNU",
"totalKobo": 9942359,
"itemCount": 4,
"customer": {
"name": "Tunde Adeyemi",
"email": "tunde.adeyemi69@outlook.com",
"phone": "+2348140900619"
},
"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.