#newb1

1 messages · Page 1 of 1 (latest)

sick coralBOT
orchid drift
#

Hi! What's the question?

delicate delta
#

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

#

i'm assuming it would be preconfigured for my stripe account

#

or for stripe accounts only i mean

orchid drift
#

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.

delicate delta
#

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

orchid drift
#

Yes, please give me a moment to check. Thanks!

delicate delta
#

k

orchid drift
#

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.

delicate delta
#

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

orchid drift
#

I am not familiar with how other card readers work, so can't help you with this, unforunately.

delicate delta
#

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

orchid drift
#

And then collect PaymentMethod however you prefer.

delicate delta
#

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

sinful pier
#

Hi! I'm taking over this thread.

#

Can you try to summarize your question while I catchup?

delicate delta
#

well there's preface from previous conversations

#

with vanya

#

start from beginning?

sinful pier
#

Well that's not really a summary. So give me a few minutes to read everything.

delicate delta
#

correct it's an unanswered question

#

but since you were helping others didn't know what to do

wheat mesa
#

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 ?

delicate delta
#

again, this isn't a payment

#

it's auth, not capture

wheat mesa
#

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)

delicate delta
#

it would be helpful if you understood how i even got to the point of looking at stripe readers as an option

wheat mesa
#

it would! could you tell me your exact use case so I can suggest the best and most recommended approach?

delicate delta
#

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.

wheat mesa
#

and the difference is you do this in person?

delicate delta
#

currently our forms have been successfully using card element to do this

#

no

#

website

wheat mesa
#

sounds good

delicate delta
#

again has been successful

#

but now we have a kiosk

wheat mesa
#

so.. in person.

delicate delta
#

and have created a kiosk version of the form

#

no not in person

wheat mesa
#

how is a kiosk not in-person?

delicate delta
#

it's still through a form, just on a kiosk as well

wheat mesa
#

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

delicate delta
#

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

wheat mesa
#

ok. I'll step away for a bit and let you type

wheat mesa
#

ultimately I don't think Stripe really supports this form of integration, but we can talk about it

delicate delta
#

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

wheat mesa
#

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

delicate delta
#

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

wheat mesa
#

yeah that part is irrelevant, either way you need to get a card number into Stripe

delicate delta
#

right and if i could control os native keyboard this conversation wouldn't be needed

#

but can't so need alternative solution

wheat mesa
#

ok then let me suggest something

delicate delta
#

thought about qr code but seems only works for payments

#

next saw stripe reader but seems only works for payments

delicate delta
#

just need a method of setupintent

#

ok please explain

wheat mesa
#

to be clear you possibly can't use Terminal since it's not certified for unattended kiosks

wheat mesa
#

you can use SetupIntents with Terminal to save cards

delicate delta
#

no charge?

#

no hold on customer card?

#

no product creation with price attached?

wheat mesa
#

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.

delicate delta
#

because it specifically says paymentintent in the first paragraph

wheat mesa
#

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

delicate delta
#

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

wheat mesa
#

I'm just a developer, I don't make these rules

delicate delta
#

what rule are we talking about?

wheat mesa
#

but they are quite different, it' a online card not present payment versus card present, they're different beasts

delicate delta
#

there is no card present

wheat mesa
wheat mesa
delicate delta
#

the kiosk doesn't require a physical card

wheat mesa
#

but it will if you use Terminal

delicate delta
#

oh well then terminal won't work

wheat mesa
#

cool!

delicate delta
#

we don't have a way to read a physical card

wheat mesa
#

to cut to the chase I don't see us supporting this use case

delicate delta
#

that was the point of looking at the stripe nfc reader

wheat mesa
#

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.

delicate delta
#

it's literally a card not present online transaction on a site

wheat mesa
#

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?

delicate delta
#

setupintent

wheat mesa
#

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

delicate delta
#

that's what i have, a normal webpage

#

i think the word kiosk is throwing this conversation out of alignment

wheat mesa
#

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.

delicate delta
#

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

wheat mesa
#

yep, makes sense. That is poorly supported though, as I said. It's a gap

delicate delta
#

well let me put it this way:

#

it already works on the kiosk... if i use the wondows osk

wheat mesa
#

to me the safe (well supported, well documented) options are the QR code-> online payment page on phone ; or Terminal + cashier+ saving card options

delicate delta
#

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

wheat mesa
#

yep, I imagine it wouldn't

delicate delta
#

and the website is your use case

wheat mesa
#

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

delicate delta
#

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

wheat mesa
#

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

delicate delta
#

right i'm going to have to. is there another method of element implementation that doesn't involve the iframe

wheat mesa
#

no. If you're using Elements, that is an iframe

delicate delta
#

is there a program whereby a website is certified pci compliant and thus able to be whitelisted by stripe or something?

wheat mesa
#

not aware of anything like that

delicate delta
#

technically all mobile devices are using a virtual keyboard btw

#

just native is the difference

wheat mesa
#

I'm not getting into a debate with you

delicate delta
#

it's not a debate

wheat mesa
#

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

delicate delta
#

anyway i'll probably go back to trying to customize windows osk, bypasses this entire convo]

wheat mesa
#

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

delicate delta
#

fine.

#

thanks

#

oh wait, is there a channel for dedicated solutions architecture?

wheat mesa
#

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.

delicate delta
#

ok so sales is the contact point for that