#nielsen_unexpected
inland matrixBOT
👋 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/1507079184684683295
📝 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.
- nielsen_plaid-de-integration-and-achv2-migration, 2 days ago, 31 messages
regal garnet
Yes
pi_3TZYN5AeTljDDHLY1vucDret
and here is the one for the credit card
pi_3TZYQZAeTljDDHLY0b0pLY52
For more context, we're migrating our bank sources to use Payment Intent instead of Charge
and this is our first test in production
rancid galleon
pi_3TZYN5AeTljDDHLY1vucDret is using a legacy ACH debit source created on the backend via the Tokens api and passing the routing and account numbers directly. I'm not sure why you would expect this to have an IP address and a mandate - you would associate that level of information with payment method details collected on Stripe Elements
regal garnet
Does adding the mandate through the SetupIntent not matter then?
Even from the backend?
To clarify, we are now adding Mandate Data to those bank sources. We had to in order to migrate from Charge
And after adding, we ran a test and got that warning
We added the data after the fact of course, these were payment methods that were created through the Plaid Stripe integration.
rancid galleon
okay I see - you did a SetupIntent on this bank account here: https://dashboard.stripe.com/acct_1Ch5RoAeTljDDHLY/logs/req_JZlwGIF6LQYiiD
Can you try retrieving this token via GET /v1/payment_methods/:id? ba_1TYpdFAeTljDDHLY86RPghOz
ah sorry I don't think we actually expose the mandate data in that API per the api reference
regal garnet
Not sure if i can, let me see if i have access to the prod secret key
rancid galleon
where are you looking for IP and seeing it on the card PaymentIntent?
regal garnet
ah sorry I don't think we actually expose the mandate data in that API per the [...
I can see the mandate data object in the stripe dashboard if that's what you mean
rancid galleon
Ah, well the dashboard is likely fetching the mandate directly from the Mandates API
regal garnet
it shows the IP is missing
rancid galleon
I'm sorry, I can't really speak much to the dashboard. You could try taking the mandate id from the response to the SetupIntent (mandate is also stored on the SetupIntent) and you should find it in Customer Acceptance
regal garnet
Ok I can see the mandate object Id with the details that include the IP adress
mandate_1TYpdGAeTljDDHLYGf1lwi1M
rancid galleon
but as to why we don't surface it in the dashboard for these migrated legacy ACH debit payment methods, you would have to reach out to support and ask about it and they could bring it up with our dashboard product team to see if we can add that
regal garnet
this is what is see
It's not just that it doesn't surface it, it says that the IP address is missing
as part of the risk analysis, it implies to me that we may not have migrated this properly.
rancid galleon
I would tend to guess that whatever logic we have to look up IP addresses for these payment methods (if it is looking at the acceptance data) is failing in this case and "missing" is the default case, or something like that. Again, I can't really can't say much about how the dashboard works as we focus on the APIs/SDKs/clientside libraries here in this server
regal garnet
Ok, so as far as you can tell, this payment method does have the mandata data correct configured and I should not expect problems with it?
rancid galleon
Yes, that's right
regal garnet
Would this create a problem at scale? If Radar is saying that it's now seeing an IP address, would it eventually cause issues as we start doing this en masse?
rancid galleon
I guess what do you mean by issue? This is a warning in the dashboard, and I'm not entirely certain it is directly tied to the acceptance IP on the mandate. I can't tell you why the dashboard displays the warning for the legacy ACH debit bank accou nt you migrated but not the card source, unfortunately.
As I mentioned, for questions about why you're getting a warning in the dashboard on one but not the other you'll ultimately need to reach out to Stripe Support: you can follow these instructions to do so:
inland matrixBOT
We wish we could help, but you need to talk to Stripe support
We can only help on Discord if all of the following are true:
- 🧑💻 You must be a developer
- 🛠️ Your question must be about building a Stripe integration
- ⚙️ Your question must be technical/developer focused
- ⏱️ You must be available to respond in realtime
- 👥 You must be comfortable receiving help in public (this is a public server)
If any of those aren't true please contact Stripe support.
If all of those are true we may have misunderstood your question; please provide more details below.
Note that using an inappropriate button or submitting inappropriate information is a violation of our rules. You will be removed from this server if you repeatedly create invalid threads.
regal garnet
Ok will do