I just filed a bug report.
My use case is that I use my customers’ Stripe account to charge their users and so I charge an application fee for that. Use case supported on the v2
I just upgraded to v3 and the charge happened successfully but it charged my account instead of my customer’s connected account. I checked my settings for the workflow Charge current user and sending everything like before.
Just to make sure the workflow “Charge current user” was not using stale data before I upgraded to Checkout v3 I deleted the workflow and recreated but it still uses my main Stripe account to charge the end user not my customer’s Stripe account as it used to be
@marca Would you agree to add the Client Reference ID as a parameter in the action “Charge the current user” ?
It would be easier to find the linked purchased Thing from webhook
Watch out everyone - I’ve found a pretty bad bug (which I’ve reported).
I’ve got a payment page where I’m trying to charge 6,000 JPY:
But, when people click through to the Stripe checkout, it becomes 600,000 JPY
Glad I caught it before the customer tried to pay 
EDIT: It got fixed 
We just pushed a fix for this! Let us know if you have additional questions by emailing support@bubble.io.
@Bubble Asking again about adding client_reference_id (introduced with PaymentIntent) in the “Charge a user” action since it is the only way to link a checkout.succeeded to a Thing BEFORE the charge is done
It looks like we lost the ability to make the plan name dynamic. Any chance to get it back? It is very cumbersome not to be able to define the plan dynamically… Or is there a new way to do it now with V3?
V2:
V3:
Thanks!
Also, it doesn’t seem that the trial period we define in the action step “subscribe the user to a plan” is taken into account anymore… Anybody else having trouble with that?
Best is to file a bug report
Will do! Did’t want to trouble the support team with something that may have already been reported/solved 
I already reported about the trial period some days ago. Bit it seems the issue is Stripe-side.
There is also an issue when money is charged on behalf of a seller account. The app fee must be a positive integer. Bubble set it to zero when the value is empty. Bug report also filled in.
Just added this functionality back!
We’ve also renamed this option “Dynamically specify plan,” which seems to make a bit more sense.
Thanks a lot!
I created a post here for reference. Is there a way the new plugin can act the same as the old in regards to workflow? i.e wait for a successful checkout to continue the rest of the workflow on return?
Any help appreciated.
Looks like I forgot the post!
Here is the new issue the V3 has created: Stripe V3 SCA Workflow
I won’t file a bug report at this point because I’m note sure if it’s intended or not.
With SCA the email of the client is empty? I’m applying the subscription to Current User. So the current user’s email should appear there automatically right?
Hey,
Where should I go to do a feature request? Should I do it in here? or on the Bug Report page?
I’d like to request the addition of the statement_descriptor field to be dynamically set.
Use case: I have a marketplace and the destination accounts (merchant / connected accounts) have their own statement descriptors which not always describe the product they are buying through our marketplace, it is only an additional field on the Payment Intents API and should be an easy addition so we can directly / dynamically set and avoid a good part of chargebacks because the customer doesn’t remember purchasing or does not appear to recognize the charge because of the descriptor
This is a simple switch that can be made in the plugin editor. If you reach out to bubble support I’m sure they will implement it.
Good idea, that’s what I’m gonna do. Thanks
Without the possibility to save CC information, is it still possible to do a delayed payment.
For example, if a user books a room and fills out his cc details. First the host has to accept the booking before the user is charged.
Is this still possible when CC info cannot be saved anymore?
@allenyang
