#Durrell
1 messages · Page 1 of 1 (latest)
Hey there
Let me take a look
Sorry for the delay
We aren't super familiar with this specific data but as far as I can tell it looks to be an account config issue. You are going to be better off working with our Support team to get this updated as it doesn't appear to be something you can do via the API. You can reach out to our Support team via https://support.stripe.com/contact/login
ok. Do you know how reliable this merchant data is? Where does it come from? Is it manually entered by the merchant somewhere?
Ah sorry, I looked a bit closer here and this is actually just data we are going to get from the card networks about the selling merchant. So it would actually be their account config, depending on what PSP they process through. So you wouldn't influence this data at all.
We just pass through what the network sends us
Ok. Do you know anything about Level II and Level III data? I saw this SO post about it. https://stackoverflow.com/a/60099842
According to that the documentation is gated so we can't see what the level II and III data looks like and how we would access it. If we knew what the data looked like and how we would access it before we got gated in that would be very helpful for us.
We are using the merchant_data part of the issuing_authorization.request event to process our authorization logic. One of the things we do as part of our auth logic is look up the merchant in our database with the merchant data from that webhook. We might be able to use that Level II and Level III data to improve our auth logic.
You would need to reach out to our Support team to discuss any private features. We can't discuss them here since this is a public server.