2

Paymill's API is awesome. It's a blaze to work with, and I should be up&running, were it not for an edge case. Context is a SAAS app, with a demo trial, and the ability to upgrade & downgrade at will.

Scenario: She changes her mind, and tries to upgrade again. So far, I've tried modeling this via:

Desired output is Continuing Subscription: no credit card charges are made until the next monthly period, and further CC charges are applied via the new payment info.

In what ways can this be achieved?

Many thanks!

Community
  • 1
  • 1
Silver Dragon
  • 5,480
  • 6
  • 41
  • 73

1 Answers1

2

Let me start by saying that the POST you described should be possible to execute. This is currently a bug, and this will be fixed sometime next week.

But your use case is, unfortunately, not supported at the moment. We are working hard to make our subscriptions feature more powerful, while retaining the simplicity of usage. We cannot offer a timeline for this, but we would love to hear more about your case.

Currently, merchants are encouraged to manage the subscriptions on their own, as this is not a simple matter of changing the amounts being charged on the next subscription's due date. For instance, if a client of yours decide to downgrade, would you make a pro-rata refund of the excess? Same for upgrade: would you charge the full amount of the new subscription on the due date, or a pro-rata of the old subscription + pro-rata of the new?

That said, I'd encourage you to keep an eye on our blog for announcements of an improved subscriptions handling.

Disclosure: I work at PAYMILL.

jpkroehling
  • 13,881
  • 1
  • 37
  • 39