card.application.rejected
Card application execution failed
When Emitted
Triggered when application execution fails or an explicit cardholder rejection moves the application to failed. It does not depend on a member email address; retries are deduplicated by application ID and status version. Normally the notification status is rejected and the application detail status is failed. When operations close a failed quick-verification application whose card issuance fee was retained and refund that fee, a new notification of the same type is sent with a higher status version. Its status remains rejected, while application_status is refunded (or canceled if there is no refund). Retrieve GET /v1/cards/applications/{data.id} for the latest application status; use the merchant funds ledger to verify the refund credit. This refund retains the separately charged Quick KYC application fee. Notifications contain no monetary amounts or currencies. Raw upstream reasons are not exposed; retrieve failure_code from the application details.
Payload
{
"event_id": "evt_491ad542803841bca106f69ae28a3c14",
"event_type": "card.application.rejected",
"created_at": "2026-09-15T08:00:00Z",
"merchant_id": "acme",
"livemode": true,
"data": {
"object": "card_application",
"id": "cap_9c41f0a8-27d5-4e63-b0a9-1f7c85d2e340",
"external_member_id": "u_88123",
"status": "rejected",
"status_version": 4
}
}
Payload Fields
| Field | Type | Description |
|---|---|---|
id | string | Use this for deduplication. evt_… remains unchanged when the same event is redelivered. |
type | string | Always card.application.rejected |
created_at | string | Time the event was created (RFC3339), not its delivery time. It is unchanged on redelivery. |
data.object | string | Object type; determines which endpoint to query with data.id |
data.id | string | Object ID; use it to retrieve details. |
data.status | string | Treat unrecognized values as unknown and raise an alert; do not fall back to “processing” |
data.status_version | number | Monotonically increasing; use it to discard older states that arrive late. |
Signature Verification and Deduplication
Verify the signature against the raw request body bytes. Do not parse and reserialize the JSON: your JSON library may change key order or whitespace, which changes the signature and can look like a key configuration error.
// Node · Run before parsing JSON
const raw = await readRawBody(req); // Buffer / string; do not use parsed req.body
const expect = crypto.createHmac("sha256", WEBHOOK_SECRET).update(raw).digest("hex");
const got = req.headers["z-signature"]; // Format: t=<unix>,v1=<hex>
if (!timingSafeEqual(expect, parseV1(got))) return res.status(400).end();
// Deduplicate using the envelope id, not data.id
if (await seen(JSON.parse(raw).id)) return res.status(200).end();
For the full procedure, including timestamp tolerance and redelivery semantics, see Webhook Guide.