#Meta data is not coming for all subscription event

1 messages · Page 1 of 1 (latest)

wispy apex
#

Its showing up for subscription.active but not for payment.succeeded.
Is it a bug ? If not can we please implement this

jade wadiBOT
# wispy apex Its showing up for subscription.active but not for payment.succeeded. Is it a bu...

It seems that you are experiencing an issue where the subscription.active event is being triggered, but the payment.succeeded event is not showing up as expected. This could be due to several reasons, including the payment flow or specific conditions related to the subscription setup.

To troubleshoot this, consider the following steps:

  1. Check Payment Flow: Ensure that the payment flow is correctly set up. The payment.succeeded event should occur after the initial payment is processed. If there are any issues with the payment method or if the payment is pending, this event may not trigger.

  2. Review Subscription Settings: Verify that the subscription settings are configured properly. If there are any trial periods or specific billing cycles set, the initial payment might be delayed or not processed as expected.

  3. Webhook Configuration: Ensure that your webhook configuration is correctly set up to listen for the payment.succeeded event. If the webhook is not configured properly, you may not receive the event notifications.

  4. Logs and Error Messages: Check the logs for any error messages or warnings that might indicate why the payment.succeeded event is not being triggered.

If after checking these points the issue persists, it may not be a bug but rather a configuration or setup issue. In that case, you might want to reach out to the support team for further assistance or to request the implementation of a feature that ensures both events are triggered as expected.

If you need further assistance or specific implementation details, please provide more context about your setup or any error messages you are encountering.

jade wadiBOT
compact hollow
#

Subscription metadata will only come in subscription webhook -- both are separate object for us.

tall bobcat
#

I think the workaround would be get metadata from the linked subscription_id in the payment payload.

compact hollow
warm socket
#

Literally facing this same issue rn

compact hollow
warm socket
#

Please fix it, metadata should come in all the payment webhook events which are associated with the subscription.

wispy apex
#

+1 on this

compact hollow
#

We will add this today!

warm socket
# compact hollow We will add this today!

Also make sure that the metadata passed when creating a subscription should come in all the payment webhook events and also on all future recurring events related to that subscription.

compact hollow
#

Yes we will have this done by EOD.

compact hollow
#

@warm socket @wispy apex we have deployed the fixes.

tall bobcat
#

great