#highspeed_issuing-cardholder-validation

1 messages ¡ Page 1 of 1 (latest)

half bridgeBOT
#

👋 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/1356400576128090242

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

spare rover
#

That card holder was disabled because required information was not provided.

azure raptor
#

I'll review the api documentation to avoid asking you the stupid question that's on my mind right now.

#

Thanks for getting back to me so quickly though, please standby

azure raptor
#

Ok, I can see now in the dashboard some requirements that are needed for card activation, though I'm not understanding entirely, because I did provide a First and Last name (one of the listed requirements). I'll be creating virtual cards on behalf of customers that use my app. Is there not an complete programmatic way to do this?

spare rover
#

Looking at our docs here it seems like providing a date of birth could help reduce watchlist issues.

#

Also, you need to collect user_terms_acceptance as we mention here

azure raptor
#

Ok, got it. Thanks. I'll get to reading and attempt to implement this.

spare rover
#

Honestly, if it were me, I'd start by copy/pasting the exact code snippets into whatever coding language you are using and see how all of that looks in the Dashboard after you create it. Just to get a sense for how it behaves.

azure raptor