View Categories

OPTEL ATP Credential Integration

OPTEL and LedgerDomain have partnered directly to deliver credential-secured drug verification under DSCSA. OPTEL’s Optchain Verify connects trading partners to the Verification Router Service (VRS) network, and through the partnership, verification messages carry LedgerDomain-issued ATP credentials so responders can automatically confirm the requestor’s identity and Authorized Trading Partner status. OPTEL is an OCI-conformant VRS provider and has completed ATP Verifiable Credential integration testing through the HDA VRS Working Group.

This is the most direct path of any provider integration we support: the wallet handoff between Optchain Verify and XATP is already established, so connecting your credential is a configuration step, not an integration project.

Before You Start #

You will need an OCI-compliant ATP credential issued to your organization. If you don’t have one yet, start with Getting Your Credential. Issuance takes minutes, not weeks. You will also need your XATP dashboard login and, on the OPTEL side, an account with VRS access enabled.

Connecting Your Credential #

Integration runs through your XATP dashboard:

  1. Log into your XATP dashboard.
  2. Navigate to the VRS Integrations tab.
  3. Click Create Integration and give it a name (e.g. “OPTEL”).
  4. Select the connection method for your provider.

The integration gives OPTEL standard access to your LedgerDomain wallet for signing and checking operations, so every verification request you send carries proof of your identity and ATP status. See VRS Credential Integration for how this works under the hood, or the VRS Provider API Integration guide if you are building against our APIs directly.

Verifying It Works #

Send a test verification request through your OPTEL environment. A credentialed request returns a normal verification response; if the credential is missing or not yet linked, responders that require ATP credentials reject the request (implementations vary, but expect an Error 403 such as “ATP Authorization header is null”). If a test request fails after your integration is confirmed, contact support@ledgerdomain.com and we will trace it with you.

Last updated

Ready to do this live?

See the Address Book and DSCSA workflows on your own data.

Explore the Address BookTalk to us