Channel for Affirm checkout lifecycle events. Affirm sends POST requests with content-type application/x-www-form-urlencoded to the merchant's configured webhook endpoint as customers progress through the checkout flow.
Fired when a customer opens the Affirm checkout flow.
Content-Type: application/x-www-form-urlencoded
CheckoutApprovedEvent
Fired when a customer receives a positive credit decision from Affirm.
Content-Type: application/x-www-form-urlencoded
CheckoutNotApprovedEvent
Fired when a customer receives a negative credit decision from Affirm.
Content-Type: application/x-www-form-urlencoded
CheckoutConfirmedEvent
Fired when a customer confirms their financing and is redirected back to the merchant.
Content-Type: application/x-www-form-urlencoded
About AsyncAPI
The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.