Luis

Hi @mrclayton , thanks.
I’ve just sent the contact form.

Hi @mrclayton , thanks for the reply.

Yes, we create some subscriptions from another website (directly with BT API). So maybe that’s what those Subscription IDs mean. I know we had these logs entries way before this problem.

As for the WooCommerce orders, you can see attached our Woo Setup, where that option is disabled.

Thanks

Hi @mrclayton ,

Yes we’re using the built in Subscriptions, and it’s happening for all subscriptions.

Thanks

Hi @mrclayton ok thanks I will!

Hi @mrclayton,
thanks for the response.

Yes you’re right, the initial issue is the same.

On that thread we found out the webhooks were not working and I thought fixing that issue could also solve this situation, but unfortunately it didn’t.

That’s why this new thread was to find if there is anything we can do as a workaround until that is fixed on the core.

Is there a hook we can use after the payment is failed, where we can remove any subscription that may have been created by it?

Thanks!

Hi @mrclayton, thanks.

I’ve done a few tests with the webhooks and we were able to have the webhooks being triggered after adding these lines to the ‘process_webhook’ function.

After this, if we cancel a BT subscription (in BT account) the subscription in Woo was updated to Cancelled too.

It’s seems the wc_braintree_notification parameter was not sending any values. Only by parsing the signature and payload, was I able to get the notification object.

Is it possible BrainTree changed something on the webhooks args?

Here’s the code I’ve added.

$notification = $request->get_param( 'wc_braintree_notification' );

// FIX START
$bt_signature = $request->get_param( 'bt_signature' );
$bt_payload = $request->get_param( 'bt_payload' );
$notification = braintree()->gateway()->webhookNotification()->parse(
	$bt_signature, $bt_payload
);
// FIX END

try {
// developers can use this hook to process webhooks to suite business needs.
do_action( 'wc_braintree_webhook_notification_' . $notification->kind, $notification, $request );

Thanks!

• This reply was modified 5 years, 5 months ago by Luis.
• This reply was modified 5 years, 5 months ago by Luis.

Thanks for the quick reply.

Shouldn’t the subscription just be created in BrainTree if the shop_order is successful?

We are having some use cases where a client does this:

• Places the first order but it failed (refused credit card for example)
• Places a second order and succeeds

This creates 2 (pending) subscriptions for that client.
One for the failed payment.
One for the success payment.

And we have to go to BT to manually cancel the subscription from the first failed order.

Do you see any reason for having the first subscription be created, because we never receive any payment from the customer (and when the renewal comes it will also fail).

Thanks again for your help!