#lutthein_api
placid pewterBOT
👋 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/1343652029003730966
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- lutthein_interac-payment-scenarios, 1 hour ago, 37 messages
cobalt inlet
Hello! I'm not seeing anything on our end for that Setup Intent other than it being created. There should be more details in your Terminal integration's logs about what happened when the card was used. Can you share that detail?
wooden goblet
Hi! Thanks for your answer. I don't have that many logs happening in my phone as terminal, as this is happening during the Tap card screen Im not seeing logs happening all I get is this message
cobalt inlet
Oh, hang on, you only have card_present set on this Intent. You would need to add interac_present as well. See here for details: https://docs.stripe.com/terminal/payments/regional?integration-country=CA#interac-payments
wooden goblet
Im currently using SetupIntents, created with the client-side flow in React Native, specifically this doc:
https://docs.stripe.com/terminal/features/saving-cards/save-cards-directly?terminal-sdk-platform=react-native
I dont pass any payment_methods_types or anything like in paymentIntents
cobalt inlet
You would need to create the Setup Intent server side in that scenario I believe.
I don't think React Native lets you set the payment method types from the client.
wooden goblet
I tried using the server-side implementation, but for me to then consume the setupIntent object returned by the API, it was telling me that I was missing the "SDKUUI" prop on the object, do you know what could be the cause?
cobalt inlet
What was telling you that? Can you paste the exact error you were seeing?
wooden goblet
I was getting this error when calling the collectSetupIntentPaymentMethod, passing the setupIntent object from the serverside implementation. I dont have the exact error message because we derived from that approach and went with the client-side one, but it refered to that setupIntent object not having the property sdkUuidon it
cobalt inlet
I'm afraid I don't know what that could mean. I'd need to see the associated request ID or, at minimum, the exact error message in full.
wooden goblet
So, what we were doing on the server-side implementation was:
- My app would make a REQUEST to the API endpoint to generate a new SetupIntent:
- The API would return me a created SetupIntent object
- I would then use that SetupIntent object in my ReactNative application to
collectSetupIntentPaymentMethod, but it would throw an error because that object would not have the sdkUuid prop
Are we understanding that wrong? we cant just jump between server-side creation and then client-side collection?
cobalt inlet
That's the correct flow, in a nutshell. I don't think you're understanding it wrong. The error sounds unusual and I wish I could tell you more about it, but to do so I'd need to look at a specific example.
For you last question I'm not sure I understand what you mean, exacty? Can you clarify what you mean by jumping between server-side creation and client-side collection?
placid pewterBOT
wooden goblet
Ok, I let me go ahead and try to replicate the issue, Im currently setting back the server-side SetupIntent creation.
By jumpin around I meant that, we have both an API and a react native mobile app doing this process. The API in this case was the one generating the SetupIntent object, and returning it to the react native mobile app, and then the mobile app would collectSetupIntentPaymentMethod to have the user tap their card on the phone to continue the process.
Now, for server-side, while creating the setupIntent, is interact_present a valid payment method type? We are currently facing an error message saying otherwise
ivory island
Hello
Taking over as Rubeus had to step away
Sorry for the confusion but I don't believe you can use SetupIntents with interac_present payment method type.
https://docs.stripe.com/terminal/features/saving-cards/save-cards-directly#:~:text=You can use SetupIntents to collect card details on Visa%2C Mastercard%2C American Express%2C Discover%2C co-branded Interac%2C and co-branded eftpos cards. Single-branded Interac cards and single-branded eftpos cards aren’t supported
If it is a co-branded interac card, then card_present payment method type should be able to save it.
I'm looking to see if I can find the reason behind why the cobranded card wasn't saved.
wooden goblet
Ok, that makes sense. Thank you, we have test it both in test/live mode and we still get the same behavior in iOS or Android
ivory island
You're sure it's a co-branded interac card correct?
Can you share issuer information?
Can you also share the reader serial number | UUID?
wooden goblet
We are currently using a phone as terminal implementation, a iPhone or a Samsung device.
Im sure it is co-branded, visa-interac from Scotiabank Canada
ivory island
Hmm based on the logs for the SetupIntent - the error seems to be coming from Apple with no clear indication of why the card read is failing.
wooden goblet
This is another setupIntent we just created from the server
seti_1Qw7y3Bb49XQ2DGy9VYfSW4V
The issue we were having while trying to have the creation the server and then use it in the mobile app was that this setupIntent would not have a sdkUuid
when we create the setupIntent using the reactnative sdk, we dont have this issue.
ivory island
do you mean the issue with saving a card?
wooden goblet
I dont know if it might be related or not
ivory island
I don't think how the SetupIntent was created matters here.
Based on the logs I'm seeing, this is something on the reader
Apple is reporting that reader had trouble reading the card and you should try another card instead
wooden goblet
Thats strange, it works just fine with a credit card
ivory island
Yup, it likely is something with the card you're using
do you have a different cobranded interac card you could try?
placid pewterBOT
keen portal
👋 we took a look into this and it does appear to be a bug. The next best thing to do here is to report the issue to our Gitbhub SDK page: https://github.com/stripe/stripe-terminal-react-native and our Engineering team would update you on the status of things there as they investigate.
wooden goblet
Hello, Thank you! I will go ahead an open it.
Just did, let me know if there should be any further information required or important. Hopefully, the solution will be simple haha
https://github.com/stripe/stripe-terminal-react-native/issues/887
keen portal
Thanks!