Skip to main content

Documentation Index

Fetch the complete documentation index at: https://memberpulseptyltd.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Stripe webhook event processing entity Tracks Stripe webhook events for idempotent processing.

Fields

Core Fields

FieldTypeRequiredDescription
idUUIDAutoPrimary key
stripeEventIdstringYesStripe event ID (unique)
eventTypestringYesEvent type (e.g., payment_intent.succeeded)
eventDatajsonYesFull event payload
processingStatusenumYespending, processed, failed
retryCountintegerAutoRetry attempts (default: 0)

Processing Fields

FieldTypeRequiredDescription
processedAtdatetimeNoProcessing timestamp
processingErrorMessagetextNoError if failed
relatedEntityTypestringNotransaction, subscription, refund
relatedEntityIdUUIDNoMemberPulse entity ID

System Fields

FieldTypeRequiredDescription
receivedAtdatetimeAutoWebhook received time
createdAtdatetimeAutoRecord creation

Handled Event Types

Event TypeAction
payment_intent.succeededUpdate transaction, grant access
payment_intent.failedMark failed, notify member
customer.subscription.updatedSync subscription status
customer.subscription.deletedCancel membership
charge.refundedProcess refund
invoice.payment_succeededExtend membership
invoice.payment_failedTrigger grace period

Business Rules

  • Events are idempotent (check stripeEventId)
  • Failed events retry up to 3 times
  • Events logged for audit trail

Features

Stripe Webhook Event

Acceptance Criteria

Frontend
  • Admin/client UI can view and manage Stripe Webhook Event records where applicable.
Backend / API
  • CRUD operations exist for Stripe Webhook Event (create, read, update, delete/archive).
Permissions
  • Access is restricted to appropriate roles (tenant-scoped).
Business Rules
  • Fields and relationships documented on this page are enforced for Stripe Webhook Event.
Error Handling
  • Invalid payloads return field-level validation errors.