in SaaS mode autoMATIC SUB-ACCOUNT creation is designed so pathetically
S
Soumyen Giri
I understand one of the main feature of SaaS mode is automatic sub-account creation. However terribly surprised to see the designer of this feature has messed it up very badly, which costs money and creates frustration among the users. More surprisingly where Product Team is fully reluctant not to pay attention on this where One revenue vertical is dependent on this feature.
The logic might be
1) First pay (which will fire the trigger) then
2) sub-account will be created automatically.
Now why is it so tightly coupled with one of a particular payment processor (Stripe) ? This might be the scenario 8 years back at the time of MVP design. Why is it not rearchitected later on ?
I comes from India and here Stripe dont open our account so easily. So will we not be allowed to use this feature ? Guys PLS TAKE THIS AS A SHOWSTOPPER AND RECTIFY.
Log In
R
Ryan Moore
I'd love a bit more control to help automate the first payment to the account setup, though I'm seeing some path improvements already since at least through nmi (not sure about stripe), you can set up a monthly payment on a sales form on a page and once the monthly payment is made that becomes an automatically setup 'membership' which can be used as a trigger in workflows. It would be even nicer if we can then grab that information from the customer that was provided on the order form, and set a 'create subaccount' event from that first payment, even then setup a freeze sub-account if the membership goes into a default status. I'm not sure that CAN'T be done already, but to link the sub-account DIRECTLY to the membership payment status would be AWESOME.