# FTM Chip Provider

## FTM Chip Provider

**Partner Management System (PMS) is used by both; PMS Admin and Partner User.**

* Partner Administrator: Partner Admin
* Partners: Partner User

### What all activities can a 'Partner Admin' perform for FTM Chip Provider?

Being a 'Partner Admin' you can perform following activities to complete the end to end functionality pertaining to Device Provider.

* Upload Root CA and Sub CA Certificates
* Approve/Reject FTM Chip

#### Upload Root CA and Sub CA

Only after Partner Admin 'Upload Root CA and Sub CA Certificates' that a Partner will then be able to **Upload CA signed Partner Certificate**.

As a process of Partner onboarding onto PMS after successful registration, Partner is required to **Upload CA signed Partner Certificate** on behalf of their organisation which would be used to build a trust store in MOSIP to cryptographically validate that they are from a trusted organisation.

**Certificate Authority (CA)** is an organization that acts to validate the identities of entities (in this case, a partner organisation) and bind them to cryptographic keys through the issuance of electronic documents known as digital certificates. A country needs to onboard valid CAs before onboarding any partner as MOSIP will only accept certificates which are signed only by a Trusted CA.

**Upload Root CA and Sub CA Certificates**

1. Go to **PMS Portal and login as Partner Admin**. Click on **Certificate Trust Store** in Admin dashboard

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-8aaac3a5bf40cddd187e4fc292aabcfa5e4ec95e%2Ftemp-pms-admin-image6.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Within Root CA tab - click on **Upload Trust Certificate** button on the top-right of the screen.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-7e751e96e44001f76fc07d058f182cfc2c068661%2Ftemp-pms-admin-image9.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Select the Partner Domain, (FTM)

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-ff3adcb341767354334df6b081e54cf7d902cfb9%2Ftemp-pms-admin-image13.png?alt=media" alt=""><figcaption></figcaption></figure>

4. Choose the **Root CA Certificate** to upload (only files with extensions as .cer or .pem).

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-a333cdb5b61f9f4858621ae903f32787bccffbd6%2Ftemp-device-provider-image4.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-199b3367f28b3b627aeca89d0a21ced3a6dda624%2Ftemp-ftm-chip-provider-image5.png?alt=media" alt=""><figcaption></figcaption></figure>

5. Click Submit and an appropriate success message appears.
6. Similarly, Sub/Intermediate CA certificate should be uploaded by following the above steps (2-4) by navigating to **Upload Intermediate CA Certificate** button provided within Intermediate Root CA tab.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-ff3adcb341767354334df6b081e54cf7d902cfb9%2Ftemp-pms-admin-image13.png?alt=media" alt=""><figcaption></figcaption></figure>

#### What all activity can a Partner (FTM Chip Provider) perform?

To be able to access the services by PMS and to validate that the partner is from a trusted organisation, undergoing self registration on PMS and uploading CA signed certificate is necessary. Here is what you are able to do as FTM Chip Provider:

* Self Register on PMS Interface
* Upload CA signed Certificate

**Self-Register on PMS as FTM Chip Provider**

1. The FTM Chip Provider can register themselves on MOSIP PMS portal by clicking **Register** on the Login Page, a form comes up.
2. Enter the FTM Chip Provider details:
   1. Partner type (FTM Provider)
   2. First and Last name
   3. Organization Name
   4. Address, Phone number
   5. e-mail, Username and password

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-e08164446a4d2c5284f3a3d4c476b7dffa354228%2Ftemp-ftm-chip-provider-image6.png?alt=media" alt=""><figcaption></figcaption></figure>

3. **On successful registration**, you will be asked to read through '**Terms and Conditions**' and having carefully read through it you can agree and accept it.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-5dc48200da023e4b653ba2b8519a73b83c20a7e7%2Ftemp-device-provider-image8.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Validations**:

* Terms & Conditions: Partner consent refers to voluntary and informed agreement provided by a partner user on behalf of the Partner Organisation, to a specific action or process where the users have a clear understanding of what they are consenting to. User consent is important to ensure data privacy, where it is compliant to obtain explicit consent from partners before collecting, processing, or sharing their personal / organisation level data.
* A detailed description explaining which of their personal and organisation data is used and for what purposes it will be used in PMS will be informed while seeking user consent.
  {% endhint %}

**Login:**

* For existing partner users who are already registered in Partner Management System, they can login to the portal with their email, username and password.
* On logging in you come to Partner Dashboard (considering the pre-requisites such as policy group selection and consent are already completed).

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-052c6db120a4e8e05d0c657f35b030880a277d2a%2Ftemp-device-provider-image9.png?alt=media" alt=""><figcaption></figcaption></figure>

**Forgot Password:**

* Partner user has an option to reset password , you can use it when you forget password or want to change password after a certain duration.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-05b7043188a1bc16d2d566a85511acd7274d2552%2Ftemp-device-provider-image10.png?alt=media" alt=""><figcaption></figcaption></figure>

### CA Signed Partner Certificate Upload / Download or Re-Upload

User is now in [Home Page/Dashboard](https://docs.mosip.io/1.2.0/modules/partner-management-services/pms-revamp/functional-overview/auth-partner/end-user-guide#interface-overview) where the following features are provided to FTM Chip Provider:

1. Partner Certificate
2. FTM Chip Provider Services

These features can also be accessed by clicking on side panel (in the form of icons) or clicking on the hamburger menu on the top left which is available across all screens of PMS to help user easily navigate.

Once registered as a process of Partner onboarding onto PMS after successful registration, user is required to **Upload CA signed Partner Certificate** on behalf of their organisation which would be used to build a trust store in MOSIP to cryptographically validate that they are from a trusted organisation.

{% hint style="info" %}
**Tips**:

Later when required a Partner can also 'Download Certificate' and 'Re-Upload Certificate' (As the need may be).
{% endhint %}

{% hint style="info" %}
**Important**:

Before a Partner can upload a 'CA Signed Certificate' it is prerequisite that the 'Partner Admin' should have already had uploaded the **Root CA** and **Intermediate CA** certificates.
{% endhint %}

### Upload CA signed Certificate

1. Go to **FTM Provider** > **Dashboard**.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-441c536b248539e1efeea143e72620ad37219b2f%2Ftemp-ftm-chip-provider-image10.png?alt=media" alt=""><figcaption></figcaption></figure>

2. Click on **Partner Certificate** option, Click on the **Upload** button to upload the partner certificate signed by CA.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-b15c05186904a0fe1e8f13d7412cf180fac194cc%2Ftemp-ftm-chip-provider-image11.png?alt=media" alt=""><figcaption></figcaption></figure>

3. Select the CA signed partner certificate from local system by tapping on the upload section (blue area).

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-6288e3e59cce8cfa7508419f87276f431315e39b%2Ftemp-ftm-chip-provider-image12.png?alt=media" alt=""><figcaption></figcaption></figure>

4. The required certificate is selected from the local system.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-960737c007b17e6bc7e43c34c3041e9969aeea3c%2Ftemp-ftm-chip-provider-image13.png?alt=media" alt=""><figcaption></figcaption></figure>

5. Certificate is successfully fetched from local system.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-552328a8cd41392e7b76ea6af8f6912b9f1642e4%2Ftemp-ftm-chip-provider-image14.png?alt=media" alt=""><figcaption></figcaption></figure>

6. Click on **Submit**, Partner Certificate is uploaded successfully.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-2d49bc49507c8560d325c770c05b89cf348a51f8%2Ftemp-ftm-chip-provider-image15.png?alt=media" alt=""><figcaption></figcaption></figure>

7. On closing the popup, The user can view the uploaded certificate details in the form of a list view.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-6179b9099632e3bd1b58022de9ada5f85b54c07c%2Ftemp-ftm-chip-provider-image16.png?alt=media" alt=""><figcaption></figcaption></figure>

### Download Certificate

There is also an option to download initially uploaded CA signed certificate and also the MOSIP Signed Certificate.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-0636627afa9de7646fa26fe2715443babf19c221%2Ftemp-ftm-chip-provider-image17.png?alt=media" alt=""><figcaption></figcaption></figure>

Success Message is displayed on successful download of Originally uploaded certificate/ MOSIP Signed Certificate.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-d44bfea26066be32f676e93cb65b5d49de6e4d5f%2Ftemp-ftm-chip-provider-image18.png?alt=media" alt=""><figcaption></figcaption></figure>

On closing the popup the user can view the uploaded certificate details in the form of a list view.

### Download Certificate

There is also an option to download initially uploaded CA signed certificate and also the MOSIP Signed Certificate.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-d0e0848a3198a0f103ad04a64d67743edaf06385%2Ftemp-ftm-chip-provider-image19.png?alt=media" alt=""><figcaption></figcaption></figure>

### Re-Upload Certificate\*\*

Re-uploading certificate is required in cases when MOSIP Signed Certificate gets expired after one year.

{% hint style="info" %}
**Note:**

'MOSIP Signed Certificate has a validity of 1 year from the time of Partner Certificate Upload.
{% endhint %}

You must ensure that you re-upload the partner certificate again so that new MOSIP signed certificate can be generated and other functionalities such as FTM Chip Provider Services can function.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-a3cb75a97fb13101b557cb8e9e00674a71b29048%2Ftemp-ftm-chip-provider-image20.png?alt=media" alt=""><figcaption></figcaption></figure>

The rest of the steps is same as covered in Upload Certificate flow (Step 3-7)

## FTM Chip Provider Services

After the partner has uploaded partner certificate he can now perform 'FTM Chip Provider Services':

* **Add** FTM Chip details and **upload** the FTM Chip certificate for the request to be sent to partner admin for approval.
* **Deactivate** FTM details.
* **Re-upload** and **Download** FTM Chip Certificate.

### **Add FTM Chip:**

You can add details of Foundational Trust Module (FTM) chip by clicking on 'Add FTM Chip' button which takes you to 'Add FTM Chip Details' screen.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-b50c00604c1aef0610f41bd63d685869ac3d363b%2Ftemp-ftm-chip-provider-image21.png?alt=media" alt=""><figcaption></figcaption></figure>

The partner is expected to enter the make and model of FTM Chip and submit the details.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-4f60e8f89a142eff06da75de1bda3ead1cbe81f4%2Ftemp-ftm-chip-provider-image22.png?alt=media" alt=""><figcaption></figcaption></figure>

After successful submission of FTM Chip details, the partner is prompted to click on 'Upload FTM Chip Certificate' to proceed further.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-256109730004702db26f0e19e8e34ffdb2e04514%2Ftemp-ftm-chip-provider-image23.png?alt=media" alt=""><figcaption></figcaption></figure>

The partner clicks on the Upload section to select the FTM Chip Certificate from local system.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-9d51a5d2339a09f70116fe764a3cdcd7bab10c41%2Ftemp-ftm-chip-provider-image24.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-0ab8c5bfc59b9d9fbcac05dc2e1b9f3e05c7885c%2Ftemp-ftm-chip-provider-image25.png?alt=media" alt=""><figcaption></figcaption></figure>

After selection, the uploaded certificate is displayed on screen which the partner has to submit.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-c2b76f825a0fdad6dba712f9afa73ef4bad58810%2Ftemp-ftm-chip-provider-image26.png?alt=media" alt=""><figcaption></figcaption></figure>

A success message on successful submission is displayed on the screen.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-7b9db84a011058c64ff7dee551aa78cf4147caf0%2Ftemp-ftm-chip-provider-image27.png?alt=media" alt=""><figcaption></figcaption></figure>

On click of Close you come back to List of FTM Chip details page where the status of the record is in 'Pending for Approval status'.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-1a8188fff5acf8fd9de878231bf591520a45dc5b%2Ftemp-ftm-chip-provider-image28.png?alt=media" alt=""><figcaption></figcaption></figure>

Let's assume, the certificate upload process was not carried out after adding FTM details due to a technical issue / unexpected closing of the PMS portal. At such instances, while navigating to FTM Chip Services Dashboard → List of FTM Chip details, the given record is found to be in 'Pending for Certificate Upload' status. Which means that without the certificate upload the record will not go to admin for approval..

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-e0594c33981746c34fd10127d4d0967ca8329fd4%2Ftemp-ftm-chip-provider-image29.png?alt=media" alt=""><figcaption></figcaption></figure>

To upload the FTM Chip certificate, select the Manage Certificate option from action menu.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-11db90fd5875de80611d2a26ee9aef58437085aa%2Ftemp-ftm-chip-provider-image30.png?alt=media" alt=""><figcaption></figcaption></figure>

The partner is navigated to Manage FTM Chip certificate page where on clicking upload button, the partner can upload the certificate by following the same steps as mentioned above.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-567130329369c8474c638ca587714029fcfbf49e%2Ftemp-ftm-chip-provider-image31.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-39585ee50f0d6c3fdf1aec838a9e16fcea4831ac%2Ftemp-ftm-chip-provider-image32.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-45bbfd0cc4a52ec197a93335747affb37a8508ab%2Ftemp-ftm-chip-provider-image33.png?alt=media" alt=""><figcaption></figcaption></figure>

Once the upload is complete - the record moves to 'Pending for Approval' status where the Partner Admin can take appropriate action by approving / rejecting this entry.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-1a8188fff5acf8fd9de878231bf591520a45dc5b%2Ftemp-ftm-chip-provider-image28.png?alt=media" alt=""><figcaption></figcaption></figure>

### Partner Admin

To approve / reject an FTM Chip, admin clicks on 'FTM Chip' card in his homepage.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-4a42d20f7a7e98a42d8c8fe7cd32bf2fd76e5496%2Ftemp-ftm-chip-provider-image34.png?alt=media" alt=""><figcaption></figcaption></figure>

The admin navigates to 'List of FTM Chip details' page where list of all FTM Chip records submitted so far by different FTM Chip providers are displayed.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-d18ede35bde16cb3f018c8f2b374eeee8008fa82%2Ftemp-pms-admin-image85.png?alt=media" alt=""><figcaption></figcaption></figure>

On clicking the action menu of the respective FTM Chip record, an option 'Approve/ Reject' is provided.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-15cf94a3d8be873cc8f6da919901f6a81b5adf86%2Ftemp-pms-admin-image86.png?alt=media" alt=""><figcaption></figcaption></figure>

A popup window appears for the admin to take appropriate action- Approve / Reject and select the respective button.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-7f9344c9e10b421a98a3f70457e483b63d6d31f6%2Ftemp-pms-admin-image87.png?alt=media" alt=""><figcaption></figcaption></figure>

The status is thus updated accordingly in **List of Devices** Page as Approved / Rejected based on the above action.

{% hint style="info" %}
**Note**:

'Pending for Approval' status is displayed when the FTM Chip request is pending with admin for approval and no action has been taken by admin yet.
{% endhint %}

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-b3d673efb43ea3787d8c75fcaf6d1e808caf2538%2Ftemp-pms-admin-image88.png?alt=media" alt=""><figcaption></figcaption></figure>

### Manage Certificate for approved records

Once the FTM Chip record is approved, FTM Chip Provider can click on Manage Certificate option in action menu so that the partner can download / reupload the FTM Chip certificate in Manage FTM Chip Certificate page.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-66d73f241e4633b69e23c8482c7d62cb89906964%2Ftemp-ftm-chip-provider-image39.png?alt=media" alt=""><figcaption></figcaption></figure>

To re-upload certificate after expiry or otherwise, click on Re-Upload button.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-fdb0f2d1fe683e3befb9894aa06e8c5485b5a133%2Ftemp-ftm-chip-provider-image40.png?alt=media" alt=""><figcaption></figcaption></figure>

Follow the same steps as upload flow to perform the reupload functionality.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-65e3737f8f0fbf28b0db8308fdffa8858da6f03a%2Ftemp-ftm-chip-provider-image41.png?alt=media" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-5637fbabd9e8fc69490c8398a4e50c8b1eb6bdb9%2Ftemp-ftm-chip-provider-image42.png?alt=media" alt=""><figcaption></figcaption></figure>

After reupload of certificate is successfully completed, the status again changes to 'Pending for Approval' as the renewed certificate needed to go through admin check for the FTM Chip record to be validated.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-4926217ce13a954acbd035d50dc8c049299e81fc%2Ftemp-ftm-chip-provider-image43.png?alt=media" alt=""><figcaption></figcaption></figure>

Every Approved FTM Chip record has a download option provided to download the FTM Chip certificate at any given time.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-dd2188e5844a8780cce398beed8e525cdf89ff5f%2Ftemp-ftm-chip-provider-image44.png?alt=media" alt=""><figcaption></figcaption></figure>

on click of download button, a success message is displayed on the screen.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-61a3c8a1e4e11b617ebc7360d7d1357cb149ed35%2Ftemp-ftm-chip-provider-image45.png?alt=media" alt=""><figcaption></figcaption></figure>

### Deactivate FTM Chip

Partner / Partner Admin can deactivate an active FTM Chip any time provided it is in 'Approved' status. To perform deactivation, click on 'Deactivate' option in the action menu of the given FTM Chip in 'List of FTM Chip details' page.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-b1e61f67195a2df4d92b3e340e1e0a2f90759b78%2Ftemp-ftm-chip-provider-image46.png?alt=media" alt=""><figcaption></figcaption></figure>

On clicking 'Deactivate', a popup window appears seeking for confirmation and appropriate info text is displayed.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-8e42a85c68ee09d7aea8ad8d5694687cfcdecc17%2Ftemp-ftm-chip-provider-image47.png?alt=media" alt=""><figcaption></figcaption></figure>

On deactivation , the status changes to 'Deactivated' status.

<figure><img src="https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-a62e0a5b7d9496c5b74cd2ab61d185c94ee148c3%2Ftemp-ftm-chip-provider-image48.png?alt=media" alt=""><figcaption></figcaption></figure>
