Hi guys.
I’m having trouble with setting up the buy button.
I keep getting this error message.
I re-watched the video about the buy button.
Do I need to create the item first in Stripe?
Should I add Stripe’s SKU anywhere in my Google sheets?
Thanks
@eltintero Which app is this? The price seems right. Are you sure you have something in the “product_it” column for this product?
app.cancuntour.app -> La Casa -> scroll down to Surprise
Yup, I had the name of the item, now I created a Stripe product and used the SKU… but didn’t work.
@eltintero Approximately when did you try to make this purchase? We can’t find any logs regarding this on our server-side, so it may be a client-side error. Could you open your browser’s developer tools and post what is going on in the console?
patch.js:1 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. https://goo.gl/7K7WLu
t @ patch.js:1
10.30d076e2.chunk.js:2 State is missing data
e.<computed> @ 10.30d076e2.chunk.js:2
5A cookie associated with a cross-site resource at <URL> was set without the `SameSite` attribute. It has been blocked, as Chrome now only delivers cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at <URL> and <URL>.
DevTools failed to parse SourceMap: chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/sourcemaps/onloadwff.js.map
DevTools failed to parse SourceMap: chrome-extension://hgmhmanijnjhaffoampdlllchpolkdnj/js/lib/purify.min.js.map
3DevTools failed to parse SourceMap: chrome-extension://hdokiejnpimakedhajhdlcegeplioahd/sourcemaps/onloadwff.js.map
VM451:1 POST https://api.stripe.com/v1/payment_methods 402
(anonymous) @ VM451:1
(anonymous) @ shared-bfd1fd86c1517df9287bd99d198295e9.js:1
e @ shared-bfd1fd86c1517df9287bd99d198295e9.js:1
k @ controller-5b26634debd9a46990b35eb531afca74.js:1
(anonymous) @ controller-5b26634debd9a46990b35eb531afca74.js:1
value @ controller-5b26634debd9a46990b35eb531afca74.js:1
(anonymous) @ controller-5b26634debd9a46990b35eb531afca74.js:1
Promise.then (async)
createPaymentMethodWithElement @ controller-5b26634debd9a46990b35eb531afca74.js:1
(anonymous) @ controller-5b26634debd9a46990b35eb531afca74.js:1
(anonymous) @ controller-5b26634debd9a46990b35eb531afca74.js:1
Ke._respondUsingPromise @ controller-5b26634debd9a46990b35eb531afca74.js:1
Ke.handleAction @ controller-5b26634debd9a46990b35eb531afca74.js:1
value @ controller-5b26634debd9a46990b35eb531afca74.js:1
(anonymous) @ controller-5b26634debd9a46990b35eb531afca74.js:1
10.30d076e2.chunk.js:2 Error creating payment method for buy button: processing_error: An error occurred while processing your card. Try again in a little bit.
e.<computed> @ 10.30d076e2.chunk.js:2
c @ main.8c9927b3.chunk.js:1
(anonymous) @ 14.01ea86a5.chunk.js:1
l @ 10.30d076e2.chunk.js:2
(anonymous) @ 10.30d076e2.chunk.js:2
forEach.e.<computed> @ 10.30d076e2.chunk.js:2
r @ 10.30d076e2.chunk.js:2
u @ 10.30d076e2.chunk.js:2
Promise.then (async)
r @ 10.30d076e2.chunk.js:2
u @ 10.30d076e2.chunk.js:2
(anonymous) @ 10.30d076e2.chunk.js:2
(anonymous) @ 10.30d076e2.chunk.js:2
(anonymous) @ 14.01ea86a5.chunk.js:1
n.onSubmit @ 14.01ea86a5.chunk.js:1
n.onClick @ main.8c9927b3.chunk.js:1
n.onClickUnhandled @ main.8c9927b3.chunk.js:1
v @ 10.30d076e2.chunk.js:2
_ @ 10.30d076e2.chunk.js:2
(anonymous) @ 10.30d076e2.chunk.js:2
E @ 10.30d076e2.chunk.js:2
A @ 10.30d076e2.chunk.js:2
k @ 10.30d076e2.chunk.js:2
P @ 10.30d076e2.chunk.js:2
Sn @ 10.30d076e2.chunk.js:2
ce @ 10.30d076e2.chunk.js:2
An @ 10.30d076e2.chunk.js:2
On @ 10.30d076e2.chunk.js:2
Pn @ 10.30d076e2.chunk.js:2
t.unstable_runWithPriority @ 10.30d076e2.chunk.js:2
Ui @ 10.30d076e2.chunk.js:2
ue @ 10.30d076e2.chunk.js:2
kn @ 10.30d076e2.chunk.js:2
i @ 10.30d076e2.chunk.js:2That’s really interesting. It’s failing to talk to Stripe even before it touches our systems. Try disconnecting and reconnecting your Stripe account in the Buy Button configuration.
Ok. Try disabling all browser extensions or using a different browser entirely. We’re pretty sure that it’s something specific either to your environment, or your Stripe account based on activity we are seeing with other Buy Button installations.
Will do that, give me some minutes.
However when trying to pay from my phone, same issue persists.
I thought there were issues with small amounts around $1.00???
@eltintero You are going to have to ask Stripe support yourself about this. We can’t reproduce it on our end, and other users are actively processing payments with the Buy Button. Based on the error code we’re seeing, it’s possible that Stripe can’t process your specific credit card. That’s way beyond our ability to fix, and Stripe support is going to need specific card info to help you out.
Is it an issue from the card or my stripe account? What do you think?
Jesús A Vargas Espinosa-Mireles
+52 5555051571
jesusvargasem@gmail.com
@eltintero We don’t know. Please ask Stripe support instead of us. It seems that Glide is doing everything correctly and Stripe itself is not working.
I read somewhere else (here in the forum) that minimum amount was 0.5 USD.
Hola @eltintero & @Daniel_Sweet
How did you solve this problem because I’m having the same one:
I’m using the Stripe’s test card numbers to test but I don’t know if it is the problem source or something wrong is happening with my settings!!
Or must I use these test card numbers on staging instance only?.
Thanks for your help!
Any chance you have row owners in the app?
You can’t have row owners, and all data passed to Stripe needs to be stored in google sheets (nothing can be user specific or in Glide columns).
So far, I have no row owners but I can see now that we can use USC into Price field without problems.
But my problem doesn’t seem to have this problem (I think), the products are already in shopping cart, the issue happens after I press the Pay (Pagar) button which is showed automatically in this section and I can’t manipulate or configure it!
Gracias @eltintero
My problem was caused by my USC!! 
Although Glide lets you use USC into Stripe fields, when the transaction is fired, Stripe can’t find the real values and aborts all.
I don’t understand this kind of constraint. The Buy button and its process can be easier if USC can be used in this case.
