Instructions for Deploying the App to Production

1

Review Code and Dependencies:

  • Ensure that all dependencies and libraries are up to date.

  • Verify that the code has been reviewed and validated to prevent security vulnerabilities.

2

Production Settings:

  • Update the configuration file to point to the production backends e.g., gwpay-prod.first-tech.net.

  • Ensure that logs are set to the appropriate level, avoiding unnecessary exposure of sensitive information.

  • Open a ticket with First Tech, providing the Package Name, SHA-256, and Version Code of the product for production enablement. This process may take 5 to 7 days, so we recommend opening the ticket as soon as these details are available to streamline the deployment.

To obtain this information:

Package Name: This information can be found in the build.gradle file of your app's module.

Variable path: android >> defaultConfig >> applicationId

Figure 19: Location of the applicationId and versionCode Variables in the Build.Gradle File

SHA-256: This information can be obtained from the Google Play Console:

  • Access the application's page

Figure 20: Main Application Page on the Google Play Console Website

Access the menu

  • Navigate to Test & Release >> Setup >> App Signing

Figure 21: App Signing Page of the Application on the Google Play Console Website

In the "App Signing Key Certificate" section:

  • The SHA-256 hash can be found in the "SHA-256 Certificate Fingerprint" field.

Figure 22: Location where the SHA-256 is generated and should be copied from.

Version Code: This can be found in the build.gradle file of your app's module. Variable path: android >> defaultConfig >> versionCode

3

Credentials and Certificates:

  • Enter the appropriate credentials for the production environment, provided by First Tech or the acquirers.

  • Verify the validity of the certificates and encryption keys being used.

4

Final Testing:

  • Perform final tests on real devices to ensure the application works as expected.

  • Simulate real transaction scenarios to validate the complete flow, from payment to authorization.

5

Privacy Policy and Terms of Use:

  • Ensure that the application includes a clear privacy policy and terms of use, as required by local regulations.

6

Publication on Google Play Store:

  • Review all app metadata, including name, description, screenshots, and category.

  • Configure app permissions correctly to avoid rejections during the store review process.

  • Submit the APK/AAB for review and wait for Google Play approval.

7

Post-Launch Monitoring:

  • Set up monitoring tools to track app performance, such as Firebase or Sentry.

  • Monitor error logs and crash reports to quickly identify and fix potential issues.

Last updated