TraceLink ATP Credential Integration

If your organization runs DSCSA verification through TraceLink, you can attach a LedgerDomain ATP credential to your verification traffic without changing serialization systems. TraceLink operates one of the most widely used Verification Router Service (VRS) networks in the U.S. pharmaceutical supply chain, with verification delivered through its Product Information Manager application, and supports both requestor and responder roles. TraceLink is an OCI-conformant VRS provider and has completed ATP Verifiable Credential integration testing coordinated by the HDA VRS Working Group.

LedgerDomain is an OCI-conformant Digital Wallet provider. That means a credential issued through XATP is designed to interoperate with TraceLink’s VRS out of the box: your credential lives in your LedgerDomain wallet, and TraceLink’s network checks it when your verification requests and responses move across the VRS.

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 TraceLink 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. “TraceLink”).
4. Select the connection method for your provider. During the industry stabilization period we coordinate the wallet handoff with TraceLink directly — once your integration is created, our team confirms the connection end to end.

The integration gives TraceLink 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 TraceLink 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 July 6, 2026