Create a subscription - Customer ID = results of step 2; Plan id= the ID I set on the Stripe test dashboard; tax=0.
The workflow seems valid, but I keep on getting the error âinvalid source object: must be a dictionary or non-empty stringâ for the âcreate a customerâ step (which I canât do without, it seems).
Is the Plus version still available? I canât find it in the plugin list. Also, are you planning on supporting the new onboarding features that Stripe Connect just announced?
Thanks!
Great question! Iâve had a few weird errors pop up in the Stripe ever since I upgraded API versions, but payments still process. Would be good to know how we should go about updating Stripe API when Stripe.js Bubble plugin gets an update.
The client-side requests, such as âConvert cardâ, are made using the latest Stripe library available. All of the additional requests, such as âCharge a paymentâ, are made without any API versioning. Stripe lets the developer set the API version right from their dashboard.
For the future, reach us at plugins@cobubble.com so we can help you directly and keep this post clear.
Weâll be sure to post any necessary updates that users should know about right to this post.
Nathan - were you able to figure out how to charge a customer for a seller using a customerâs already saved info? I have a customer saved on the platform Stripe account (as opposed to the connected stripe account), and when I try to create a subscription for a seller using that customerâs info it says the customer doesnât exist.
The stripe documentation seems to suggest you need to tokenize the customer before adding it from the platform account to a connected seller stripe account, but I canât see how to do that in the Stripe.js plug plugin.
You mentioned that you tried to âcreate a subscription for a seller using that customerâs infoâ which yields a âcustomer doesnât existâ message. Bare in mind that any call that denotes an action done for a seller is executed as if the seller made the request. Since the customer exists as a customer on your platform, and not as a customer of the seller, Stripe throws the error saying the customer doesnât exist altogether.
The solution?: Create a customer for the seller Create a subscription for seller.
Thanks for the response Salar! The reason I didnât use that process is because my app is going to have a customer buying from multiple sellers, at various points in time. I believe Stripe calls this âshared customersâ. I understood your suggested process would require getting/passing the customerâs payment info each time I wanted them to buy from a new seller.
The stripe documentation (https://stripe.com/docs/connect/shared-customers) suggests you create an account on the main platform, and pass that through to connected sellers as a token. Is that possible via the plugin?
Once you create the customer that has the payment method stored, youâre all set. Weâd love to help out, but we donât offer support on the forum. Give us a shout at plugins@cobubble.com and we can take it from there!
Any chance the documentation could be updated to include all the functionality? The video is nice, but a suggestion from my experience watching it would be to offer shorter length videos outlining each function.
This is functionality I would like to have access to. It is indeed possible according to the documentation. Do I need to reach out to you via email to get more info on how to do this?
Stripe has a policy about sharing customers outlining the differences between a platformâs Customer and a sellerâs Customer. Weâre going to push forward with sharing features in Version 1.4.3, due later this week.