LSPedia ATP Credential Integration

If your organization runs DSCSA verification through LSPedia, you can attach a LedgerDomain ATP credential to your verification traffic without changing serialization systems. LSPedia’s OneScan suite includes a Verification Router Service handling saleable returns and enhanced drug verification for manufacturers, wholesalers, and dispensers, and OneScan VRS is built to carry OCI-compliant verifiable credentials on verification transactions, so responders can confirm the requestor’s Authorized Trading Partner status automatically.

LedgerDomain is an OCI-conformant Digital Wallet provider (audited, not just self-attested), and OCI conformance is exactly what makes this work across vendors: a credential issued through XATP lives in your LedgerDomain wallet, and LSPedia’s VRS checks it when your verification requests and responses move across the network.

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 LSPedia 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. “LSPedia”).
4. Select the connection method for your provider. Once your integration is created, our team confirms the connection end to end.

The integration gives LSPedia 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 LSPedia 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