Invitation & Access Policy
Registration with the EBRICS Registry is by invitation only. This policy sets out who may be invited, the strict criteria for a principal to request access, the automatic refusals, and how requests are decided.
1. Purpose
The EBRICS Registry exists to give verified principals in the fuel industry a sealed institutional identity. To protect the integrity of the Reserve Ledger, and the time of the institutions that rely on it, the Registry does not accept open applications. Registration is by invitation only.
This policy applies to everyone who seeks to engage with the Registry, and it binds the compliance desk of Eurabelt Fuels Ltd.
2. Registration by invitation
- Who issues invitations. Invitations are issued only by the EBRICS compliance desk: to institutions already in a relationship with Eurabelt Fuels Ltd, and to principals whose request for access has been approved under section 4.
- What an invitation is. An invitation is an invitation to *apply*. It is not an EBRICS code, an endorsement, or a statement about the invitee's standing. A code is issued only after full verification under the Verification Standard.
- Personal and single-use. An invitation is addressed to one corporate mailbox (or, where the Registry so decides, to one corporate domain). It may be used for one application, expires on the date stated (normally 14 days) and cannot be transferred, sold or shared.
- Mailbox proof. On the Invited Institutions page, the invitee enters the invited email address. A single-use link, valid for 60 minutes, is sent only to an invited mailbox, and only that link opens the application form. The registered email of the application is the mailbox that opened it.
- Neutral response. The Invited Institutions page gives the same answer for every address entered. The Registry never confirms or denies whether an organisation has been invited.
3. Warning to uninvited parties
If you do not hold an official invitation from the EBRICS Registry, you cannot engage with the Registry through the Invited Institutions page. Attempts to do so are recorded. Unsolicited applications, documents, offers and correspondence are not reviewed and are not acknowledged.
Principals that meet every criterion in section 4 may request access. No other route exists.
4. Requests for access — principals only
A request for access may be made only by a company that meets every one of the following criteria:
- it acts as a principal buyer or principal seller for its own account;
- it belongs to one of the four principal categories in the table below;
- it provides its registered company name, company registration number, country of incorporation and official website; and
- it makes the request from a corporate mailbox at the domain of that official website, through a named officer stating their position.
| Principal category | Assessed against |
|---|---|
| National oil company or state entity | T1 — Sovereign |
| International oil company, refinery or major trading house | T2 — Prime Institutional |
| Principal with an established operating history (3 years or more) | T3 — Principal |
| Principal with a shorter operating history (under 3 years) | T4 — Registered Principal |
The category selected indicates the tier against which the company will be assessed. The tier itself is assigned only by the compliance desk after verification and is never self-declared.
5. Who may not request access
The following may not request access, invitation or registration, whether acting alone or on behalf of another party:
- brokers, intermediaries and introducers;
- mandate holders and agents, including those holding a mandate from a principal;
- consultants, advisers and representatives acting for a third party;
- any party that is not itself the buyer or the seller in the transaction.
A principal that wishes to engage the Registry must do so itself, through its own officers and its own corporate mailbox.
6. Automatic refusals
The Registry's systems refuse a request automatically, before any review, where:
- the email address is a personal or webmail address (such as Gmail, Outlook, Yahoo, iCloud or Proton);
- the email domain does not match the domain of the official website given;
- the email domain does not receive mail, or the website domain does not exist;
- a request from the same organisation is already under consideration;
- a request from the same organisation was declined in the previous 12 months;
- any required field or declaration is missing; or
- the request is not confirmed from the corporate mailbox within 24 hours.
7. Review and decision
- Mailbox confirmation. A request is lodged only when the requester confirms it through the link sent to the corporate mailbox.
- Register check. The compliance desk confirms the company, its registration number and its status against the official company register of the country of incorporation, and may screen the company under the Sanctions Policy.
- Decision. The compliance desk approves or declines the request. On approval, a formal invitation is sent to the confirmed mailbox and the company proceeds as an invited institution. On decline, the requester is notified; the Registry does not disclose reasons.
- No guarantee. Meeting the criteria in section 4 makes a request eligible for review. It does not guarantee an invitation, and an invitation does not guarantee the issue of a code.
- Twelve-month bar. An organisation whose request is declined may not request access again for 12 months.
8. False declarations
Every request and application includes declarations that the company acts as a principal for its own account, is not an intermediary, and that the information is true. A false or misleading declaration results in permanent refusal of the organisation and of the individuals involved, the revocation of any invitation or code, and may be reported to the relevant authorities under the Fraud & Impersonation Warning.
9. No fees
The Registry never charges for a request for access or for an invitation, and never asks for payment, codes, passwords or confirmation links by telephone, messaging app or email reply. Any such demand is fraudulent and should be reported to compliance@eurabeltfuels.com.
10. Personal data
Requests contain business contact details of the requester. They are processed to decide the request, to prevent duplicate and abusive requests, and to keep the audit record, as described in the Privacy Notice. Requests that are not confirmed are deleted after 90 days. Decided requests are kept for 24 months to apply the twelve-month bar, then deleted, as set out in the Data Retention Schedule.
11. Contact and complaints
Questions about this policy may be sent to compliance@eurabeltfuels.com. Complaints about the handling of a request are dealt with under the Complaints & Appeals procedure. A complaint does not reopen a request within the twelve-month bar unless the compliance desk decides otherwise.