Skip to main content
For general webhook concepts like bubble-up behavior, payload visibility rules, and versioned snapshots, see Webhook Concepts.

Description

This event is triggered when a payment transaction status changes — for example, to success or failed.

Integration Details

  • Subscription Key: pay.transaction.updated
  • Use Case: Automatically fulfill orders or unlock features in your app once a transaction becomes success.
  • Related Events: pay.transaction.created

Trigger

  • Event Type: pay_transaction_updated
  • Source: Update of a record in the pay.transaction table.
This event does not include an old field. Transaction status changes are tracked in transaction_status_history within the payload. See Versioned-Snapshot Objects.

Cross-Service References

The payment payload traverses the order chain to provide full purchase context:
  • Order (pay.order): Order metadata and status.
  • Order ItemsItemSKU (pay.sku): Product details including pricing and currency.
  • Coupon (pay.coupon): Discount information if applied.

Payload Example

Payload Type Showcase

Field Notes

  • payment_id is a UUID from the payment gateway (e.g., Stripe, Razorpay).
  • narration is a human-readable payment description.
  • transaction_status_history provides the status audit trail. Empty on creation, populated on subsequent status transitions.
  • coupon on order items is nullable — only present if a discount was applied.
  • The order → order_items → item → sku chain provides the full purchase context.