#newb1
1 messages · Page 1 of 1 (latest)
Hi! What's the question?
hey, first question is how is the data passed from nfc to my account
if i build a checkout for it, isn't that going to force me to create a product with a price, thus making it a payment only?
the docs seem to indicate that's what nfc reader requires
whereas an nfc reader isn't actually processing a transaction, it's just grabbing data
i'm referring to the nfc technology itself
like i could just use any nfc device to grab the data
passing it to stripe is a separate function
am i explaining my question clearly enough
this is what i'm talking about, stripe's nfc readers: https://stripe.com/terminal/stripe-reader
i'm assuming it would be preconfigured for my stripe account
or for stripe accounts only i mean
Yes, as you say, sending data to Stripe is a separate function, however, it is built-in into our readers. So any device wouldn't work.
so for example, say i buy a nonstripe nfc reader
and somehow use the data it grabs to send to my account via stripe api
(as i do now with an input field)
as opposed to
buying a stripe nfc reader, which presumably only works with a stripeaccount
if i had a nonstripe reader, i could use the api for setupintent
am i able to use the stripe reader for setupintent
or is it paymentintent only. but again, i don't know stripe nfc reader is passing the data to begin with
i assume it's passing the data, surely the transaction doesn't happen inside the device
are you still there
Yes, please give me a moment to check. Thanks!
k
Sorry for delay, looking now
Okay, if you are able to collect data from a reader you could potentially send it to Stripe via your backend. I am not sure if it is possible, but it will be surely less secure as you will need to handle Payment Method data yourself.
the reader would populate the input field
not sure how, will have to look into nfc reader's method of passing data
that's why when i saw stripe nfc readers i got my hopes up, only to have them dashed by what appears to be payment only
really need a solution
I am not familiar with how other card readers work, so can't help you with this, unforunately.
but how does stripe's reader work
is it payment only?
or can i use it to auth, not capture
again, called support, they said come here
It depends on how the PaymentIntent is set up. You could use capture_method: manual: https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
And then collect PaymentMethod however you prefer.
but that's still paymentintent, i need setupintent
paymentintent is a capture and will show in customer's bank account
def don't want a hold being placed on their card
are you familiar with how opentable uses your api?
that's exactly how we do it
create customer object, attach setupintent
Hi! I'm taking over this thread.
Can you try to summarize your question while I catchup?
well there's preface from previous conversations
with vanya
start from beginning?
Well that's not really a summary. So give me a few minutes to read everything.
correct it's an unanswered question
but since you were helping others didn't know what to do
hey @delicate delta I'm going to close all other threads and you and I will talk here
to answer your question about card present payments, you have to use our readers. We don't certify the use of third party ones and they wouldn't work with our API. While you might able to use a reader to get a raw card number and pass that to our API(if you were PCI certified level 1 yourself), that would not be processed as a card present payment in our API so would cost more/have the liability of an online payment for disputes etc.
is there a way to pay for dedicated support?
sure, https://stripe.com/ie/support-plans
what other open questions do you have @delicate delta ?
that doesn't change much really.
so yes, you might able to use a reader to get a raw card number and pass that to our API(if you were PCI certified level 1 yourself)
it would be helpful if you understood how i even got to the point of looking at stripe readers as an option
it would! could you tell me your exact use case so I can suggest the best and most recommended approach?
restaurant, reservations, valid cc required to place reservation
if you know opentable, they use your card elements to do this via setupintent; we mimic the method.
and the difference is you do this in person?
currently our forms have been successfully using card element to do this
no
website
sounds good
so.. in person.
how is a kiosk not in-person?
it's still through a form, just on a kiosk as well
so in person
it's a physical kiosk in the real world, customer presents card to it, the kisok runs your site, you want to get the card details to the site
I get it
it's no different then the website, so if using the form on the kiosk is in person, then so is using it on the website
no
again let me explain, there's no physical card
it's just a form they type in their card nbumber
ok. I'll step away for a bit and let you type
to be clear, using a standard keyboard, or like a virtual touch keyboard in your software?
ultimately I don't think Stripe really supports this form of integration, but we can talk about it
yeah that's the first issue, it has to be a virtual keyboard
but can't be os native because those aren't customizable
and can't have people circumventing browser lock
yeah I'm not sure they will work well with our Elements. You'd need to build a virtual keyboard I think and I don't really know you'd reliably get that to type into the iframe
this is not what we design stripe.js for or certify it for. It's mean to be run on the customer's own device. Kiosk payments are a separate beast
yes using jquery keyboard and works fine for all fields except card elemtns because of iframe,
it's not a payment, it's setupintent
again same as opentable
yeah that part is irrelevant, either way you need to get a card number into Stripe
right and if i could control os native keyboard this conversation wouldn't be needed
but can't so need alternative solution
ok then let me suggest something
thought about qr code but seems only works for payments
next saw stripe reader but seems only works for payments
not true
to be clear you possibly can't use Terminal since it's not certified for unattended kiosks
you can use SetupIntents with Terminal to save cards
no
none of those things. Anyway again, if it's an unattended kisok then as far as I know we can't support that. Our readers are certified for in-store use where there's a cashier/employee involved and monitoring. I could be wrong, that's more of a product question for our sales/support teams.
because it specifically says paymentintent in the first paragraph
yeah but like
You can use previously saved card details to charge customers later.
that paragarph shows you how to charge the saved card
these two links are how you save it
so like https://stripe.com/docs/terminal/features/saving-cards/save-cards-directly for example is saving the card with a SetupIntent
ok will read that
however not sure what unattended kiosk has to do with the equation, forms on the website are unattended
it's the same thing, a website in a browser with a form full of input fields
it's a windows desktop
chrome browser
I'm just a developer, I don't make these rules
what rule are we talking about?
but they are quite different, it' a online card not present payment versus card present, they're different beasts
there is no card present
the use of Terminal for unattended kiosk transactions
it will be if you use Terminal to save the card
the kiosk doesn't require a physical card
but it will if you use Terminal
oh well then terminal won't work
cool!
we don't have a way to read a physical card
to cut to the chase I don't see us supporting this use case
that was the point of looking at the stripe nfc reader
I think the only way to do it is to be PCI certified yourself, build your own non-Elements inputs and accept the card details that way and submit to our API. At a technical level that works fine.
what you're describing is a fairly rare use case that doesn't come up very often(I've worked at Stripe for 5 years in this role and have only seen it a handful of times). My impression has been that it's not really a use case we directly support or have any direct recommendation about; it doesn't fit into the buckets of either a card-not-present online transaction on a site, or a card-present transaction in-store, so it's sort of a "we can't help too much with designing this" gap.
it's literally a card not present online transaction on a site
I know what it is, yep. Like I said, it really doesn't come up often.
let's go back to QR codes. Why is that not an option?
setupintent
you could have a "scan here to register" link, which opens your normal site on the customer's phone.
yeah, and?
you can build a normal web page using Elements that uses a SetupIntent
bad link
that's what i have, a normal webpage
i think the word kiosk is throwing this conversation out of alignment
so is it not an option to have a QR code to scan that opens that page? I know it's not exactly what you asked for, I'm just throwing it out there as a well-supported option.
oh yes i understand, it would just take them to the same form on their device
but we didn't need a kiosk to do that, we already have that
we're trying to make this work on the kiosk aka windows desktop
yep, makes sense. That is poorly supported though, as I said. It's a gap
well let me put it this way:
it already works on the kiosk... if i use the wondows osk
to me the safe (well supported, well documented) options are the QR code-> online payment page on phone ; or Terminal + cashier+ saving card options
so the idea that it's not supported is just not true
the only issue is i can't control the windows osk
that's why i built a virtual keyboard into the page
but
and this is significant
that virtual keyboard also doesn't work on our website
for your card element
so it's not about the kiosk
yep, I imagine it wouldn't
and the website is your use case
think the only way to do it is to be PCI certified yourself, build your own non-Elements inputs and accept the card details that way and submit to our API. At a technical level that works fine.
hence why I say this
ok forget the kiosk, how do i get the virtual keyboard input to work on my website
my research led me to using a proxy
so that the calls would be coming from my domain
I don't think you can, that's not a use case we support(as in, we don't intend for Elements to be used that way so we don't consider that in the design). At a technical level you'd have to somehow get the keystrokes into the <input> inside our iframe, which seems difficult and error prone(and will break when we change the internal structure of the iframe).
so I would build my own inputs instead and call the API directly if I really needed to do this
right i'm going to have to. is there another method of element implementation that doesn't involve the iframe
no. If you're using Elements, that is an iframe
is there a program whereby a website is certified pci compliant and thus able to be whitelisted by stripe or something?
not aware of anything like that
technically all mobile devices are using a virtual keyboard btw
just native is the difference
I'm not getting into a debate with you
it's not a debate
overall my suggestion here is the QR code approach. Becoming PCI certified yourself is a big undertaking, but is possible! there aren't many docs on integrating with raw PANs because it's highly discouraged, and only larger users with Sales support usually do that, but if you have technical API questions there, we can help
anyway i'll probably go back to trying to customize windows osk, bypasses this entire convo]
can we stop there and focus on purely technical/API question for any follow ups? Unfortunately this is not a channel for dedicated Solutions Architecture help but hopefully you have a solid direction now
no
like, if you have a Solutions Architect working with you because you're in our Sales pipeline you could ask them! That's what I mean. If not, you can work with our public docs and this channel and our support team to self-serve and get advice on building your integration.
ok so sales is the contact point for that