#taylor-source-fingerprint

1 messages · Page 1 of 1 (latest)

vernal haven
#

the fingerprint can change because for example a card can be automatically updated after it's renewed by the bank. It's based on the card number so if the card number changes, so would the card fingerprint

proven notch
#

what if the payment source is a bank account?

vernal haven
#

same, the underling account number/routing number could be automatically updated so that could change, though that's a lot rarer

proven notch
#

If the fingerprint changes, is there a webhook we could listen to?

vernal haven
#

there are a variety of events depending on your integration. If you're using ACH debit it'd be customer.source.updated

proven notch
#

Yeah we're seeing bank account fingerprints update and the account number/routing number are the same

#

Are there any other pieces of data besides routing/account number that are factors for a fingerprint?

vernal haven
#

you can't know the account number at all in the API

#

it might be easier to start from a clear example, you seem to have a concrete question behind the hypothetical one

proven notch
#

req_4NaELdU2lbxRhv

#

That response shows an id of ba_1IPVtxLMHLcGMW3QLH09xrUD and a fingerprint of V800nnkhlbZH9PUL

#

When I look at the fingerprint for that same resource today, it is: P8DiSIfG53KSwCsX

proven notch
#

yep i see it

vernal haven
#

so that's the event you want to listen for, that's what I explained right?

proven notch
#

yep! that squares me away.

vernal haven
#

it's rare that the fingerprint changes without something else changing

#

but imagine if their account number was 111112222 and the bank moved them to 333332222 then the last 4 are still 2222 so in the API nothing changes, but the fingerprint calculated on the underlying account number is different

proven notch
#

We are seeing this happen a handful of times with bank accounts, seems weird

vernal haven
#

sometimes it's people moving to a higher threshold with their banking and they have logic to keep "same number but starts with an extra 1" or something

#

but agreed that's weird, I've rarely seen this

proven notch
#

I suppose the more volume and transactions you process, the more you see weird edge cases.

#

🤷‍♂️

vernal haven
#

yeeeeep

#

thanks for the examples that really helps

proven notch
#

Sure thing. We know what to do now. Thanks for the help.