#local-issuing-cardholder-name
1 messages · Page 1 of 1 (latest)
np
name was top level
we should of been using the returned cardholder object anyways but that's only reason I stumbled across it. we we're accessing the top level name property
yeah I think your account also has some pretty old legacy feature from years ago but digging
This one had the top level prop req_akAQHcxjsiNNbb from early March
Yea it was weird we had the banner for a long time about issuing beta being over and I clicked the Ok message and maybe that triggered the change
We assumed the beta would swap us over automatically so i had to go click thte banner for the platform and some connects I think
May be the cause or not IDK
and yes okay that's the issue
your account is configured in a way where Test mode requests get the old behaviour and Live mode requests get the new behaviour
yes, I'd recommend just working with our support team directly: https://support.stripe.com/contact
ok sounds good. thanx