Deploying Banno apps

In order to setup your application for priority deployment, you’ll need to generate a deployment key from your Google Play Developer Account and send us that key securely through jSource. If you have multiple Banno Mobile applications under the same Google Developer account, you will only need to generate a single key for use with all of the apps.

1. Open a browser and log in to the Google Developer Console with your Account Owner credentials.
2. Open a new tab and paste in https://console.cloud.google.com/welcome.
3. Click on the dropdown next to GoogleCloud to create a new project.
4. From the popup window, click New Project.
5. For the Project name field, enter Banno API.
6. Leave the Location field as it displays.
7. Click Create.
8. Click on APIs & Services.
9. Ensure you have the correct API (Banno API) selected next to GoogleCloud, and click + ENABLE APIS AND SERVICES.

10. Scroll down to the Mobile section, and click on Google Play Android Developer API.

11. Click Enable. The API/Service Details screen displays.

12. In the API/Service Details screen for Google Play Android Developer API, click on the Credentials tab.

13. Click on Manage service accounts (API/Service Details > Credentials compatible with this API > Service Accounts > Manage Service Accounts).

14. Click + CREATE SERVICE ACCOUNT.
15. If an Updates to Terms of Service window appears, select No for the email updates and click the Terms of Service checkbox. Then click Accept.
16. Service Account Details
    • Service account name: Google Play API
    • Service account description: For Banno
    • Click Create & Continue.
17. Grant this service account access to the project:
    • Click the Select a role dropdown. Scroll almost to the bottom to find the Service Accounts option. Select the Service Account User role.
    • Click Continue.
18. Grant users access to this service account:
    • Skip Service account users role and Service account admins role boxes.
    • Click Done.
    • Locate the newly created service account on the Service Accounts page and copy the email for the new service account. You’ll paste the email in a later step.
    • Click the three vertical dots on the right-hand side and select Manage keys.
    • Click Add key.
    • Click Create new key.
    • Set the key type to JSON and choose your download destination.
    • Click Close once the JSON file is saved.
19. Close the Chrome tab that the Service Accounts page is open on.
20. Go back to the original tab you started working in, click Users and Permissions in the sidebar

21. Add the email address you copied from step 18 above to the Email address field.
22. Click on Account permissions under the Permissions section, and check Admin (all permissions).
23. Click Invite user.

Now, with your newly generated Android Deployment key, navigate to jSource where you’ll upload the key that was downloaded to your computer. Support will then upload this key to our deployment pipeline, confirming it’s a valid key.

Done! You’re now setup for automated Android deployments.

1. After logging into Google Play, you’re presented with a list of your applications. Choose the application you’d like to complete by clicking on View App. These steps will need to be completed for all of your live applications, not just Jack Henry applications.

2. Scroll down to the bottom of the left sidebar and click App Content.

3. You’re then presented with a page stating that the Financial features declaration needs attention. Click Start on the Financial features declaration. The console may state that there is more than one declaration that needs your attention but you need only be concerned with the “Financial features” declaration. We’re in the process of working through the other outstanding declarations internally, the deadline of which is December of this year. We’ll likely be complete with these changes by the end of September.

4. You’re then presented with the actual form. Fill out the form by checking the boxes of the features you provide directly in the application. This includes features available from your plugins and SSO options. Click Next once you’ve reviewed the entire form. If you provide any of the following from within the application, you’ll have to provide further documentation to Google about the lending provider:

• Personal loan direct lender
• Loan facilitator
• Payday loans

5. Unless your app has any of the features mentioned in step 4, you’ll be presented with a screen stating that you do not require further documentation. If you’re required to provide further documentation, please walk through that process. Once you’re done, click Save on this page.

6. You’ll the be presented a modal, click Go to overview

7. Once you click, Send for review, you’ll be done with the financial features form.

It’s important for your end users to get new builds as quickly as possible. Whether they’re getting vital new features or the hottest performance improvements, we can ensure your end users always have the newest builds as soon as they’re available. Better still, setting up the App Store Connect API Keys that make this possible is a straightforward process, and we’ve outlined it below.

Enabling App Store Connect API key generation

First, you’ll need to log into App Store Connect.

•⎯⎯⎯⎯⎯⎯➊

Select Users and Access (1) to continue.

•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊

•⎯⎯⎯⎯⎯⎯➋

Select the Keys heading (1), then the Request access button (2), which displays the submission dialogue.

•⎯⎯⎯⎯➊

•⎯⎯⎯⎯⎯⎯➋

Check the agreement box (1) and click Submit (2) to see your App Store Connect API approval.

This screen means your setup was successful and your job is done! If you have any questions, contact your support representative.

Banno is a pretty amazing platform for for community banks and credit unions, yet we understand you might find a reason to change. If your institution migrates from Banno, your end users can be guided with a hard or soft prompt to download a link that acquires the new mobile app. At the start of your migration, you’ll work with Banno Support to configure which prompts and messages are right for you.

How does it work?

Soft prompt

If you choose to guide your end users with a soft prompt, the prompt allows them to log in to the app. Upon login, end users can choose to immediately download the new app or wait. If they wait to download the new app, the soft prompt will display on every single successful sync when the end user logs in. Our goal is to consistently remind the end user to download the new app and begin using it.

•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊

•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➋

Hard prompt

If you choose to guide your end users with a hard prompt, this prompt blocks them from logging into the app and directs them to download the new app.

•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➊

•⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯➋

FAQ

In addition to our written documents outlining the steps for setting up keys and accounts for mobile stores, our operations team creates videos outlining the process in detail. See what’s available below.

Android store setup