#bouya1543
oak monolithBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- bouya1543, 1 day ago, 28 messages
celest ferry
👋 happy to help
there is a way but it would be a really expensive one
if you create x numbers of PaymentMethods for the same Payment Details (e.g. same card number) all of the Payment Methods will have the same fingerprint
then the problem becomes finding the needle in the haystack
arctic raptor
Ok thanks ! (this also leads to my next question....)
Does a duplicated payment method has the same fingerprint as the original even if it is in another account ? (i may be lazy and i could have found this with a simple request but here i am ...)
When i mean duplicate/clone, i'm obvioulsy talking about cloning it in another connected account
celest ferry
regardless on what the account is
arctic raptor
Thank you very much for answering this ! Have a nice day !
celest ferry
oh sorry
my bad
it is unique per account
ok let me circle back another time on this
so basically let's go back to your original example
so if you create a Payment Method (e.g. a card) on your platform Account A
the pm_xxx would have a fingerprint x
when you clone it to the Connected Account B
if the Account B is looking at the pm_yyy they would see the fingerprint y
whereas if you're using the Platform Account A's secret key with the Stripe-Account header to retrieve the pm_yyy you would see the fingerprint x
does that make any sense to you @arctic raptor?
arctic raptor
Yes @celest ferry thanks !
So if i understand well, i need to make the request through Platform A on account B to have the same fingerprint as Plaform A which where the original pm was declared ?
celest ferry
yes
arctic raptor
As we can go a request like await stripe.paymentMethods.retrieve( 'pm_from_account_b', {stripeAccount: 'AccountB'} );
I'll have fingerprint A ?
celest ferry
I really discourage you from doing that to be honest
celest ferry
As we can go a request like ```
await stripe.paymentMethods.retrieve(
'pm_from...
correct
but again, I don't think you should go that route
it's really expensive as a flow
arctic raptor
The goal here is not to request everytime to find the fingerprint but just to have only one fingerprint stored in our database (for fraud purposes)
celest ferry
you shouldn't store fingerprints either
there are multiple ways of achieving this
but I need to understand the use case so I could help you out more
arctic raptor
You mean to have an unique identifier per creditcard declared at Stripe? If you have an alternative to that i'm all ears
celest ferry
let's forget about the implementation for a second
arctic raptor
We need to have an unique identifier across account to detect frauds
celest ferry
when you say unique identifier for what exactly?
arctic raptor
As i have a correlation system between users, creditcards, and products
Unique identifier for a creditcard. Card XXX has been declared to user A, but user C D and E have it declared too
celest ferry
then in that case yes fingerprint is the only way to go
arctic raptor
Ok thanks ! I understand that it is costly, but as you said, this is the only way to go sadly
celest ferry
let me know if you need any more help