#nina_error

1 messages · Page 1 of 1 (latest)

cedar pastureBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1437623907749199923

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

brave atlas
#

Hi! Do you have the request ID for the confirmation attempt?

waxen jolt
#

No, I can't find the comfirmation request in the dashboard

#

I check the transaction list, found there is incomplete one, from the log I just found the create intent log, but when we invoke the confirmPayment, it response the error No such payment_intent: 'pi_3SS2kEH1KHPZelP40jAbEon0', But I can't find the confirm request in the log

brave atlas
#

You are confirming this on the backend or frontend?

waxen jolt
#

frontend

brave atlas
#

This payment intent belongs to acct_17NY8sH1KHPZelP4. Are you using the publishable key for acct_17NY8sH1KHPZelP4?

waxen jolt
#

Yes

#

I just wonder why I can't find the confirmation request log

brave atlas
waxen jolt
#

No i don't use it

brave atlas
#

Can I get the last few digits of the publishable key you're using?

waxen jolt
#

JKFrprzLW2C7N2Sxe

brave atlas
#

I see your account has 2 publishable keys. Does using the other one help? Could you also provide your code for confirming the payment intent?

waxen jolt
#

try {
const returnUrl = checkoutHashKey
? ${window.location.origin}/checkout/stripe/return?checkoutHashKey=${checkoutHashKey}
: ${window.location.origin}/checkout/stripe/return;
const result = await stripe.confirmPayment({
elements,
clientSecret,
confirmParams: {
return_url: returnUrl,
payment_method_options: {
card: { setup_future_usage: 'off_session' },
},
payment_method_data: {
billing_details: {
name: ${state.checkoutInfo.shippingFirstName} ${state.checkoutInfo.shippingLastName},
email: state.checkoutInfo.email,
phone: state.checkoutInfo.phone,
address: {
line1: billing.address_line1,
line2: billing.address_line2,
city: billing.address_city,
state: billing.address_state,
postal_code: billing.address_zip,
country: CountryUtils.getCountryById(billing.address_country)?.code,
},
},
},
},
redirect: 'if_required',
});

#

I use the another one to search for the confirm request in the log, I also can't find it.

#

This issue doesn’t happen consistently — I found that some of the incomplete transactions were caused by this.

brave atlas
#

I use the another one to search for the confirm request in the log, I also can't find it.
What do you mean by this?

waxen jolt
#

I use another account to search for the confirm request in the log

brave atlas
#

Give me a moment to check.

brave atlas
#

I am unable to replicate the issue. Do you have a screenshot of what you see when you attempt to confirm the payment intent?

waxen jolt
#

Is it possible to get the confirmation log?

#

What’s strange is that I can see the result of the confirmPayment call, but I can’t find the log for the confirmation request itself.

brave atlas
#

I believe the confirmation request is not being created because the account that is confirming the intent is not the account that the intent belongs to.

#

Could I get your help with the screenshot?

waxen jolt
#

What screenshot? I can't reproduce it.

waxen jolt
brave atlas
#

The account confirm the intent will depend on the publishable key you are using. The error that you get usually indicates a Connect authorization issue or using the wrong publishable key. You will need to verify on your end that you are using the correct publishable and don't have any Stripe account header.

waxen jolt
#

Thank you. const returnUrl = checkoutHashKey
? ${window.location.origin}/checkout/stripe/return?checkoutHashKey=${checkoutHashKey}
: ${window.location.origin}/checkout/stripe/return;
const result = await stripe.confirmPayment({
elements,
clientSecret,
confirmParams: {
return_url: returnUrl,
payment_method_options: {
card: { setup_future_usage: 'off_session' },
},
payment_method_data: {
billing_details: {
name: ${state.checkoutInfo.shippingFirstName} ${state.checkoutInfo.shippingLastName},
email: state.checkoutInfo.email,
phone: state.checkoutInfo.phone,
address: {
line1: billing.address_line1,
line2: billing.address_line2,
city: billing.address_city,
state: billing.address_state,
postal_code: billing.address_zip,
country: CountryUtils.getCountryById(billing.address_country)?.code,
},
},
},
},
redirect: 'if_required',
}); My comfirmPayment code is any problem.

brave atlas
#

The code looks fine. You need to ensure that the clientSecret is for the correct payment intent created on the account for which you are using the publishable key.

cedar pastureBOT
#

⛔️ Stripe developers have stepped away for a short while

Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.