mathias-henriksen_error | Stripe Developers | Page 1

brazen nexusBOT May 14, 2025, 11:57 AM

#

👋 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/1372181037865766983

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

#

thorny harbor May 14, 2025, 11:59 AM

#

👋 happy to help

#

would you mind sharing the request ID that failed?

#

https://support.stripe.com/questions/finding-the-id-for-an-api-request

Finding the ID for an API Request : Stripe: Help & Support

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

elder goblet May 14, 2025, 12:01 PM

#

Yes, I will see what I can find 👍

#

I cannot see any failed requests related to the attempted purchase, but this is the last request related to the customer that got the PayPal issue: req_v73inK9RNPzPSM

thorny harbor May 14, 2025, 12:10 PM

#

where did you see that error message at?

elder goblet May 14, 2025, 12:11 PM

#

under Developers -> Logs in the Stripe Dashboard

thorny harbor May 14, 2025, 12:11 PM

#

I'm not talking about req_v73inK9RNPzPSM I'm talking about

    "error": {
        "message": "Sorry, something went wrong. We've already been notified of the problem, but if you need any help, you can reach us as support.stripe.com/contact."
        "type: "api_error"
    }
}

elder goblet May 14, 2025, 12:14 PM

#

ohh yeah, that shows up when clicking "Agree & Continue" in PayPal

thorny harbor May 14, 2025, 12:15 PM

#

oh I see now

#

is this a new issue? or have you been seen this for a period of time?

elder goblet May 14, 2025, 12:19 PM

#

It is new. PayPal is currently working in production where we do subscription creation on the server and payment confirmation on the client.
In our new solution we do subscription creation and payment confirmation on the server, and then do stripe.handleNextAction on the client. This is when PayPal stops working

thorny harbor May 14, 2025, 12:21 PM

#

would you mind redoing a test now?

#

just wanted to check whether this is still happening or just an intermitent thing?

elder goblet May 14, 2025, 12:27 PM

#

Okay, I just have to set up an account to test

#

alright I tried to pay now and got the same error

thorny harbor May 14, 2025, 12:32 PM

#

ok taking a look thanks for confirming

elder goblet May 14, 2025, 12:33 PM

#

great, thanks

brazen nexusBOT May 14, 2025, 12:48 PM

#

short hollow May 14, 2025, 12:58 PM

#

Hi there 👋 jumping in as my teammate needs to step away. I just want to make sure I'm understanding correctly. You're using handleNextAction from Stripe.js after confirming the intent server-side?

Do you have the ID of a payment that you were processing when this happened? Like the ID of a Payment Intent or related Invoice object?

elder goblet May 14, 2025, 1:01 PM

#

Hey! Yes here is the related payment intent: pi_3ROZwXJxfuw0gUii0L65DbOP

#

Invoice: in_1ROZwXJxfuw0gUiiu2DgYvlN

short hollow May 14, 2025, 1:06 PM

#

I see this is all in livemode, are you seeing this same issue in testmode or your sandbox account?

elder goblet May 14, 2025, 1:08 PM

#

No when I try to use paypal in testmode I don't get redirected to paypal, the payment just goes through

short hollow May 14, 2025, 1:13 PM

#

Gotcha, thank you for that insight. Unfortunately, that makes it hard for me to try to test and reproduce, but it does give me some insight to approach this differently.

elder goblet May 14, 2025, 1:14 PM

#

Alright nice

short hollow May 14, 2025, 1:20 PM

#

And to confirm, are you using handleNextAction from Stripe.js, or are you redirecting your customers to the URL we provide in the response to the confirmation request?

elder goblet May 14, 2025, 1:23 PM

#

The former, like this:

const onCreateSubscriptionSuccess = async (createSubscriptionData: StripeCreateSubscriptionResponse) => {
if (!stripe) {
throw new Error();
}

if (createSubscriptionData.status === "requires_action") {
  const { error, paymentIntent } = await stripe.handleNextAction({
    clientSecret: createSubscriptionData.clientSecret,
  });
  if (error) {
    throw new Error(error.message);
  } else {
    onPaymentSuccess(createSubscriptionData.subscription);
  }
} else {
  onPaymentSuccess(createSubscriptionData.subscription);
}

};

#

I tried again now and it worked. Did you do anything?

Before I tried I changed the return_url to the same URL that I am using to test the integration. So, unless it was fixed from your side it seems that the domain of the return_url needs to be the same as the one you are redirected from. In that case, this info would be handy to have in the error message 😅

short hollow May 14, 2025, 1:34 PM

#

I did not change anything, and I agree if that is a requirement it should absolutely be documented.

elder goblet May 14, 2025, 1:35 PM

#

Well, at least it seems to be working now! Thanks for your time 😄

short hollow May 14, 2025, 1:36 PM

#

I'm glad to hear it's working again, and I really appreciate you sharing your firndings! We're going to keep looking into this no our side and see if our docs need to be updated.

#mathias-henriksen_error