#dphantom_api
1 messages Β· Page 1 of 1 (latest)
π 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/1372867614799564891
π Have more to share? Add more details, code, screenshots, videos, etc. below.
What code do you use that throws that error?
Should be this one function ExpressCheckoutSection({
onPaymentResult,
clientSecret,
}: {
onPaymentResult: (paymentIntent: PaymentIntent | null, error?: { message: string }) => void;
clientSecret: string | null;
}) {
// ...
const expressCheckoutOptions: StripeElementsOptions['expressCheckout'] = {
buttonTheme: { applePay: 'black', googlePay: 'black' },
emailRequired: true,
shippingAddressRequired: false, // Sie setzen dies hier
billingAddressRequired: false,
};
return (
// ...
<ExpressCheckoutElement
onConfirm={handleExpressWalletConfirm}
options={expressCheckoutOptions} // Diese Optionen werden verwendet
/>
// ...
);
}
this is the one for create payment intent:
When is the error thrown though? When you click something? Send a request?
Do you have the actual req_xxx ID where the error is returned
Yes req_in4fiC0RX64RwP
That request returned a 200 (success)
I guess then its before or after i click the paypal button
Because in dev tools it gives me a 400 error:
Request URL
https://api.stripe.com/v1/elements/express_checkout
Request Method
POST
Status Code
400 Bad Request
Remote Address
34.240.123.193:443
Referrer Policy
strict-origin-when-cross-origin
access-control-allow-credentials
true
access-control-allow-methods
GET, HEAD, PUT, PATCH, POST, DELETE
access-control-allow-origin
https://js.stripe.com
access-control-expose-headers
Request-Id, Stripe-Manage-Version, Stripe-Should-Retry, X-Stripe-External-Auth-Required, X-Stripe-Privileged-Session-Required
access-control-max-age
300
cache-control
no-cache, no-store
content-length
263
content-security-policy
base-uri 'none'; default-src 'none'; form-action 'none'; frame-ancestors 'none'; img-src 'self'; script-src 'self' 'report-sample'; style-src 'self'; worker-src 'none'; upgrade-insecure-requests; report-uri https://q.stripe.com/csp-violation?q=xgcX0t7PQB8X8Tw9Tg68tjyiXLG4cgsGujZtNrkddbuNW_0D8xf8g02b91ugdjQIMGIyXAW3cO9-j3O2
content-type
application/json
date
Fri, 16 May 2025 09:28:36 GMT
idempotency-key
6fa4c18d-1935-43b4-b02a-c6823b57797e
original-request
req_qt1eDIdKxcWZyi
request-id
req_qt1eDIdKxcWZyi
server
nginx
strict-transport-security
max-age=63072000; includeSubDomains; preload
stripe-version
2025-03-31.basil
timing-allow-origin
https://js.stripe.com
vary
Origin
x-stripe-priority-routing-enabled
true
x-stripe-routing-context-priority-tier
api-testmode
x-wc
ABGHI
:authority
api.stripe.com
:method
POST
:path
/v1/elements/express_checkout
:scheme
https
accept
application/json
accept-encoding
gzip, deflate, br, zstd
accept-language
de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7,fr;q=0.6
content-length
281
content-type
application/x-www-form-urlencoded
origin
https://js.stripe.com
priority
u=1, i
referer
https://js.stripe.com/
sec-ch-ua
"Chromium";v="136", "Google Chrome";v="136", "Not.A/Brand";v="99"
sec-ch-ua-mobile
?0
sec-ch-ua-platform
"macOS"
sec-fetch-dest
empty
sec-fetch-mode
cors
sec-fetch-site
same-site
user-agent
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36
--
15 / 31 requests
7.7 kB / 16.2 kB transferred
0.3 kB / 324 kB resources
{,β¦}
error
:
{code: "parameter_missing", doc_url: "https://stripe.com/docs/error-codes/parameter-missing",β¦}
{
"error": {
"code": "parameter_missing",
"doc_url": "https://stripe.com/docs/error-codes/parameter-missing",
"message": "Missing required param: is_shipping_required.",
"param": "is_shipping_required",
"type": "invalid_request_error"
}
}
req_qt1eDIdKxcWZyi is the one
for some reason i cant find this one: req_qt1eDIdKxcWZyi
Yeah it's an internal call so it's not in your Dashboard but it's there in the JSON dump above
Okay nice that you found it
Looking at it now
Thanks for your quick helpo
This only happens for the PayPal button, right?
Sadly not, so no express button is working after all, they behave a bit different tho, depending on the provider
What other errors do you see?
Can you try and omit the shippingAddressRequired param from here? Just testing something
Sure one second
When i test it with bancontact, i authorize it and get again an problem with the address, will reproduce
Bancontact? That's not a wallet in the Express Checkout Element?
Yes, this one was when i tested out a different one than Card, sorry
same issue
I thought we were talking just about the Express Checkout Element? Not Payment Element, where you'll see Bancontact, card, etc
Yes this request is only about the express checkout elements, sorry i mixxed this up, in the final product i only want to use express and "nomral" card
Did you try this? The defualt value is false so should have no impact
That param directly maps to the is_shipping_required param internally in the error so trying to figure out why it's thrown
Let me check, please give me 1 min
I removed shippingAddressRequired but it behaves the same
π taking over for my colleague. Let me catch up.
now i noticed something, if i put it on true
Paypal is no longer closing right away but opening the correct sandbox popup
ok so it's fixed now?
Sadly not, it just opens
But when i try the payment with LINK for example, it behaves again with an error
just give me a couple of minutes to read over the thread
Sure
ok it seems that we have an issue from our side, I was able to reproduce the issue on my end
Okay thanks for letting me know, so my setup should be correct?
we need to investigate this internally before we do anything
if you want an update I can send you a DM to directly file a ticket and we will update you as soon as we have something concrete to share
Hello @fading viper, we have sent you a direct message, please check it at https://discord.com/channels/@me/1372882295958011908
- πThe message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
Alright sounds good thanks, do you got ideas for a workaround? I was wondering because for example the woocommerce stripe Wordpress plugin uses express checkout buttons as well and they seem to work fine
unfortunately you would need to wait until we mitigate this
Alright, thanks π