#tobewisebeforeiamold_code
1 messages ยท Page 1 of 1 (latest)
๐ 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/1486858382982906037
๐ 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.
- tobewisebeforeiamold_code, 1 day ago, 22 messages
- tobewisebeforeiamold_code, 1 day ago, 13 messages
Here is a request ID showing the failure req_hiUmK7zSB2H2po
๐ Taking a look
Given how explicit the error message is i'd say that it's expected the Payment Intent currency needs to match the currency associated with the saved Payment Method when dealing with ACSS. What feels like a bug is the fact that we surface that saved Payment Method, when in theory we should be filtering out any Payment Method incompatible with the Payment Intent.
Looking for any evidence that counters my understanding that it should be filtered out but I suspect we'll need to file a bug internally.
What feels like a bug is the fact that we surface that saved Payment Method, when in theory we should be filtering out any Payment Method incompatible with the Payment Intent.
I agree - that would be the ideal: if someone pays PAD+cad then goes to pay usd, the would have to create a new PAD payment method
Looking for any evidence that counters my understanding that it should be filtered out but I suspect we'll need to file a bug internally
Perfect, thank you!
My preemptive next question would be: if you file such a bug, how long might that take to implement: days, weeks, months? I ask because our alternative would probably be to restrict PAD to cad until the bug is fixed...
Just to confirm, are you using the same payment details to create the Payment Method set up for USD as you used to create the Payment Method set up for CAD?
When I create the payment_intent from which the secret the front-end needs, the currency changes. Is that what you're wondering about?
And of course amount, connect account, customer, etc. But the shape is similar.
My preemptive next question would be: if you file such a bug, how long might that take to implement: days, weeks, months? I ask because our alternative would probably be to restrict PAD to cad until the bug is fixed...
As much as I would love to give you an ETA It would be a total guess at best. I would think it would be fairly straight forward but there may be some gotcha that makes resolving a little more challenging. What I can do if you write into support.stripe.com/?contact=true we can link the internal ticket so that we can keep you updated on the progress.
I'm working with some of my team members to try and determine if there is something were overlooking here first.
You're the best! I'm going to load up that URL now.
Do I just use the "Assistant" to write in/create said ticket?
Yes, but hold up actually, I can send you a link that should, route the ticket straight to our team which would allow us to link the internal ticket quicker. Just want to rule out any other possibilities before I have you write in ๐
OK, thanks! I'll cool my jets and await your reply.
I'm back! Appreciate your patience.
I appreciate your help!
So we dived into how our Element Sessions filters saved payment methods for redisplay, and it looks like we really only really check if the presentment currency is one of the valid options for the given type. We don't look at the individual PM at all.
So there isn't any system in place to do this kind of check. It's not just absent or failing to work in this specific scenario.
I'm surprised this is new ground! I would imagine PAD is probably not the only payment method that works in a subset of currencies...
Maybe it's the only one that requires a new payment_method for each currency though?
I don't feel like this is a good user experience personally but I believe some major changes would be required to filter out specific PMs. It puts this in a 'Product Feedback' category.
I'm going to file some product feedback for you because I think it's absolutely worth considering, but I can't say for certain if it will get picked up or how soon it could be implemented : /
Well, thank you for submitting that! In the interim, what would your recommendation for approach be here? Would we only allow PAD for CAD currency?
That's probably the simplest, most straight forward solution.
Oh well, we can only do what we can do. I'll pass that along to the team.
Is there something we should keep an eye on to see if this product feedback gets implemented? Or maybe we should periodically ask our Stripe rep to keep us up to date on that?
Probably the later option, I don't know if this would surface in a change log. Do you have an account ID handy? Can help to associate the feedback to a specific user.
The account ID for our production Stripe account?
That would be acct_1DLcKyFXc3zoUgUu
I have to take off. Thanks again for your help today!
Thanks for sharing the account ID! We have included your account to the product feedback.
Thank you!