#jslaybaugh-terminal-reactnative

1 messages · Page 1 of 1 (latest)

bronze bisonBOT
solemn arrow
#

jslaybaugh-terminal-reactnative

#

@runic pecan hello! I'm sorry I barely understand what you are describing here. ARe those two completely separate integrations? One for a Terminal integration and one for online payments?

runic pecan
#

I mean they're two separate SDK's/integrations that stripe provides, but they're fundamentally doing the same thing

#

One is providing a form where they type in card number and expiration date, etc and the other is when they use a card in Reader SDK

#

But from our end, they're all placing an "order" in our system, and all the things we have to track from meta data or application fees are the same

#

so we want to run them through the same endpoint on our server, but on one, the client creates the payment method and then we use that to create a payment intent (like stripe.js on the web)

#

And on the other, we appear to have to create the payment intent first, then the client uses that to create the payment method

#

which is exactly backwards from the other implementations

#

Unless I'm missing something, which is why I'm looking for clarification here

solemn arrow
#

gotcha, so both integrations should
1/ Create a PaymentIntent server-side
2/ Confirm the PaymentIntent client-side in your mobile code

#

that's all you need to do

runic pecan
#

Ok, I have to run into a meeting. But let me review this and see if I can understand what is going on here. I've listed two specific instances in RN, but there is also a 3rd with web where we get the payment method first. So it still feels like 2 of the 3 get the payment method first and that is my preferred method so it can all be consistent.

#

back in a bit

solemn arrow
#

there are many ways to integrate. It's up to you which one you choose, but the default one uses the PaymentElement/PaymentSheet integration that does everything for you