Comment by Dullaz
3 days ago
Could you elaborate on inflexible subscription system and also what you would like to see from a 3DSecure implementation?
Full disclosure: I'm a dev at a fintech startup and we're currently working on these two things so I'm curious how our direction lines up with your thoughts
> inflexible subscription system
For example, Braintree can't switch from monthly to annual billing (or the other way around). You have to delete the subscription and recreate it with a different billing period.
I want my customers to be able to switch plans, billing periods, currency, and buy additional items (user slots), all with proration.
> what you would like to see from a 3DSecure implementation
I would like not to see anything, really. I want to forget 3DSecure even exists. Stripe largely gets this right. Braintree required me to do many rather bizarre things, pass additional data, and then rewrite the entire flow once every couple of years or so. With the last rewrite, I was told that in my case (SaaS subscriptions) I would need to drag the customer through 3DSecure TWICE and that there is no other way. So I switched to Stripe, because I value my customers' time.
Also, 3DSecure with braintree would fail every once in a while and I would get customers from various countries telling me they are unable to subscribe. Braintree support, after a week or two, would inquire and either tell me it's the customer's bank (not helpful), or tell me that I have to rewrite my integration to a New Way of Doing Things, which was usually so far off the mark for my use case it wasn't even funny. I just checked my E-mail archives quickly for "Braintree support", over the years I'm up to around ~400 E-mails exchanged.