You might have to use an external API. I came across this one that may fit your use case. I could see caching the results since routing numbers for banks/CUs would hardly ever change. Requests are limited 100 per hour but it is free.

https://bankrouting.io/

I utilize Q2 Central to enable or disable a feature at the group level. For instance, we have a group that consists of credit union employees that test a new feature before we enable for the entire userbase. Hope this helps.

Hey Brock,

I've used Discover to track number of visitors, page views, and average time of page for our custom extensions. I would be happy to discuss, feel free to reach out.

Thanks
Bradley

If you have access to Q2 Central you can find it there. Navigate to Manage Secure Messaging under the Administration menu tree. That should show all your Secure Message group names and GroupID. That's where I had to look.

I would recommend housing and configuring the terms and conditions disclaimer in Q2 Central using the Digital Banking UI self-service form. To start, you would create the disclaimer, assign it to a disclaimer bundle, associate that bundle with a Q2 Group, and then link it to a navigation node (which I assume would be the nav node for your extension).

Adding a new disclaimer requires the assitance of Q2 support.

For tracking acceptance, if you have access to the EVE data extract, there i...

I'll add my answer here in case it helps you and you can mark it as the solution. There's a couple of things that we needed to consider when creating a list of eligible accounts for the user to choose from:

1. We wanted to ensure that the accounts linked to the User's profile had view-permission. We utilize Member to Member transfers and when those accounts are linked to the User's profile, the permissions are set to deposit only (no withdrawal permissions or view permissions).
2. I wan...

Thanks Brian! Got it all setup. However, after completing all the steps in the tutorial, it's not calling out to my MFA extension but to the built in Q2 MFA process and it listing all SAC targets for a code to be sent to. Not sure what I'm missing here.