#dev-authorize-card

1 messages · Page 1 of 1 (latest)

radiant mango
#

Hi there! You are referring to authorizations with Stripe Issuing?

fossil cloud
#

yes

radiant mango
#

Thanks! I do believe this is possible but don't remember off top of my head where we return this info. Give me a moment to check.

fossil cloud
#

thank you!

radiant mango
#

Give those docs a look and let me know if that doesn't answer what you are looking for

fossil cloud
#

ok so once a card is swiped, would we only get the merchant category of the purchase or would it also include the name/id of the fuel station for example? Ie could we differentiate a transaction with same purchased products but at different locations?

radiant mango
#

Ah good question. I believe you just receive the MCC and wouldn't be able to differentiate between locations, but let me double check.

#

Wait no I think I'm wrong

#

However, you can't set spending controls based on name... only category.

#

That said, you can set up your webhook to handle this

fossil cloud
#

what does the network_id refer to in that data?

radiant mango
#

That is basically a UUID that comes from the card networks for the seller

fossil cloud
#

could that be used for this purpose? ie allow at location 1 with network_id = "abc" and decline at location 2 with network_id = "def"?

#

i guess we would have no way of knowing that network_id's before a swipe happens at that location

radiant mango
#

Right

#

Don't think that would really work

fossil cloud
#

i assume seller name would not necessarily be unique?

#

like for a chain, they might be the same?

radiant mango
#

Yeah I don't think they necessarily would be... that information will be provided to us via the card network and then we will relay it. So we can't really guarantee either way (in terms of it being unique or not or some mix of both).

fossil cloud
#

got it, really appreciate your help!