card fingerprint

[Jamin Benjamin]

Regarding the Card object's fingerprint property:

1. Does anyone use this for any reason?  I'd be interested in hearing about any clever suggestions about this...

2. Am I putting myself or my users at risk in any way by displaying this fingerprint on their account settings or payment receipt screens?

 

[Matthew Arkin]

Two uses that I know of:

1. Preventing users from saving the same card multiple times in their account.

2. Preventing fraud. If there are cards that you suspect are fraudulent or you want to blacklist a card that had previously done a chargeback against you, you can keep a database of blacklisted card fingerprints.

I can’t really answer 2. I haven’t seen of anyone displaying the fingerprint and don’t know what value it provides to the customer. 

--

Matt Arkin

Kollective Solutions

http://kollective.it

http://mattarkin.com

--
You received this message because you are subscribed to the Google Groups "Stripe API Discussion" group.
To post to this group, send email to api-d...@lists.stripe.com.
Visit this group at http://groups.google.com/a/lists.stripe.com/group/api-discuss/.

To unsubscribe from this group and stop receiving emails from it, send an email to api-discuss...@lists.stripe.com.

[Patrick Collison]

Hi Jamin,

As Matthew described, the primary intent is enable you to reason about
the underlying card and detect cases where the same card has been used
multiple times. One caveat is that fingerprints for the same card will
(intentionally) differ across different Stripe accounts.

While we'd probably recommend not showing them to customers in order
to avoid confusion, you're not running an undue risk by showing them
in payment receipt screens.

Patrick