View Categories

SAP ATP Credential Integration

SAP delivers DSCSA verification through the SAP Information Collaboration Hub for Life Sciences (ICH), which includes a Verification Router Service connecting pharmaceutical trading partners on SAP’s network. SAP has completed ATP Verifiable Credential integration testing through the HDA VRS Working Group, and verifiable credentials are designed to plug into existing ICH VRS workflows as an additional authentication layer.

For companies running serialization on SAP ATTP with verification through ICH, an ATP credential adds per-request proof of Authorized Trading Partner status without changing your SAP landscape. Your credential is held in your LedgerDomain wallet, and the VRS accesses it for signing and checking operations when requests 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 SAP 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. “SAP”).
  4. Select the connection method for your provider.

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