Movilitas DSCSA is a free mobile application for distributors and dispensers in the USA market to verify packs.


You can verify a pack by giving your company GLN and contact details. It is also possible to verify a pack with ATP credentialing in the background. For ATP credentialing, you must have a state license to obtain a DID from an ATP wallet provider. If there is no DID yet, you can initiate the account registration in an ATP wallet provider through the application.


List of Procedures


Downloading and Installing Movilitas DSCSA from the Application Store


You can install Movilitas DSCSA from the app store of your device (Android or iOS).


Android requirements:

  • OS Android 5.1+ with Chromium 89+
  • Android System WebView (version 60)
  • Processor Dual Core
  • RAM 2GB
  • Network required
  • Storage 150MB free storage


iOS requirements:

  • OS iOS 15.0+
  • Processor Dual Core
  • RAM 2GB
  • Network required
  • Storage 150MB free storage


Procedure


1. Open the Application Store of your mobile device.

  • Google Play for Android.
  • App Store for iOS. To install apps, you must sign in with your Apple ID and password or you must create an account.


2. Search for Movilitas DSCSA application.


3. Select Movilitas DSCSA from the results.


Google Play Store example:



4. Install Movilitas DSCSA.

  • For Android, tap Install.
  • For iOS, tap Get.


Back to the list of procedures



Registering the User Details


Before You Begin


Make sure you own a GLN.


Procedure


1. Open Movilitas DSCSA mobile. The application displays the User details page.


The following example illustrates the case after the application is installed and opened for the first time:



2. Enter the user details:

  • GLN
  • Email address
  • Phone


Example:



3. Tap Save.


The application saves the user details.


Next Steps


Verify a pack. For more information, see Verifying a Pack without a Verifiable Credential.


If the VRS responder requires a verifiable credential with the request, but you don't have one, the responder returns an error message. We strongly recommend you request a verifiable credential from an ATP wallet provider (CARO or XATP) through our application. For more information, see Requesting a DID.


Back to the list of procedures



Requesting a DID


Procedure


1. Open Movilitas DSCSA mobile.


2. Select the burger menu in the top-right corner of the screen. The application displays the options.


Example:



3. Select Request credentials.


The application displays the Request DID page. You can request a DID from CARO or XATP. By default, the CARO tab is selected.


CARO Example:




4. (Optional) For more information on DSCSA USA, tap on the blue message. 


You are redirected to a Movilitas.Cloud website explaining DSCSA. To return to the Request DID page, close the website by tapping X.


Example:



5. On the Request DID page, select your ATP wallet provider to obtain the DID:

  • CARO (default)
  • XATP


XATP Example:



6. Provide the contact information:


TabContact Information to Give
CARO
  • Email address
  • Company name
XATP
  • Email address
  • GLN


CARO Example:



XATP Example:



7. Tap Request. The application returns a green message: Registration successful.


The registration is initiated for the selected ATP wallet provider as follows:


TabSystem Actions
CARO
  • A tenant (business account) is automatically created in CARO.
  • CARO returns an email to activate your account.
XATP
  • An email is sent to Movilitas.Cloud Sales to set up a tenant (business account) in XATP.


8. Complete the registration in the ATP wallet provider:

  • For CARO, activate your account through email and follow the instructions from CARO.
  • For XATP, follow the instructions from Movilitas.Cloud Sales and XATP.


Next Steps


Once the tenant is set up in CARO or XATP and you have a valid DID, you can register the credential details. For more information, see Registering the Credential Details.


Back to the list of procedures



Registering the Credential Details


Procedure


1. Open Movilitas DSCSA mobile.


2. Select the burger menu in the top-right corner of the screen. The application displays the options.


Example:



3. Select Credential details.


The application displays the Verifiable credentials page:

  • You can enter the credential details.
  • For the first time, when credential details are not yet filled in, the application displays the section Don't have a DID? Request one now! at the bottom of the page. By selecting Request DID, you are redirected to the Request DID page. For more information, see Requesting a DID.


Example:



4. Enter the credential details:

  • DID
  • API Key (XATP only).


CARO Example:



5. Tap Save.


The credential details are saved.


Next Steps


Verify a pack. For more information, see Verifying a Pack with a Verifiable Credential.


Back to the list of procedures



Verifying a Pack without a Verifiable Credential


Procedure


1. Open Movilitas DSCSA mobile.


The application displays the following:

  • A yellow message that requesting a verifiable credential from CARO or XATP is recommended. By tapping on the yellow message, you are redirected to the Request DID page. For more information, see Requesting a DID.
  • The Product in your possession toggle button (ON by default)
  • The Context setting.


The following example illustrates the case when the context is not selected:



2. Confirm that the product is in the possession of your company (default setting). Otherwise, turn off the Product in your possession toggle button.


Note: If the product is not in the possession of your company, the responder may reject giving a response. 


3. Select the context.


ContextWhen to Use?
Verification for saleable returnRequester is seeking to understand the status of a product that is a saleable return prior to further transacting the product.
Verification of suspect or illegitimate productRequester is performing a verification as all trading partners must perform verification of a product identifier as part of their obligation to investigate suspect and illegitimate products.
Verification after exception arises with the productRequester is seeking to verify a product after an exception arises with the product in question.
Verification of the product statusRequester is seeking to understand the status of a product that is not a saleable return or known to be suspect or illegitimate.


Example:



4. Select OK.


5. Scan the item.

  • For a mobile device with a camera only, tap Scan Item and use the built-in camera of your device for reading the barcode.
    • Note: Before the first scanning, the application might request access to the camera that you need to allow (one-time activity).
  • For a mobile device with a built-in scanner (next to a camera), use the toggle button to switch between the scanner or camera mode. By default, the application chooses the scanner mode and you need to press the physical button on the device and point the reader at the barcode to scan. The GUI button Scan Item is only displayed in the camera mode.


The request is routed to the responder. Once the response is available, the application displays the following:


GUI SectionDescription
Scanned pack dataThe application displays the pack data:
  • Serial number
  • Batch
  • Expiration date
  • GTIN (Product code)


The application displays a status indicator in line with the verification result:

  • Green checkmark icon - The pack is valid.
  • Red no entry icon - The pack is not valid.
  • Red exclamation mark icon - There is an error in the verification process.
Response dataThe application displays the verification result for the pack:
  • The pack is valid versus not valid (true or false).
  • The responder Global Location Number (GLN).
  • The timestamp of the verification.
  • The verification failure reason (when the pack is not valid). Note: For product identifier mismatch, the responder may not provide a reason.
  • The additional information (if any).
When there is an error in the verification process, the application displays an error message.
ATP Verification ResponseThe application displays the verification result for the Authorized Trading Partner (ATP) that acts as the responder:
  • The ATP is valid versus not valid (true or false).
  • The timestamp of the verification.
  • The ATP details when the ATP is valid (true).
  • The verification failure reason when the ATP is not valid (false).


The application displays a status indicator in line with the verification result:

  • Green checkmark icon - The ATP is valid (true).
  • Red no entry icon - The ATP is not valid (false).


Note: Applicable when verification of the responder is activated in the application settings and the response includes verifiable credentials.
Contact InformationDisplays the responder's contact information:
  • Contact email
  • Contact phone number


When one of the contact data is not provided, the application displays Not available for that contact field. The responder shall provide at least one of the contact data. Otherwise, the responder cannot respond and the application displays an error message.


The following example illustrates the verification of a pack. The mobile device has only a camera (no built-in scanner). The pack is valid. Because the requester did not provide a verifiable credential in the request, the ATP responder information is not included in the response:



For more information about verification failure reasons and additional information related to the pack, see VRS Responses for the Pack (Verification Failure Reason and Additional Info).


For more information on verification errors, see Verification Error Handling.


If the product is not found in the Lookup Directory, the application returns the following message: GTIN not found. Contact support@movilitas.cloud.


Back to the list of procedures



Verifying a Pack with a Verifiable Credential


Procedure


1. Open Movilitas DSCSA mobile.


The application displays the following:

  • The Product in your possession toggle button (ON by default)
  • The Context setting.


The following example illustrates the case when the context is not selected:



2. Confirm that the product is in the possession of your company (default setting). Otherwise, turn off the Product in your possession toggle button.


Note: If the product is not in the possession of your company, the responder may reject giving a response. 


3. Select the context.


ContextWhen to Use?
Verification for saleable returnRequester is seeking to understand the status of a product that is a saleable return prior to further transacting the product.
Verification of suspect or illegitimate productRequester is performing a verification as all trading partners must perform verification of a product identifier as part of their obligation to investigate suspect and illegitimate products.
Verification after exception arises with the productRequester is seeking to verify a product after an exception arises with the product in question.
Verification of the product statusRequester is seeking to understand the status of a product that is not a saleable return or known to be suspect or illegitimate.


Example:



4. Select OK.


5. Scan the item.

  • For a mobile device with a camera only, tap Scan Item and use the built-in camera of your device for reading the barcode.
    • Note: Before the first scanning, the application might request access to the camera that you need to allow (one-time activity).
  • For a mobile device with a built-in scanner (next to a camera), use the toggle button to switch between the scanner or camera mode. By default, the application chooses the scanner mode and you need to press the physical button on the device and point the reader at the barcode to scan. The GUI button Scan Item is only displayed in the camera mode.


The request is routed to the responder. Once the response is available, the application displays the following:


GUI SectionDescription
Scanned pack dataThe application displays the pack data:
  • Serial number
  • Batch
  • Expiration date
  • GTIN (Product code)


The application displays a status indicator in line with the verification result:

  • Green checkmark icon - The pack is valid.
  • Red no entry icon - The pack is not valid.
  • Red exclamation mark icon - There is an error in the verification process.
Response dataThe application displays the verification result for the pack:
  • The pack is valid versus not valid (true or false).
  • The responder Global Location Number (GLN).
  • The timestamp of the verification.
  • The verification failure reason (when the pack is not valid). Note: For product identifier mismatch, the responder may not provide a reason.
  • The additional information (if any).
When there is an error in the verification process, the application displays an error message.
ATP Verification ResponseThe application displays the verification result for the Authorized Trading Partner (ATP) that acts as the responder:
  • The ATP is valid versus not valid (true or false).
  • The timestamp of the verification.
  • The ATP details when the ATP is valid (true).
  • The verification failure reason when the ATP is not valid (false).


The application displays a status indicator in line with the verification result:

  • Green checkmark icon - The ATP is valid (true).
  • Red no entry icon - The ATP is not valid (false).


Note: Applicable when verification of the responder is activated in the application settings and the response includes verifiable credentials.
Contact InformationDisplays the responder's contact information:
  • Contact email
  • Contact phone number


When one of the contact data is not provided, the application displays Not available for that contact field. The responder shall provide at least one of the contact data. Otherwise, the responder cannot respond and the application displays an error message.


The following example illustrates the verification of a pack. The mobile device has only a camera (no built-in scanner). The pack is valid and the ATP responder information is also displayed:



For more information about verification failure reasons and additional information related to the pack, see VRS Responses for the Pack (Verification Failure Reason and Additional Info).


For more information on verification errors, see Verification Error Handling.


If the product is not found in the Lookup Directory, the application returns the following message: GTIN not found. Contact support@movilitas.cloud.


Back to the list of procedures



Managing User Details


Procedure


1. Open Movilitas DSCSA mobile.


2. Select the burger menu in the top-right corner of the screen. The application displays the options. 


Example:



3. Select User details.


The application displays the User details page with the saved configuration.


Example:



4. Update your user details.

  •  GLN
  • Email address
  • Phone number


The following example illustrates changing the email address and phone number:



5. Tap Update. The user details are saved.


Back to the list of procedures



Changing the Credential Details


You can update the credential settings for your current ATP wallet provider, or you can change the ATP wallet provider.


Procedure


1. Open Movilitas DSCSA mobile.


2. Select the burger menu in the top-right corner of the screen. The application displays the options. 


Example:



3. Select Credential details.


The application displays the Verifiable credentials page with the current configuration.


The following example illustrates an existing credential setting for CARO:


4. Enter the credential details:

  • DID
  • API Key (XATP only).


The following example illustrates giving the credential details for XATP:



5. Tap Update.


The credential details are saved.


Next Steps


Verify a pack. For more information, see Verifying a Pack with a Verifiable Credential.


Back to the list of procedures