#mattcomroe_api
heady nexusBOT
👋 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/1470866240284393624
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
fallen spade
Hi there,
just to clarify, you are trying to confirm a Setup Intent as a platform on the connected account?
cunning ember
correct!
fallen spade
do you have account ID for platform and connected account?
cunning ember
sure! one sec please.
Platform account is: acct_19sH6VHAuKxNQma4. The Connected account which is MX-based is acct_1Q5YB3H7A1IybVWg
this was brought to me today as an issue from a production user, but as far as I'm aware I haven't changed anything around this particular part of the logic in a minute...
fallen spade
When I look at the request I can see that the platform itself is trying to confirm the Setup Intent
cunning ember
the setupintent is being created with an on_behalf_of parameter. i thought that's sort of what that was for.
heady nexusBOT
mortal wedge
Hello
Taking over as my colleague needs to step away
cunning ember
no worries at all. you've helped me out before! hope you're doing well today...
mortal wedge
Doing well, thank you!
Your confirmation request is fine. That's the expected flow with on_behalf_of
cunning ember
ok. we haven't touched the code for adding new payment methods in a quite awhile so i just wanted to note that.
mortal wedge
Looking into what's going on with the confirmation request..
Can you share the code you use to initilize Payment Element in the meantime?
cunning ember
it's on sort of a weird platform that we write our application in so i don't have a nice clean javascript action to point you to. i can dig around for it tho if you tell me what you are looking for as far as how i'm attaching the payment element.
but that part also has been unchanged for a few months.
mortal wedge
Are you setting any options before you pass it to Elements?
What I am actually trying to do is figure out how exactly the currency is coming into play here..
cunning ember
i am not passing in currency to the javascript init. you would know better than me but i assumed the currency was coming in through the account settings on the connected account.
from the API object details of that connected account.
mortal wedge
Thanks.. Give me a moment to check something
cunning ember
of course! take your time and I appreciate you and your help.
cunning ember
wrong that it isn't working all of a sudden?
ok good to know i'm not going crazy then. :p
mortal wedge
I'm trying to dig deeper though, let me see what I can find
I think the issue here is that the default currency on your Platform account is usd but the card only supports mxn
Since the SetupIntent is created on the Platform, it's using usd as the presentment currency
Let me see if that's the case with other currencies as well
cunning ember
hmm ok maybe it's something mxn specific? because i feel like we would have had a lot more complaints about this a long time ago otherwise.
we currently operate in a bunch of non-US countries besides MX and this is the first issue of the sort that I've been made aware of. my assumption is that people have been happily adding cards and paying in local currency this whole time.
mortal wedge
Okay yeah I think this seems to be expected with this flow.. I tried to test it with a UK account where I expected the presentment currency to be gbp but it still used usd
cunning ember
so for a UK account it also failed with the same error?
mortal wedge
No, it succeeded with a UK card for the UK connected account
But most likely the validations are different for an MX card versus a UK card
cunning ember
ah, ok. I am finding it hard to believe that this is the first i'm hearing about it tho. We have multiple MX-based Connected customers that have been on our Platform for years. Have we just maybe been lucky that the majority of cards people have added have been international cards or otherwise support USD whereas the test card specific to Mexico does not?
mortal wedge
It is possible.
cunning ember
wild 😹
mortal wedge
Now, are you seeing the same behavior on live mode too?
cunning ember
a report came in from a customer about this today or yesterday, so i guess the answer is yes?
do you have thoughts about what my easiest fix is here? do i need to change how the payment element is created to pass mxn when showing the Element to a MX-based customer?
whoops that shouldn't have been a quote; sorry.
heady nexusBOT
hybrid lotus
Hi there 👋 jumping in as my teammate needs to step away soon. Bear with me a moment while I catch up here.
cunning ember
yep no problem! thanks for hopping in and i appreciate your help! this is a weird one.
hybrid lotus
Hm, do you happen to have any of the object or request IDs from the example in production? I'm thinking there is no way to fully avoid this, as it looks to me like this is representing the issuer declining the authorization due to the currency being used.
cunning ember
unfortunately i don't have any requestids showing this problem. i heard about it through our Customer Support folks and they were able to reproduce the problem in a lower environment, but I don't have any specific examples from Live mode.
can i search my own error logs for that error string to find one that way?
might have one.
one sec please!
seti_1SzH0UBnxMPxdETuZipF2mW4
whoops
req_sA44dfqYghW5cf
hybrid lotus
Amazing, thank you!
cunning ember
glad i found one.
hybrid lotus
While I wait for logs to load, I want to take a step back and see what sort of your ideal solution is here. Do you want more control over the currency that is used?
cunning ember
no, nothing like that. i would like things to continue to operate as they have previously.
i know this isn't scientific at all, but i see a couple of those currency failures when looking through the setup_intent confim API logs from today.. i went back and reviewed a week's worth back from January and i don't see any of those in those logs. certainly could have missed them if they're there, and i don't see a great way to filter on JUST those types of logs.
and we have a large enough customer base that it feels like something we would have heard about sooner. so only finding out about it today really feels like something has changed recently but I don't know what.
hybrid lotus
I agree it's hard to find these specific logs. But offhand, I don't think anything has changed here.
cunning ember
you would definitely know more than i would... it just seems like a pretty common thing that i would have heard about since our payment method onboarding process hasn't changed in months.
hybrid lotus
We can reach out to the product teams to confirm, but that's not something we'll be able to update you on in this thread, we'll need to get a support case opened. If that's alright I can have our bot send you a DM for creating a case.
cunning ember
yeah that would be great! but while i have you... i can't set a currency when doing a Setup_Intent like I can for a payment_intent, right?
hybrid lotus
Correct
heady nexusBOT
Hello @cunning ember, we have sent you a direct message, please check it at https://discord.com/channels/@me/1470897862782226555
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
cunning ember
so i will be able to pass the currency in to the payment element when i'm instantiating it instead?
hybrid lotus
Yup, if you use what we refer to as "deferred intents" (the creation of the payment intent is deferred until after the Payment Element is completed), then you can pass a currency when initializing the Elements instance:
https://docs.stripe.com/js/elements_object/create_without_intent#stripe_elements_no_intent-options-currency
https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=setup
cunning ember
but in this case i shouldn't even need a payment intent. i just need a setup intent to collect the payment method.
can i still pass a currency when initializing the Elements then?
hybrid lotus
Yup, should be able to even with a mode of setup
cunning ember
ok.. i will look at all that! thank you so much for your help!