#Quinnzuo

1 messages · Page 1 of 1 (latest)

noble falconBOT
craggy tree
gray valve
#

that's no error occurred in the dashboard lol so strange.

#

but we can received the first payment and second 'saved card' payment

#

also in my log, I can see it successfully called up the payment intent regard for that. but in reality, customer can not call the payment intent and get the showing error above.

craggy tree
#

It sounds like they faced some error on frontend when communicating to your backend server, before sending request to Stripe (since we found no log)

#

I would recommend checking your server log for the error message your customer reported

gray valve
#

we checked frontend already, that is not error in the frontend server. is it any chance to work aroung with Pluhing.

craggy tree
#

Sorry I don't follow. What is "frontend server"?

#

And "requestPayment:fail[Paymentstripe:51]There was anunexpected error -- try again in a fewseconds" should be coming from your codebase, doesn't it?

gray valve
#

Sorry my confusion. Because we built in the uni-app framework. When this error appeared, we check from our backend codebase, that is no error. So we suspect that something happened in the front-end, but it is still nothing happened in the front-end too. the error respond doesn't existed in my codebase

craggy tree
#

Hmm okie. Not familiar with uni-app, but does it use a Stripe SDK?

#

And which SDK?

gray valve
#

The stripe SDK in uniapp is the encapsulated stripe SDK lol

craggy tree
#

Can you elaborate exactly how your integration looks like?

#

What Doc have you followed?

gray valve
#

Sure. 1. we are following this doc https://en.uniapp.dcloud.io/tutorial/app-payment-stripe.html 2. We set up the customized payment element page (because the saved card button doesn't appeared in stripe official payment element) for customer to choose they purchase or not; If they not save card and pay successfully, customer payment method will be saved in our backend. When customer implement the next pruchase, they still call the same UI page 3. But if the customer save the card, when they implement the next purchase, they can see the listed card in the payment intent page as I showing below, they can successfully process the payment with this function 4. a few hours or even shorter, when they try to call up the third purchased which is supposed to call up the listed card, appear error ....

craggy tree
#

I see. It looks like a wrapper around Stripe PaymentSheet component

#

But uniapp owns this integration and Doc

#

The error seems to come from their integration logic

#

since we have confirm it's neither on your server log, nor your request history to Stripe