I am using payment workflow -> Collect Users CC Card information.
I thought that would charge the customer, but it doesnât, that just wants to save the info that was input so it looks for a customer on StripeâŚwhich I didnât haveâŚthat was the error message.
BUTâŚI need to charge a customers debit card not just save the infoâŚI cannot see how to do this?
Yes the error message was from stripe telling me that the customer doesnât exist in live but it can find it in test, but I am accessing Strip via LiveâŚwhich is correct as I am testing my Live App.
Charge current user would charge the user that is logged inâŚI donât want to do this.
My App allows different sellers to login in to their account and sell products to people at fairs etc, so the person being charged is not the seller but will be customersâŚdoes that make sense?
Just change the email to something else. Charge current user doesnât require the user to be logged in. But you need an email to charge someone, itâs a requirement from stripe.
I have read the Stripe documentation and I have implemented the Connect feature.
So my âUserâ Logins inâŚthey are asked to Connect to their Stripe account via the workflow -> Register the User as a SellerâŚafter they have Signed Up/Logged into Stripe, they are redirected too my StripeAccess Page which in my settings is API Tab I have set StripeAccess as my Login Page for OAuth Redirects.
The documentation says that after I have done Register the user as seller there is one other thing that need to be done for Standalone connection
Using the code parameter, you should make a POST request to our access_token_url endpoint
curl https://connect.stripe.com/oauth/token
-d client_secret=sk_test_xDROamzZwpe2kRQ3KSOSOzS4
-d code=AUTHORIZATION_CODE
-d grant_type=authorization_code
Stripe will return a response containing the authentication credentials for the user:
{
âtoken_typeâ: âbearerâ,
âstripe_publishable_keyâ: PUBLISHABLE_KEY,
âscopeâ: âread_writeâ,
âlivemodeâ: false,
âstripe_user_idâ: USER_ID,
ârefresh_tokenâ: REFRESH_TOKEN,
âaccess_tokenâ: ACCESS_TOKEN
}
Youâre done! The user is now connected to your platform.
Bubble handles that on your behalf. What you need to do is have your venders go through a âregister as a seller actionâ, and then when you use a charge user action, you can pick âthe payee is another userâ, and pick which vendor should get the payment.
SoâŚhave moved forward but still got an issue, it might be a page flow thing maybe!?
I am going to explain the App flow just so that there is no confusion and tell you the issue.
âUserâ Logins
âUserâ Registers as Seller with Stripe
Stripe redirects to StripeAccess Page with is the OAuth redirect
âUserâ Clicks Continue and gets taken to the Apps Welcome Page
âUserâ Clicks âAdd New Orderâ and gets taken to New Order Page
âUserâ Selects a âCustomerâ from dropdown (previously added onto their account)
âUserâ selects products the customer wants to order
âUserâ Clicks Submit and gets forwarded to the Order Summary Page
âUserâ Clicks Submit on Order Summary Page and the Stripe payment pops-up
âUserâ fills in the Customers card details and submits payment.
At this point I get an error saying
âSorry, this seller cannot accept payments right now due to a temporary error. Please try again laterâ
The âUserâ then gets an email from Bubble as below
Hello,
You are trying to sell something but are not registered as a seller through Stripe.
Please go to the link below to register.
Thank you for your selling with us!
The team
The link takes me to the same page as âRegister user as Sellerâ to connect to Stripe accountâŚuser did this already, so confused as to why it cannot make payment
Itâs probably because the payee of the transaction is the wrong user. Try to use the debugger (see our email of yesterday) to confirm itâs the right user, the message youâre getting is pretty explicit.
Payee is correct, is the currently logged-in userâŚits also them that gets the email that mentioned in my previous post, it is the same email address that they did step âregister user as a sellerâ with
Then check the register as a seller workflow, because stripe is saying the user isnât registered. Check with your stripe console to make sure the user is a seller. The issue here is a workflow issue, not a bubble feature one.
Yep does look like its a workflow issueâŚas I canât see what Bubble does in the background its hard to figure out.
When the use Registers as a seller, once they connect their stripe account they are redirected back to my appâŚmy app needs to hold on to the authentication credentials to use later onâŚdoes Bubble do this in the background?
The URL that the email asks me use to âRegister User as a Sellerâ is https://connect.stripe.com/oauth/authorize?response_type=code&client_id=ca_6yu1icPsPCTyg6dxRSGfVjwH1Az80WlC&
scope=read_write&state=%7B%22nextURL%22%3A%22https%3A%2F%2Fbubble.is%2Fsite%2F4evertest%2Fversion-test%22%2C%22
user_id%22%3A%221441285454619x635236654896289200%22%2C%22appname%22%3A%224evertest%22%7D&
stripe_user%5Bemail%5D=vpatel%40znazzymedia.com&
stripe_user%5Burl%5D=https%3A%2F%2Fbubble.is%2Fsite%2F4evertest%2Fversion-test&stripe_user%5Bbusiness_name%5D=4evertest
The URL my app uses to do the same thing is https://connect.stripe.com/oauth/authorize?response_type=code&client_id=ca_6yu1icPsPCTyg6dxRSGfVjwH1Az80WlC&
scope=read_write&state=%7B%22nextURL%22%3A%22https%3A%2F%2Fbubble.is%2Fsite%2F4evertest%2Fversion-test
%2Fstripe_registration%3Fdebug_mode%3Dtrue%26resume%3D1442495825619x206%22%2C%22
user_id%22%3A%221441285454619x635236654896289200%22%2C%22appname%22%3A%224evertest%22%7D&
stripe_user%5Bemail%5D=vpatel%40znazzymedia.com&
stripe_user%5Burl%5D=https%3A%2F%2Fbubble.is%2Fsite%2F4evertest%2Fversion-test&stripe_user%5Bbusiness_name%5D=4evertest
Can you post a screenshot of your workflow that both register the user as a seller and charge the (other user). We have quite some apps that use these functions, so things work on the Bubble end.