#josando-charges
drifting spruce
Hi there, please allow me to address your questions one by one 🙂
I can see that the Charges API is an older one. Is it still OK to use it?
It is okay to use, however I would strongly recommend PaymentIntent [0], as it comes with benefits such as:
- Automatic authentication handling
- No double charges
- No idempotency key issues
- Support for SCA
And these are not supported with the old flow with Charges.
I need to use some advanced features like Separate Charges and Transfers, Manual Payouts, etc., with an Express or Custom account (not Standard)
Is there anything you would like to know about Express/Custom accounts?
quartz crow
> I need to use some advanced features like Separate Charges and Transfers, Man...
Not directly related to Express/Custom accounts, but the Stripe website does mention that Separate Charges and Transfers require a more "complex" Connect integration. Can this integration be done via API calls alone? Because I am using a no-code software called Bubble, and I don't think I can run any custom code.
Also, I would like to stay PCI compliant so I'd like to handle everything via Stripe Connect as much as possible.
devout haven
@quartz crow you really can not use something complicated like Connect with a no-code platform, it's a bespoke integration for large platforms I would say.
you'd need a developer/development team
quartz crow
@devout haven Bubble is a pretty complex no code tool, and people seem to be using Stripe Connect with it without much problem. My business logic is a little more complex than the usual marketplace, so your point might still be valid. I need to research further.