> For the complete documentation index, see [llms.txt](https://ftcoders.first-tech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ftcoders.first-tech.com/first-tech-ttp-sdk/developer-zone/instructions-for-deploying-the-app-to-production.md).

# Instructions for Deploying the App to Production

{% stepper %}
{% step %}

### **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.**
  {% endstep %}

{% step %}

### **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><img src="/files/uSKWgohVDLkknZMLospj" alt=""><figcaption><p><strong>Figure 19: Location of the <code>applicationId</code> and <code>versionCode</code> Variables in the Build.Gradle File</strong></p></figcaption></figure>

**SHA-256:** This information can be obtained from the [**Google Play Console**](https://play.google.com/console/u/0/developers):

* **Access the application's page**

<figure><img src="/files/DWdwkdFRF9DMNLP0y0vt" alt=""><figcaption><p><strong>Figure 20: Main Application Page on the Google Play Console Website</strong></p></figcaption></figure>

**Access the menu**

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

<figure><img src="/files/17mStxv7io2uf3P1pGe3" alt=""><figcaption><p><strong>Figure 21: App Signing Page of the Application on the Google Play Console Website</strong></p></figcaption></figure>

In the **"App Signing Key Certificate"** section:

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

<figure><img src="/files/cKhmw1oTzghuoKGFBYRP" alt=""><figcaption><p><strong>Figure 22: Location where the SHA-256 is generated and should be copied from.</strong></p></figcaption></figure>

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

<figure><img src="/files/ijQhq7ooobb4HzUfFiwv" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### **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.
  {% endstep %}

{% step %}

### **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.
  {% endstep %}

{% step %}

### **Privacy Policy and Terms of Use:**

* **Ensure that the application includes a clear privacy policy and terms of use**, as required by local regulations.
  {% endstep %}

{% step %}

### **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**.
  {% endstep %}

{% step %}

### **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.
  {% endstep %}
  {% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ftcoders.first-tech.com/first-tech-ttp-sdk/developer-zone/instructions-for-deploying-the-app-to-production.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.