Estiaje Mx Webhooks

generated: '2026-11-07'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://estiaje.mx/blog/webhook-que-no-llego
sources:
- https://estiaje.mx/blog/webhook-que-no-llego
- https://estiaje.mx/en/blog/webhook-not-received
description: Estiaje documents the webhook events it expects from payment providers and the custom events it emits for monitoring.
events:
- event: checkout.session.completed
  description: Stripe Checkout Session completed event (fires when the customer receives the voucher for OXXO payments, with payment_status "unpaid").
- event: checkout.session.async_payment_succeeded
  description: Stripe event to fulfill OXXO payments after the asynchronous payment succeeds.
- event: payment.approved_by_customer
  description: Custom Estiaje event emitted on the thank‑you page when the customer returns with an approved payment.
- event: payment.confirmed
  description: Custom Estiaje outcome emitted after the webhook has successfully processed and marked the order as paid.
delivery:
  signature: Stripe uses the `stripe-signature` header; Mercado Pago validates an `x-signature` header with the application’s secret key.
  content_type: 'Raw request body must be used for signature verification (e.g., `express.raw({ type: ''application/json'' })` for Stripe).'
note: Both providers require the endpoint to respond with HTTP 200 (or 201 for Mercado Pago) within the allowed time (22 seconds for Mercado Pago).
  If the response is not received, the provider treats the delivery as failed and will retry according to the policies below.
docs: https://estiaje.mx/blog/webhook-que-no-llego