Variable subscription empty total

Hi @ydwebdesign,

This is how the current functionality is designed. With the plugin’s out of the box subscription functionality (not using WCS), the order total reflects all charges that are not maintained via the Braintree Subscription.

For example, if you had a one time shipping fee, that would be reflected in the order total. But if you have a recurring total that starts immediately, then it will be reflected in the recurring totals section of the checkout page and the subscription object, not the order.

We have considered changing this so that the initial order captures the entire charge via a transaction and then recurring charges are handled by the Braintree subscription.

If this is braintree for woo commerce….why would it work this way?

Does not make sense.

So the recurring charges are not handled by braintree automatically? The subscription is in the braintree sandbox showing active and the next bill date… shouldn’t it be now?

Hi @ydwebdesign,

I believe you misunderstood a part of my explanation. The recurring charges are handled by Braintree and that’s why you see the subscription active in the Braintree control panel.

There are two types of payments; one time transactions and recurring totals. One time transactions are things like regular products, fees, one time shipping, etc that aren’t charged more than once. Those have to be charged immediately via a transaction call. Those are the amounts that you see in the order total.

What you see in the recurring total section is what is charged as part of the subscription. So if you had a product that was $10 / month, the recurring total would show as $10.

What we are considering doing in a future release is including the subscription(s) first recurring total in the order’s transaction call, if the subscription(s) start immediately. Then, the first payment date in the Braintree control panel will show as being the next payment date. This would perhaps visually make more sense on the checkout page etc and cut down on confusion.

Kind Regards,

The next version of the plugin (2.6.29) will resolve the highlighted issue which should cut down on customer and merchant confusion.

Kind Regards,

Correction. Version 2.6.30.

I appreciate your attending to this. Testing out. Thank you.