In short
Your team submits the Q2 app order and requests staging; PayMitto completes the app configuration.
Installing PayMitto does not automatically make it visible to account holders.
Both your team and PayMitto must select Ready for Production.
1. Open your app order and request staging
Open your existing Q2 app order and confirm that your team can edit it.
If you cannot find the order, contact Q2 support.
Select Install to Staging before PayMitto submits the configuration.
The order targets production by default, and each environment has its own deployment ticket.
2. Provide your navigation and account details
Provide the menu, section, title, description, icon and preferred order within the section.
Include the title and description in each language your institution uses.
Confirm whether Spanish is enabled and whether international addresses are allowed.
Provide and confirm the product IDs for the consumer checking and savings account types that can fund transfers.
Provide a settlement demand deposit account (DDA) for each environment, not a general ledger (GL) account.
Use the secure channel supplied by PayMitto for account numbers; do not post logins or passwords in Q2 tickets.
Custom transaction codes depend on your core banking setup and must be confirmed with PayMitto.
3. Let PayMitto complete the app configuration
PayMitto completes App Configuration on your Q2 app order; your team does not edit the underlying configuration.
After PayMitto submits the configuration, Q2 installs the extensions.
PayMitto confirms the Host Account ID that maps to your settlement DDA in each environment.
The Host Account ID is not the account number and must not be copied from staging to production.
Q2 passes through your primary theme color; other brand fonts and secondary styling are not configurable end to end.
For detailed technical documentation, see PayMitto developer documentation. This is on the developer portal, which needs a password. See Getting into the PayMitto developer portal.
4. Confirm the test environment and pilot audience
Before testing, confirm with PayMitto and Q2 which environment and core the app uses.
A staging Permanent Test Environment (PTE) connected to a production core moves real funds.
Forward also uses the production core and moves real funds; it is not a substitute for staging.
Work with PayMitto to verify both a send and a cancellation with refund in staging.
Your team controls app visibility by user group in Q2 Central.
Agree a small internal pilot group before production, rather than exposing the app to everyone.
App visibility and the account types allowed to fund transfers are separate controls.
5. Request production and verify it separately
After testing sign-off, your team requests production and confirms the production navigation details.
Your team and PayMitto each select Ready for Production on the app order; Q2 requires both actions.
PayMitto supplies the production configuration and verifies the production Host Account ID.
Set group access again in production; staging access does not carry over.
Confirm the production product IDs rather than assuming they match staging.
After the first production transfer, confirm the transaction description and code on the account holder's statement.
Expand access after the pilot passes, in line with your rollout plan.