#nerdslice_code

1 messages ¡ Page 1 of 1 (latest)

sly sapphireBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1270133347527561290

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

chilly relic
#

Hi there

spark canyon
#

hello

chilly relic
#

No, not exactly

#

We have the CardElement and PaymentElement for online payments but this assumes a card-not-present scenario

spark canyon
#

Right, what we are wanting to do is help a store on board with us and start processing immediately. So that they are already processing before their terminal arrives

chilly relic
#

Got it. Give me a few minutes

#

I recommend using something like PaymentLinks for this and having folks at the store email or send a PaymentLink to these customers when they're ready to complete payment

#

This way the customers complete payment on their phones while in store and there's no additional integration work that you have to do

spark canyon
#

We are white labeling, so our connect customers interact exclusively with our software and stripe exclusively through api

chilly relic
#

I see

spark canyon
#

I do not expect it used often but I want to offer it for stores to use so they can process with us faster

chilly relic
#

We have some recommendations for MOTO payments but that doesn't quite fit your model. MOTO payments are specifically payments that are made where the customer shares their payment details with a business over the phone: https://stripe.com/resources/more/moto-payments-101

spark canyon
#

ok so stripe-elements is the best path for this use case then

chilly relic
#

Kind of. It's a bit of a grey area since using the PaymentElement or CardElement assumes that it's the end customer providing their payment details and not an employee

spark canyon
#

So if we put in a screen for the customer to do so then?

chilly relic
#

Right, that could work

spark canyon
#

OK thank you, we were planning a customer facing screen in our next release anywayus