If you were to initiate a transfer after a successful charge, you will get an error. You have to wait days for it to make it to your available balance and transfer then.
I want to start the migration, but don't want to lose access to Balanced all together until we're ready...
Greetings from a fellow "Limerician" btw :)
i.e. ACH debits, marketplaces, etc.
Migrating over to Stripe sounds great, but having these libraries updated with the proper endpoints seems like a must.
Specifically, for those in the ACH beta you can put a customer's bank account token in that field to charge their bank account.
(I currently have this ability with Balanced. Also have very low fraud, chargeback, etc.)
To make an ACH debit, you'd need to verify a bank account beforehand. And I don't think client libraries support a `bank account resource` w/o curling.
Maybe I'm missing something.
https://www.wepay.com/developer/facilitate_withdrawals/settl...
https://www.wepay.com/developer/facilitate_withdrawals/embed...
Disclaimer: I haven't actually used them myself. YMMV.
In other words, while I and many others may wish you to actually get to Balanced's level of public commitment to transparency, the essential item is to allow people to simply use Stripe without being forced to run non-free code on their own machines client-side. Fixing this is as simple as making the source just for the client-side JS be available under an appropriate license and including some header or license file indicating this appropriately.
Please consider this, it will win you a lot of good will and is the right thing to do.