Identities & Addresses
The Identities & Addresses tool in the DIDWW User Panel allows customers to add the End User information required for DID number registration processes, A2P SMS Campaigns activation, Emergency Calling service, CNAM ativation and number Porting. There are two types of identity bundles, Personal or Business. This bundle will contain End User’s information with uploaded proof documents, which will be encrypted and stored at DIDWW. Created identity bundles can then be reused to activate other services for the same End User.
Porting identity can created by following this guide. When creating the Porting Identity, validate if your provided data meets all Porting requirements of your selected country and number type as indicated in “Checking Requirements” section.
Identity hierarchy acts as a ranking system that determines which identity takes precedence over others when setting up services. There are several types of identities at DIDWW, which may be used and re-used to activate services. However, once the identity has been created/used to activate a service, it must be further used to activate other services for the same number and/or user. Porting identity is an exception which can be overriden by any other higher priority identity in the hierarchy.
The following identifies the priority in the identity hierarchy:
Number registration Identity (1)
A2P Campaign Identity (2)
Emergency calling Identity (2)
CNAM Identity (2)
Porting Identity (3)
The assigned identity is displayed in the DID Numbers section, Identity column :ref:
If the number registration identity is pending, it is not possible to assign it to other services (A2P, Emergency, CNAM). If the DID number does not require registration, other service identities can be assigned.
A2P Campaigns can only be registered with a Business identity. CNAM and Emergency calling service can be activated with either Personal or Business identities.
If you have i.e. CNAM set with Personal identity and would like to set A2P Campaign, you should remove Personal identity from CNAM service and proceed with A2P Campaign Business identity setup.
Creating a New Identity
A new identity can be created by navigating to the “Identities & Addresses” section on the left side menu of the DIDWW User Panel, and clicking on the “New Identity” button (Fig. 1).
A new window will appear, where you will be prompted to select a “Type of Identity” and enter the corresponding details (Fig. 2).
Once all details have been entered, scroll down to upload the documents of the associated identity (Fig. 3).
When uploading the documents you can select multiple files at once. See Attaching Files section for more information.
After the documents have been uploaded, click continue, and you will be prompted to enter the address details of the associated identity (Step 2) (Fig. 4).
Once all details have been entered, proceed to Proofs and click Add New where you will be prompted to upload the documents associated with the address (Fig. 5).
Customers can check the requirements for the DID number registration process when creating a new identity (Fig. 1)
Customers may check the requirements for DID Number portability process when creating a new Identity (Fig. 2)
End User details can be submitted during the purchase process. The verifications tab in the “Identities & Addresses” section will indicate the status of your DID number registration process.
Approved - indicates that end user details have been confirmed.
Pending - indicates that end user details verification process is pending.
Rejected - indicates that end user details have been rejected.
If the verification has been rejected, you can hover your mouse over the status “Rejected” and it will indicate the reason for rejection.
Attaching Multiple Files
When uploading the necessary documents, multiple files should be attached if the single documents is splitted to 2 parts. For example: pictures of drivers license, can be 2 separate files (front and back) (Fig.1).
The number of attached files will be displayed as follows (Fig. 2).
File content is encrypted with AES-CBC 256 bit, which is then being stored on our servers, where associated parties can decrypt it with personally provisioned private keys. All private keys are being kept on the hardware security module (HSM).