llh_api

[misty folio]

👋 Welcome to your new thread!

⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1261414993811869849

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

[tiny breach]

Can you share the payment method id where this happened?

[summer sluice]

pm_1PbpSzENxjodxCKlgLpgur07 & pm_1PbpUQENxjodxCKl0yZEQKPV

they are the same card btw

[tiny breach]

afaik fingerprint should always be populated

[summer sluice]

this is all the fields I got from createPaymentMethod

this is in test mode btw

a more general question is whether that's a deterministic way to incorporate in idempotency key

[tiny breach]

Ok so I just checked with a colleague on this. We don't surface fingerprint on publishable key requests, so this is actually expected. If you were to retrieve that payment method from your server via a secret key, you'd get the fingerprint.

[tiny breach]

what do you mean? also idempotency key for what exactly?

[summer sluice]

I mean for the payment intent, we're trying to prevent double charge for the same card

in case user attempted a payment of the same card

our situation is that when we attempt to collect payment, say if there's a network issue, user reloads and try to pay with the same card again. We want to make sure we don't allow that to happen

[tiny breach]

Well you can't charge the same payment intent twice

[summer sluice]

if we attempt to create a new payment intent, anything we can use from the payment method to set the correct idempotency key?

[tiny breach]

I'm still not sure how idempotency helps here. It sounds like you may be using an older/not-recommended flow. Are you creating payemnt method in 1 request, then separately creating and confirming a payment intent all in 1 call?