#ulrike_68194
opal warren
zinc musk
As far as I know we do not support that, but I am double checking with my colleagues and will get back to you
wicked field
hi! yeah I don't think we support that, thanks for the pointer to PaymentCardVerificationRequest, as far as I can see we control that in the SDK and it can only be .saveCard right now
so it's a feature request, I'd suggest writing to https://support.stripe.com/?contact=true with the context or speaking to any Stripe sales etc contact you have so the feedback can be flagged.
true mica
Thanks a lot! Will do!
wicked field
but in general at a higher level Terminal supports charging and saving a card for future charging, I haven't heard of this use case (read the card to lookup something based on its details) just yet so it's not something we have specific docs or approaches for
true mica
Yes, we use the save card user flow and that works well. But we also support checking an account. We use it for account lookup and checking the balance. At the time the customer tap their card, we don't know whether they actually have an account. We don't want to bother them with a consent dialog or show "Save Card" in the display.
In that particular use case the physical card becomes more like a security token for identity verification.
wicked field
I'm curious how that works, how do you as a merchant check someone's bank balance just from the card number?
true mica
It's not a bank balance. We support borrowing reusable items. Checking the balance in our case means, checking whether they have anything borrowed and when they need to return it.
wicked field
I see, so it's more like you use their PAN as an ID to lookup something in your database.
true mica
Exactly! It's really about convenience. Pulling out a card and holding it against a reader is much quicker and less error prune than typing or telling someone for example an email address. It's also a a verification compared to just an email address.
All we need is the fingerprint associated with the card.
wicked field
Fair enough. Not sure that's a use case we really support or consider, Terminal is explicitly a payments solution I would say and the ability to read a card is in service to that rather than a fully independent feature in itself
you can get the fingerprint via reading the PaymentMethod normally anyway, I think
true mica
Yes, that's what I'm using for the initial borrowing. There we read the card, save it and also keep the fingerprint on record. This happens every time the borrow and that's fine. The second use case, comes afterwards, where we need to lookup the account. I just looking for ways to make it even quicker. No consent screen and no "Save Card" display. Ideal would be a "Looking Up Card" or so. Not sure what Apple will display when "lookUp" is used. But I assume they'll change the display.
I'll reach out via the contact form and see that it can be filed as a feature request.