<aside> ℹ️

The FAQ here are intended for CARO users and people who have already had some exposure to CARO. If you have just discovered CARO, you might find the introductory resources on our website helpful to get started.

</aside>

CARO usage

For how long are authentication tokens valid?

You can use the same Client ID and Client Secret to communicate with CARO when acting on behalf of each of your VRS customers.

Bearer tokens have a validity of 24 h. In the absence of any further agreement with us, each client is limited to 150 tokens per 24 hour window. Please reuse each token until its expiry.

<aside> ℹ️

If the use of one client Secret:ID pair or one authentication token for all your VRS customers conflicts with your own architecture, do let us know, since we have no insights into your systems. In that case, we may need to reconsider certain design decisions at our end.

</aside>

Why can I not see the client authentication details?

The Client ID and Client Secret can be found under Developer Tools.

Only users set up as Service Provider Developers are permitted to see this information. Ask a team member with that access permission to upgrade your role in Team Management.

What kind of results does the CARO search function return?

Our search returns fuzzy results. So, if you look for a specific corrUUID or DID, make sure to check the returned result, as the search may have found something that is highly similar if there is no exact match.

VRS set-up

How do I connect a VRS customer in my system to CARO?

While we cannot provide any advice specifically for your system, a key task you need to perform is to link the customer identifiers between our two systems. Your customer's unique identifier related to CARO is their Enterprise Identifier. You can find it in the Customers ****section of your CARO Service Provider Account. You will need to map this identifier to the GLN your customer wants to use for VRS-facilitated interactions. If applicable, you may also want to connect the CARO Enterprise Identifier to another customer ID used in your system.

CARO will send you two notifications in the customer onboarding process:

  1. The connection notification tells you that your CARO Service Provider account has been connected to the Trading Partner's CARO Enterprise Account.
  2. The routing readiness notification tells you that your customer has successfully passed due diligence checks from the Credential Issuer and, thus, obtained the ATP credential that your VRS fetches for routing.

How do I need to handle the corrUUID in a VRS response?

The purpose of the corrUUID is to connect all events in a full VRS roundtrip (request and response) for a consistent audit trail. Hence, as a responder you must re-use the corrUUID that you have received from the requester instead of creating a new random corrUUID. The requester’s corrUUID can be extracted from the nonce field in the decoded received Verifiable Presentation.