#hendie_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/1262754134713438381
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
more complete code:
const elementsGroupOptions = {
mode: 'payment',
amount,
currency,
};
const paymentElementOptions = {}
if (isForFutureUsage) {
elementsGroupOptions.setup_future_usage = 'off_session';
}
if (creditCardsOnly) {
elementsGroupOptions.payment_method_types = [
'card'
];
paymentElementOptions.wallets = {
applePay: 'never',
googlePay: 'never'
}
}
stripeFormState.elements = stripeFormState.stripe.elements(elementsGroupOptions);
const paymentElement = stripeFormState.elements.create('payment', paymentElementOptions);
according to the docs, the only wallets you can disable are applePay and googlePay. It doesn't mention Link.
Hey there, offering Link in your payment element is controlled in your dashboard settings:
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Use the overflow "..." menu and choose the integrations where Link will be used
Must say that is a rather obscure place to look for it. Any documentation on this?
In the Link docs here: https://docs.stripe.com/payments/link/payment-element-link
The default Payment Element integration includes a Link prompt in the card form. To manage Link in the Payment Element, go to your payment method settings.
so why can one control applePay and googlePay from the API, and not Link. It would be REALLY nice if you could be consistent in your implementations!
I don't disagree. We do try to bring things together as much as possible, but there's a balancing act with avoiding breaking changes + creating two ways to do the same thing.
thanks anyway
From a "new feature" perspective it would be preferable that you don't enable new features by default. This has caused our (new) AU merchant to get all upset because they are being presented with something they didn't ask for (yet). I apreciate that you want to push new features, but this kind of surprise is not acceptable.
Please convey that to your product team.
I'll share that feedback ๐