NCC-LEGAL-002 — NCC Operating Rules

1. Overview

These NCC Operating Rules (“Rules”) govern the operation of the Newport Clearing Corporation network.

NCC is the clearing, settlement, routing, and interbank infrastructure subsidiary of Alta Group N.V. NCC provides approved participating institutions with access to interbank transfer, clearing, routing, settlement, institution record, and related infrastructure services.

These Rules apply to every participating institution, applicant, authorized representative, operator, system user, and any other person or entity that accesses or uses NCC services.

By participating in NCC, the institution agrees to follow these Rules, the NCC Participation Agreement, the NCC Fee Schedule, the Alta Group Terms of Service, the Alta Group Privacy Policy, and any applicable NCC procedures or notices.

NCC may update these Rules at any time.

2. Roleplay and Virtual Economy Notice

NCC is designed for use within Minecraft, Discord, roleplay communities, virtual economies, and related online environments.

Unless NCC clearly states otherwise in writing:

• NCC is not a real-world clearing house;
• NCC is not a real-world central bank;
• NCC is not a real-world payment system operator;
• NCC does not process real-world bank transfers;
• routing numbers, settlement balances, transfers, clearing records, reserves, and fees may represent in-game, fictional, simulated, or roleplay value only;
• these Rules do not create real-world banking, payment, securities, investment, legal, or financial rights.

Participating institutions are responsible for understanding that NCC is a roleplay and virtual economy infrastructure service unless expressly stated otherwise.

3. Purpose of the Network

NCC exists to provide trusted infrastructure for approved financial institutions in the Alta ecosystem.

NCC services may include:

• interbank transfers;
• payment routing;
• clearing records;
• settlement records;
• routing number administration;
• institution profiles;
• settlement status tracking;
• transfer review;
• dispute review;
• network risk controls;
• institution restrictions;
• emergency operating procedures;
• related infrastructure services approved by NCC.

NCC is infrastructure. NCC is not a retail bank and does not directly provide ordinary deposit accounts to retail users.

4. NCC Authority

NCC has authority to operate, supervise, review, pause, restrict, correct, or terminate activity on the NCC network.

NCC may:

• approve or reject participating institutions;
• assign or revoke routing numbers;
• process or reject transfer instructions;
• clear or settle transfers;
• delay, hold, reverse, or adjust transfers;
• impose limits;
• require reserves;
• restrict institutions;
• suspend network access;
• investigate activity;
• resolve disputes;
• update records;
• protect network integrity.

NCC decisions are final unless NCC chooses to reopen or review a matter.

5. Participating Institutions

Only approved institutions may participate in NCC.

Participating institutions may include:

• banks;
• payment platforms;
• exchanges;
• settlement participants;
• financial platforms;
• other approved institutions.

Participation is a privilege, not a right.

NCC may approve, deny, restrict, suspend, or terminate participation at its discretion.

6. Institution Records

Each participating institution must maintain accurate records with NCC.

Institution records may include:

• legal or roleplay name;
• public name;
• routing number;
• institution identifier;
• authorized representatives;
• owner or controlling party;
• Discord server or contact;
• settlement account;
• approved services;
• participation status;
• risk status;
• technical access;
• support contact;
• other required information.

Institutions must promptly update NCC if information changes.

7. Routing Numbers

NCC may assign routing numbers or institution identifiers to participating institutions.

A routing number:

• remains subject to NCC control;
• may only be used for approved NCC services;
• may not be sold, transferred, leased, or assigned without NCC approval;
• may not be used to impersonate another institution;
• may be suspended, revoked, modified, or reassigned by NCC.

NCC may maintain routing number records as the official network records.

8. Authorized Representatives

Each participating institution must designate authorized representatives.

Authorized representatives may be permitted to:

• submit transfer instructions;
• receive NCC notices;
• manage institution information;
• respond to NCC inquiries;
• submit disputes;
• approve settlement matters;
• receive operational alerts;
• communicate with NCC staff.

NCC may rely on actions or instructions from authorized representatives according to NCC records.

The institution is responsible for removing representatives who no longer have authority.

9. Transfer Instructions

Participating institutions may submit transfer instructions through approved NCC systems.

A transfer instruction may include:

• sending institution;
• receiving institution;
• sender account or reference;
• recipient account or reference;
• routing number;
• amount;
• currency;
• memo;
• transaction reference;
• authorization record;
• timestamp;
• supporting information;
• any other required field.

The sending institution is responsible for ensuring each transfer instruction is accurate, authorized, complete, and compliant with NCC rules.

10. Transfer Acceptance

Submitting a transfer instruction does not guarantee acceptance, clearing, settlement, or completion.

NCC may accept, reject, delay, hold, cancel, reverse, or review a transfer instruction when necessary.

Reasons may include:

• invalid routing number;
• missing information;
• insufficient settlement capacity;
• sending institution restriction;
• receiving institution restriction;
• suspected fraud;
• duplicate transfer;
• unauthorized transfer;
• technical issue;
• system issue;
• limit violation;
• rule violation;
• platform integrity concern.

11. Clearing

Clearing is the process of validating, recording, reviewing, and preparing transfer instructions for settlement.

NCC may clear transfers automatically, manually, in batches, in real time, or through any process adopted by NCC.

Clearing may include:

• validating routing numbers;
• checking institution status;
• checking limits;
• checking required fields;
• screening for duplicate transfers;
• recording transfer details;
• placing transfers into settlement queues;
• flagging transfers for review.

A cleared transfer is not necessarily settled or final.

12. Settlement

Settlement is the process of updating balances, obligations, or records between participating institutions.

NCC may settle transfers on a:

• gross basis;
• net basis;
• batch basis;
• real-time basis;
• manual basis;
• delayed basis;
• other basis adopted by NCC.

NCC may determine settlement timing, sequence, windows, requirements, and procedures.

A transfer is final only when NCC records it as final.

13. Settlement Windows

NCC may establish settlement windows for processing transfers.

Settlement windows may be:

• continuous;
• hourly;
• daily;
• manual;
• scheduled;
• emergency-only;
• custom for certain institutions.

NCC may open, close, extend, shorten, skip, delay, or cancel settlement windows at its discretion.

Transfers submitted outside a settlement window may be queued, rejected, delayed, or handled according to NCC procedures.

14. Settlement Priority

NCC may prioritize settlement based on:

1. network safety;
2. institution restrictions;
3. transfer status;
4. available settlement capacity;
5. time of submission;
6. manual review requirements;
7. emergency controls;
8. NCC discretion when needed to protect the network.

NCC may change settlement priority when necessary.

15. Queued Transfers

NCC may place transfers into a queue before clearing or settlement.

Transfers may be queued because of:

• settlement window timing;
• insufficient settlement capacity;
• manual review;
• receiving institution status;
• sending institution status;
• technical issues;
• risk controls;
• operating limits;
• system backlog.

NCC may process, expire, cancel, reject, reorder, or hold queued transfers according to NCC procedures.

16. Failed Transfers

A transfer may fail for reasons including:

• invalid routing number;
• invalid recipient information;
• insufficient settlement capacity;
• institution suspension;
• account restriction;
• technical failure;
• duplicate transfer;
• unauthorized transfer;
• manual rejection;
• rule violation;
• network emergency.

NCC may notify one or more participating institutions when a transfer fails.

NCC is not responsible for customer issues caused by a failed transfer unless a specific written agreement states otherwise.

17. Reversals and Corrections

NCC may reverse, correct, adjust, or cancel transfers and settlement records when necessary.

Reasons may include:

• error;
• duplicate transfer;
• wrong institution;
• wrong account reference;
• wrong amount;
• unauthorized transfer;
• fraud or suspected fraud;
• technical issue;
• settlement failure;
• institution default;
• rule violation;
• platform integrity concern.

NCC records are the official records unless NCC determines that correction is required.

18. Payment Finality

A transfer or settlement is final only when NCC records it as final.

NCC may determine finality status based on network records, system status, transfer state, settlement completion, institution status, and applicable procedures.

NCC may reopen, correct, or reverse a transfer that was mistakenly marked final if necessary to correct an error, address fraud, or protect network integrity.

19. Settlement Capacity

Each participating institution must maintain sufficient settlement capacity to meet its obligations.

Settlement capacity may include:

• balances;
• reserves;
• settlement accounts;
• approved credit;
• collateral-style protections;
• other approved sources of settlement support.

NCC may determine whether an institution has sufficient settlement capacity.

20. Reserves and Holds

NCC may require institutions to maintain reserves or holds.

NCC may impose reserves or holds because of:

• new institution status;
• high transfer volume;
• settlement risk;
• prior failures;
• suspicious activity;
• technical instability;
• customer disputes;
• institution default risk;
• unpaid fees;
• manual review;
• network safety.

NCC may increase, decrease, release, apply, or extend reserves or holds at its discretion.

21. Limits

NCC may impose limits on institutions, transfers, routing activity, settlement obligations, or technical access.

Limits may include:

• per-transfer limits;
• daily limits;
• weekly limits;
• settlement window limits;
• institution exposure limits;
• route-specific limits;
• currency-specific limits;
• API limits;
• manual review thresholds.

NCC may change limits at any time.

22. Operating Hours

NCC may establish operating hours for support, transfer processing, settlement, manual reviews, dispute review, and technical operations.

NCC may operate continuously or only during defined hours.

NCC may pause operations for maintenance, emergencies, technical issues, staffing limitations, or business reasons.

23. Institution Restrictions

NCC may restrict an institution’s network access.

Restrictions may include:

• routing suspension;
• transfer limits;
• settlement holds;
• manual review requirement;
• disabled outbound transfers;
• disabled inbound transfers;
• revoked API access;
• frozen settlement activity;
• restricted representatives;
• probationary status;
• termination.

NCC may apply restrictions immediately and without prior notice when needed.

24. Institution Default

An institution may be in default if it:

• fails to meet settlement obligations;
• fails to maintain required reserves;
• submits fraudulent or unauthorized transfers;
• provides false information;
• fails to pay fees;
• fails to cooperate with NCC;
• violates the Participation Agreement;
• violates these Rules;
• creates unacceptable risk;
• becomes inactive or abandoned;
• loses required approval;
• engages in activity harmful to the network.

Upon default, NCC may take any action allowed by the Participation Agreement, these Rules, or NCC procedures.

25. Default Remedies

If an institution defaults, NCC may:

• suspend routing;
• reject transfers;
• hold pending transfers;
• apply available balances or reserves where permitted;
• require immediate settlement;
• restrict access;
• revoke routing numbers;
• notify affected institutions;
• initiate dispute procedures;
• terminate participation;
• preserve records;
• take any other action needed to protect the network.

NCC remedies are cumulative and may be used together or separately.

26. Emergency Procedures

NCC may declare an emergency if necessary to protect network integrity.

Emergencies may include:

• system outage;
• fraud incident;
• major settlement failure;
• security incident;
• database issue;
• exploit or bug;
• mass duplicate transfers;
• routing attack;
• unauthorized access;
• platform emergency;
• Discord or hosting failure;
• major participant default.

During an emergency, NCC may pause transfers, halt settlement, restrict institutions, disable APIs, extend settlement windows, reverse records, or take other protective actions.

27. Technical Access

NCC may provide technical access through websites, dashboards, bots, APIs, forms, spreadsheets, databases, Discord channels, or other tools.

Institutions must protect technical access.

Institutions may not:

• share credentials improperly;
• expose API keys;
• bypass authentication;
• scrape or overload NCC systems;
• access unauthorized data;
• reverse engineer NCC systems;
• use unauthorized bots or scripts;
• interfere with NCC infrastructure;
• compromise system security.

NCC may restrict technical access at any time.

28. Message Standards

NCC may require transfer instructions, routing messages, settlement files, API requests, or other communications to follow NCC message standards.

Message standards may include required fields, formats, identifiers, status codes, authentication methods, timestamps, references, or metadata.

NCC may reject messages that do not meet required standards.

29. Security Requirements

Participating institutions must maintain reasonable security practices.

This may include:

• protecting credentials;
• limiting staff access;
• reviewing authorized representatives;
• protecting API keys;
• monitoring suspicious activity;
• reporting compromises;
• maintaining accurate contact information;
• responding to NCC alerts.

Institutions must notify NCC promptly if they suspect unauthorized access, compromised credentials, fraudulent transfers, or system issues affecting NCC activity.

30. Disputes Between Institutions

Institutions may submit disputes to NCC through official channels.

Disputes may involve:

• incorrect transfer instructions;
• failed transfers;
• duplicate transfers;
• settlement errors;
• unauthorized transfers;
• routing mistakes;
• fees;
• institution restrictions;
• operating rule interpretation.

NCC may resolve disputes based on records, logs, transfer data, settlement records, institution submissions, screenshots, staff review, and applicable rules.

NCC’s decision is final unless NCC chooses to reopen the matter.

31. Customer Disputes

NCC generally does not directly handle customer disputes.

Participating institutions are responsible for their own customers.

NCC may become involved if a customer dispute affects:

• interbank settlement;
• routing;
• fraud;
• duplicate transfers;
• network integrity;
• another institution;
• NCC records.

32. Investigations

NCC may investigate institutions, representatives, transfers, settlement activity, routing patterns, technical access, suspicious behavior, disputes, defaults, and network incidents.

Institutions must cooperate with investigations and provide requested information.

Failure to cooperate may result in restrictions, suspension, or termination.

33. Records

NCC may maintain official records of:

• institution profiles;
• routing numbers;
• institution identifiers;
• authorized representatives;
• transfer instructions;
• clearing records;
• settlement records;
• queues;
• failures;
• reversals;
• reserves;
• holds;
• limits;
• disputes;
• investigations;
• restrictions;
• suspensions;
• terminations;
• staff actions;
• audit logs;
• technical logs.

NCC records are the official records unless NCC determines that correction is required.

34. Notices

NCC may send notices through:

• NCC dashboard;
• Discord direct message;
• Discord channel;
• email, if provided;
• support ticket;
• website alert;
• bot notification;
• official operations channel;
• other approved method.

Notices may include operational alerts, settlement updates, failed transfers, disputes, restrictions, suspensions, fee notices, rule updates, and emergency notices.

A notice is deemed received when sent through an official NCC channel unless NCC determines otherwise.

35. Fees

NCC may charge fees according to the NCC Fee Schedule or another written notice.

Fees may include:

• participation fees;
• routing fees;
• settlement fees;
• transfer fees;
• manual review fees;
• investigation fees;
• premium connectivity fees;
• technical service fees;
• custom service fees.

NCC may collect fees from balances, invoices, settlement accounts, or other approved payment methods where permitted.

36. Confidentiality

Institutions may receive non-public NCC information.

Confidential information may include:

• settlement data;
• institution data;
• routing details;
• technical documentation;
• system information;
• security procedures;
• risk controls;
• operating procedures;
• dispute information.

Institutions may not disclose confidential NCC information without approval unless required by a recognized legal, platform, or server-government process.

37. Network Integrity

All institutions must act in a manner that protects NCC network integrity.

Institutions may not use NCC services in a way that creates unreasonable risk, disrupts settlement, misleads other institutions, harms users, abuses technical systems, or damages confidence in the network.

NCC may take action whenever it believes network integrity is threatened.

38. Service Availability

NCC services may be unavailable, delayed, interrupted, restricted, changed, degraded, or discontinued at any time.

NCC does not guarantee uptime, settlement timing, transfer speed, routing availability, API availability, dashboard availability, bot availability, or uninterrupted service.

NCC may perform maintenance, emergency shutdowns, upgrades, resets, migrations, or feature changes when necessary.

39. Relationship to Other Documents

These Rules apply together with:

• NCC Participation Agreement;
• NCC Fee Schedule;
• NCC Governance Charter;
• Alta Group Terms of Service;
• Alta Group Privacy Policy;
• Alta Group Intellectual Property Policy;
• any applicable NCC procedures, notices, or technical documentation.

If there is a conflict between these Rules and a more specific written NCC procedure, the more specific procedure controls for that subject unless NCC states otherwise.

40. Changes to These Rules

NCC may update these Rules at any time.

Updated versions become effective when posted, published, or otherwise made available.

Continued participation in NCC after an update means the participating institution accepts the updated Rules.

41. Contact

Questions, disputes, or support requests should be submitted through official NCC support or operations channels.

42. Approval

These NCC Operating Rules are adopted by NCC as the governing operating rules for NCC services.