React to subscription lifecycle events from the built-in membership system

Free Intermediate Since v1.0.0

MembershipWebhookHandlers registers four handlers on the shared Stripe webhook and re-emits each Stripe event as a normalised core action carrying (string $stripe_subscription_id, \Stripe\Event $event). Add-ons should hook these routing actions instead of registering duplicate webhook handlers — it keeps per-event payload parsing in one place. Important: …_invoice_payment_failed listeners MUST NOT revoke a subscriber’s token or feed access — core policy lets Stripe exhaust its retry schedule. Revocation is reserved for …_subscription_deleted.

Code

<?php
add_action(
    'benecaster_stripe_membership_invoice_payment_failed',
    function ( string $stripe_subscription_id, \Stripe\Event $event ): void {
        // Do not revoke feed access here — core policy is to let Stripe
        // exhaust its retry schedule. Use this hook for diagnostics,
        // creator notifications, CRM updates, etc.
        my_addon_log_payment_retry( $stripe_subscription_id, (int) $event->created );
    },
    10,
    2
);

View on GitHub →

Code

Hooks Used