2

I can't find a way to trigger webhook notifications for subscription actions that happen in the future. How am I supposed to develop a subscription billing mechanism if my only way to test it is to wait fo 1 month for the next billing cycle?

For example I need to develop subscription upgrades and downgrades right now. This means I need to handle proration etc. But I can't find a way to test if my code actually works - because I can't trigger future billing cycles.

Renka
  • 146
  • 9

1 Answers1

0

Full disclosure: I work at Braintree. If you have any further questions, feel free to contact support.

I think this question might be better addressed to our support team as there might be more things to work out with your integration and testing with regards to managing Braintree's recurring billing system.

Depending on your settings, events like changing the price of an active subscription can cause transactions to be issued immediately, or just impact the subscription's balance which can be determined by assessing the balance parameter of the subscription. This would happen against a subscription which was created on the same day as well, so that shouldn't impact your testing specifically, save receiving a webhook on its future billing date. Those webhooks however would reflect the result of your subscription billing the addition/difference between the next_billing_period_amount and the balance.

In either regard I'd recommend opening a ticket with our support team to work this out further.

Ryan Regan
  • 116
  • 5
  • 2
    I opened a support ticket and got exceptionally unhelpfull response from there. It seems the platform just does not provide the neccessary tools to actually test subscriptions. AFAIK there is no way to actually test anything subscription related on Braintree. You just need to read the docs and HOPE to get it right on the first try. Which is pretty bad practice - and I'm really not willing to do that. So currently we are looking for alternative payment methods - as we can't really build our software around a complicated service/API that is not testable in any reasonable way. – Renka Dec 16 '17 at 21:17