alex_best-practices | Stripe Developers | Page 1

kindred plankBOT Apr 14, 2025, 10:00 PM

#

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

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

#

paper whale Apr 14, 2025, 10:01 PM

#

Hi there

blissful sequoia Apr 14, 2025, 10:01 PM

#

hello

#

event id of a recent payment method collection: evt_1RDuXPBb49XQ2DGya693zTAl

paper whale Apr 14, 2025, 10:02 PM

#

That event payload contains a PaymentMethod object; I see the fingerprint there, too

blissful sequoia Apr 14, 2025, 10:03 PM

#

yes, however I didn't see it in my client side code, which is why I was asking here.

#

I would expect this step to have the fingerprint via paymentMethod.card

const { paymentMethod, error: createPaymentMethodError } =
    await stripe?.createPaymentMethod({
      elements,
    });

#

and for that fingerprint to be the same whether or not the payment method is of type card or card_present

paper whale Apr 14, 2025, 10:12 PM

#

Got it, okay. A couple of things:

Using createPaymentMethod is an older integration flow. We now recommend using ConfirmationTokens instead: https://docs.stripe.com/payments/payment-element/migration-ct
Retrieving PaymentMethod details can only be done server side. This can't be done with a Publishable Key

blissful sequoia Apr 14, 2025, 10:13 PM

#

ok perfect that clarifies then why it wasn't there, I will add the step server side and consult that doc to assess the lift for updating our integration

paper whale Apr 14, 2025, 10:14 PM

#

The fingerprint should be the same as long as the PaymentMethods exist in the same account

kindred plankBOT Apr 14, 2025, 10:15 PM

#

blissful sequoia Apr 14, 2025, 10:15 PM

#

ok

#

Does this also apply to Setup Intents?
"Instead of calling stripe.createPaymentMethod, call stripe.createConfirmationToken to create a ConfirmationToken object. Pass this ConfirmationToken to the server to confirm the PaymentIntent."

paper whale Apr 14, 2025, 10:16 PM

#

Yep!

blissful sequoia Apr 14, 2025, 10:17 PM

#

ok cool, yeah I see this section now about setup future usage:
https://docs.stripe.com/payments/payment-element/migration-ct#conditional-options

#

I realize it's good to stay up to date, but it sounds like this confirm token is there to help with shipping information. Is there anything else I should be aware of with regards updating? Is there a deprecation date for createPaymentMethod?

#alex_best-practices