The Settings tab in the DSCSA Product Verification & Tracing application allows you to configure the Verification Router Service (VRS) settings when the tenant in Movilitas.Cloud is the verification requester and you want to verify packs by using Movilitas Mobile:
- Requester GLN. Note: The GLN is also used in trace requests initiated from the mobile application.
- Activating verifiable credentials through CARO (Spherity) or XATP (LedgerDomain).
- If your company is not onboarded in CARO (Credentialing of ATP for Regulatory Observance) yet, it is possible to initiate the tenant creation in CARO from Movilitas.Cloud.
- To apply verifiable credentials, you need to provide the assets (digital identifier, API key) received from CARO or XATP.
- Activating the verification of the responder.
- Providing a Scandit license to use matrix scanning (installed mobile application only).
List of Procedures
Creating a Tenant in CARO
To obtain and use a verifiable credential for your verification request, you need to own a digital identifier (DID) in a digital wallet provider (for example, CARO) as per your state license.
In CARO, the digital identifier is assigned to a tenant (ATP enterprise account), and the tenant is linked to a VRS provider (Movilitas.Cloud).
If you do not have a tenant in CARO, Movilitas.Cloud enables you to first initiate the tenant creation in CARO. Then, CARO will contact you for further details. In the end, you will have a digital identifier (DID) that is essential to apply a verifiable credential in your verification request.
Note: Only applicable when CARO (Spherity) is your digital wallet provider. Tenant creation in XATP (LedgerDomain) from Movilitas.Cloud is not supported. If you want to connect to XATP, skip this procedure and do the onboarding outside Movilitas.Cloud.
Procedure
1. Select the DSCSA Product Verification & Tracing application --> Settings tab. The application displays the settings.
The following example illustrates the case when the Settings page is not yet configured:
2. Click Create Tenant on CARO. The application displays a pop-up window to confirm the action.
3. Click Yes.
Movilitas.Cloud sends the enterprise name (tenant in Movilitas.Cloud) and the email of the logged-in user to CARO.
If the request is successful, the button disappears and the application displays the following text in green at the bottom of the screen: Tenant request is successful. You will be contacted by CARO for further details. Please check your mail.
Next Steps
Once the tenant is set up in CARO and you have a valid DID, you are ready to configure the settings.
Back to the list of procedures
Configuring the Settings
Before You Begin
If you want to apply a verifiable credential in your verification request, make sure that you own the necessary assets:
- A valid digital identifier (DID) in CARO or in XATP.
- An API key (XATP only).
If you want to use matrix scanning in the mobile application, obtain a Scandit license. You will need to add the Scandit license key.
Procedure
1. Select the DSCSA Product Verification & Tracing application --> Settings tab. The application displays the settings.
The following example illustrates the case when the Settings page is not yet configured but a request to create a tenant in CARO was sent because the Create Tenant on CARO button is not displayed:
Note: If you want to connect to XATP for the verifiable credential and not to CARO or you have not initiated a tenant creation in CARO from Movilitas.Cloud, the application displays the Create Tenant on CARO button at the bottom left corner until a digital identifier is provided.
2. Provide the requester GLN in the GLN field. The GLN is added to each request.
3. To include verifiable credentials in the verification requests, select the Enable Verifiable Credentials checkbox. The application displays the Select identifier drop-down.
4. In the Select identifier drop-down, manage your digital identifiers (DIDs) that were created in CARO or in XATP.
| Action | Description |
|---|---|
| Add an identifier | 1. Click on the Select identifier drop-down. Example:  2. Click Add new +. The application displays the Add new identifier window. 3. Select the ATP wallet provider.
4. Based on the selected provider, add the identifier details.
CARO example:  5. Click Add. |
| Edit an identifier | 1. Click on the Select identifier drop-down and click on the edit icon next to the identifier. Example:  2. In the Update identifier pop-up, modify the fields as needed. CARO example:  3. Click Update. |
| Delete an identifier | 1. Click on the Select identifier drop-down and click on the delete icon next to the identifier. Example:  The application deletes the identifier immediately without any confirmation request. |
| Select an identifier | 1. Click on the Select identifier drop-down. 2. Select an identifier from the list. |
5. To activate verifying the responder, select Enable Verification Responder.
When the checkbox is selected and the operator scans a pack for verification in the mobile application, the application checks whether the verification response is from a valid Authorized Trading Partner (ATP).
6. (Optional) To use matrix scanning in the installed version of the mobile application, enter the Scandit license key in the Scandit License field.
Example:
7. Click Save Settings.
Next Steps
Assign the operators that use the mobile application. After the operators are assigned, the operators can scan the packs for verification or initiate a trace request.
You can view the verification requests by going to the Reports & Analysis application --> DSCSA --> VRS --> Requests tab.
You can download the JSON file of a trace request that is initiated from the mobile application by going to the Reports & Analysis application --> Trace Request tab.
Back to the list of procedures
