> For the complete documentation index, see [llms.txt](https://docs.plumvoice.com/fuse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plumvoice.com/fuse/data-security/managing-secure-phone-numbers.md).

# Managing Secure Phone Numbers

## Phone Numbers in a Secure Environment

### PCI Numbers

Plum Voice hosts Fuse applications that require PCI-compliance in a secure environment on PCI-compliant servers. This environment is on a completely separate network from out non-PCI servers. 

Any phone numbers originally provisioned within Plum's PCI environment can be used to deploy Fuse applications that have PCI security requirements. Typically, provisioning requests sent directly to <provisioning@plumgroup.com> that explicitly request PCI-compliant phone numbers fall into this category.

Throughout the Fuse interface, PCI numbers are generally listed with a PCI symbol (![](/files/dgqwR1oSYLzPRDxEfTDy)).

### **Converting Non-PCI Numbers to PCI**

{% hint style="danger" %}
Customers **cannot** use Plum's PCI-environment for testing or QA purposes.
{% endhint %}

Any phone numbers used for testing and QA purposes, and the application associated with them, are non-PCI numbers and hosted on non-PCI servers.

It is possible to convert a non-PCI number to a PCI-compliant number. To move a non-PCI phone number to the PCI environment for production use, [contact Plum Support](https://portal.plumvoice.com/hc/en-us#) to initiate the migration process.&#x20;

Once the migration process completes, the application associated with the number **must be re-deployed** in order to migrate the application to Plum's PCI servers.&#x20;

To re-deploy an application:

* Go to **Deployments.**
* Select the desired application in the list and click the **Edit Deployment** button.
* In the **Edit Deployment** menu, select the **New Revision** drop-down menu and change that option to **latest** then click **Update.**&#x20;

<div align="left"><img src="/files/-MAgRAHDgUheI4wdbYVi" alt=""></div>

* Go to **Applications.**
* Locate the application corresponding to your deployment and open it in the Application Editor.
* Click the yellow **Save** button <img src="/files/-M4u9_1cg5ytUjBIBgqk" alt="" data-size="line"> in the top right corner to update the revision.

<div align="left"><img src="/files/-MAgQZnaPaNq-SKr3T4-" alt=""></div>