#clydstrife_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/1308697011733663814
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
So I disabled the Link button when I created the cardNumberElement could this be the issue?
const cardNumberElement = elements.create('cardNumber', {
style: style,
disableLink: true
});
This is the Payment Request Button that the email is referring to : https://docs.stripe.com/stripe-js/elements/payment-request-button. We recommend you migrate to the Express Checkout Element which is https://docs.stripe.com/elements/express-checkout-element.
There's a migration guide mentioned here : https://docs.stripe.com/elements/express-checkout-element/migration
even if the goal of the implementation is to save cards for later charging?
I'm not taking payments for this one, just need to save the card information into stripe for later charging.
even if the goal of the implementation is to save cards for later charging?
yes, we still recommend you migrate to Express Checkout Element
Looking at the migration guide it looks like it only show's saving the card during payments. My current Implementation is following this guide https://docs.stripe.com/terminal/features/saving-cards/save-cards-directly?terminal-sdk-platform=js which again align's with my goal of saving the card directly with no charge invovled (though the guide is for terminals I applied the same logic using Stripe JS), using setupIntent's and I use Stripe Elements for the cardNumber, cardExpiry, and cardCvc. Do you have a similar guide for that in Express Checkout? can't seem to find it.
The logic is similar, if you're having trouble, we can help advise. At a high level, instead of using mode: payment, you would use mode: setup, and instead of using PaymentIntents, you would use SetupIntents. In short, as long as you're using Payment Request Button, we recommend you migrate to the Express Checkout Element.
Ok, additional question If I use Stripe Checkout using the mode: setup this still aligns with my goals of Save payment details to charge customers later correct?
yes, that works too
Ok great thanks for the information! I'll tinker around with Express Checkout Element for now is there an implementation guide for it? The doc's kinda seem vauge on how use the Express Checkout Elements.
hmmmm, we don't have a specific guide for saving a payment method with the Express Checkout Element. It's really this flow : https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web, but modified to use an Express Checkout Element instead