Counterparty Verification Terms

1. Who these terms apply to

These terms apply to any person or organisation ("Counterparty") that enters an EBRICS code and an ATV reference on the decoder, or queries the Registry's verification API. By submitting a verification you accept these terms on behalf of your organisation.

2. Authorization is required

You may verify a code only with an Authorization to Verify issued by the code holder and delivered to you by the Registry. You must not:

• attempt verification without a valid ATV, or with an ATV addressed to someone else;
• attempt to guess, generate or enumerate codes, seals or ATV references;
• use automated tools against the decoder. Institutional access is available only under the Institutional API Terms.

Every attempt is logged. Repeated failed attempts may result in blocking and referral to the relevant authorities.

3. What a successful verification tells you

A successful verification confirms that, at the moment of the query:

• the code is recorded on the Reserve Ledger and is active;
• the verified profile shown is the one sealed into the code at issuance, and the integrity check has passed;
• the holder has authorised you to view it.

The profile reflects the Registry's determinations under the Verification Standard. It is not a guarantee of performance, product availability, quality or quantity, of financing, or of creditworthiness, and it does not replace your own due diligence.

4. Unsuccessful verifications

The Registry returns the same neutral response for every failure and does not say which element failed. A failed verification may mean a typing error, an expired or used-up ATV, a suspended or revoked code, or an attempted impersonation. If in doubt, ask the counterparty to issue a new ATV, and do not proceed on the strength of documents alone.

5. Use of verified information

The verified profile is confidential. You may use it only to:

• decide whether and how to engage with the holder for the purpose stated in the ATV;
• keep a record of your due diligence, including the verification reference;
• meet your own legal and regulatory obligations.

You must not publish it, resell it, add it to a third-party database or use it for marketing. Personal data in the profile (such as the name of the authorised contact) must be handled in accordance with the data protection law that applies to you.

6. Notification to the holder

The holder is told that a verification took place, including your organisation name as stated in the ATV and the verification reference.

7. Your records

Record the verification reference (VER-…) with your due-diligence file. The Registry can confirm to a regulator or auditor that a verification with that reference took place.

8. Liability

The Disclaimer & Liability policy applies. The Registry is liable only for failing to report the Ledger accurately at the time of your query, within the limits set out there.

9. General

These terms are governed by the laws of England and Wales, and the Terms of Use apply in addition.