#slendie_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/1334528598475800646
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
What do you mean by 'changes don't reflect on my site'? What are you expecting to see versus what do you see?
Hi Guys, i have put SEPA direct debit has one of the payment method but it still doesnt show on my checkout payment
The button doesn't adjust to the new button type
Let me show you an example...
I set the google pay buttont type to "order". It should now say "Order with Google"
Do you have a link to the checkout page so we can take a look?
Also can you share the complete client-side code you're using to initialize Elements and the Express Checkout Element?
I'm running my site locally, so sadly I can't share a link to the site
Express Checkout Element requires https though
But here's the code for my express checkout element
<ExpressCheckoutElement
options={{
paymentMethods: {
googlePay: 'always',
applePay: 'always',
},
buttonHeight: 40,
layout: {
overflow: 'never',
},
buttonType: {
googlePay: 'order',
},
}}
onConfirm={onConfirm}
onShippingAddressChange=. {onShippingAddressChange}
onShippingRateChange={onShippingRateChange}
onClick={onClick}
onCancel={onCancel}
onLoadError={onLoadError}
onReady={onReady}
We have a local environment set up to accommodate all that
Hey there, just taking over for duchess as they need to step away
Hmm this does work for me and switch to "Order with G Pay" when i test it
๐ค
Are those options params provided via a variable, or hardcoded props in the component?
The button type and payment methods parameters are hardcoded
Very strange, it's actually working for me now too! But it seems to be inconsistent, at least in my local environment
Oh that's pretty odd
I wonder if its related to the logged-in state of google pay
since you're using always
Yeah perhaps. ut all good for now I guess
One more question - can you confirm the conditions we need to meet in order to show the paypal button via stripe express?
You need to be using a qualified account generally, and not using setupFutureUsage -- saving PayPal for later is only supported ia payment element
It's also recommend to disable phone number collection, as the paypal api does not allow us to guarantee that
https://docs.stripe.com/payments/paypal/paypal-button
So if you require phone collection, paypal can sometimes be disabled to avoid scenarios where you might not get a phone number
What is a "qualified account"?
In a country where paypal is supported as a payment method: https://docs.stripe.com/payments/paypal
see business locations here
briefly: in europe
(eg, it is not supported for a US account)
And that's based on our business address?
We do have one account with a UK address, and the button still isn't shpwing up...does the buyer need to be located in Europe too?
It's the country of your stripe account, yes based on your business location. if you have paypal as an option in your payment method settings, you should be fine.
No, that should not be the case. It supports customers worldwide.
If you open your developer tools, when the elements are beign initialized you should see a request to /v1/elements/sessions -- can you open that request and get the request-id from the response headers?
I see paypal in the payment method settings, yeah
But...button isn't showing ๐
Definitely using the right merchant account
Did you find that request ID?
๐คฆ
sorry, i missed this early on
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
You're specifying payment_method_types in your elements initialization, not using dynamic payment methods
In order for paypal to be including using this technique, you need to add it here
Otherwise you can remove payment_method_types to use let them be calculated automatically from your settings
Oh so I need to add "paypal" to that types array?
yep
Nice! No problem, glad we got you sorted out ๐
One more question...
If I hardcode "paypa" in that array, might is cause any unforeseen issues down the line?