#lutthein_api
frigid spokeBOT
👋 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/1354472490415423499
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
ivory crag
Hi, Can I get assistance setting up my strip API in my dashboard?
potent sandal
Hey @ivory crag you probably want to go to #help and tap one of the options to open your own support ticket 🙂
visual sedge
@potent sandal Looking at some logs it looks like the network returned a "lost card" code, so that's why the authentication failed
But really in these authentication issue situations, you have to reach out to the issuer/bank for more info
potent sandal
Yeah, I checked the docs, and it seems it could be essentially the bank not wanting to provide the information. It worked with my credit card. We are currently PoC to see if we can add support for Interac-branded cards in Canada with the WisePad3. We already have a Tap to Pay solution in place, but that is a "card" method, which doesn't accept Interac
Do you know if with this implementation (WisePad3) we could use Interac branded cards in Canada for setupIntents? I saw in the failed setup intent that the method is now "card_present" thats what we want, which should accept Interac, but could you confirm that? I sadly dont have any other interac cards to test with
Mine is def not "lost" lol but yeah, anyways, banks being banks
visual sedge
co-branded interac is supported it looks like
However
Single-branded Interac cards and single-branded eftpos cards aren’t supported.
potent sandal
Yeah, still need to see it work haha, I guess getting this auth error is a good sign, other than the usual "Card not supported" we got on Tap to Pay implementation.