#ced-sofort
1 messages · Page 1 of 1 (latest)
Hi there 👋 no, and Sofort is single-use so blocking duplicates would block customers from paying with it more than once.
Well I do not want to block duplicates but detect if it is the same customer so he can not have the new customer promotion.
You won't be able to accomplish this from the payment method information.
Is there another way? I plan to use the fingerprint on card and SEPA.
Not that I'm aware of. You can reference the Customer object (if you're reusing those) or add some form of customer tracking on your end.
I have no reliable information to group users under the same Customer object without a fingerprint for SOFORT.
To track users I will need to request acceptance to comply with GDPR. And of course cheaters will not accept.
By the way it is a little bit strange to have fingerprint for SEPA and not SOFORT, both are linked to a bank account.
SEPA is reusable, like card payments, which is why it makes sense to have a fingerprint for it.
I do not see why it should be only on reusable?
Because fingerprint is intended to allow the identification of duplicate payment methods so you can avoid ending up with multiple payment methods that all map to the same card/bank account. However, for single-use payment methods you need multiple copies if you want to process more than one payment.
Having a fingerprint on single-use payment methods do not prevent to have multiple copies but it will help identify duplicate customers.
Will it though? Multiple people may have access to the same bank account.
Indeed but this already exist with SEPA.
My goal is not to merge customer object but to know that they share the same source of payment so they are not new customers.
Gotcha, so you may not want to accept Sofort then as you won't be able to achieve that with the functionality currently available.
Do you think it may become available in the future?
Not that I'm aware of, but I'm submitting it as an enhancement request.
OK thanks