Getting started

Private settlement on NEAR

Money Station is a development protocol for business-to-business payments and business-to-worker or contractor transfers on NEAR. Independent vaults hold principal. Shared zero-knowledge notes authorize a direct payout from one verified funded vault, with recipient-signed invoices and selected evidence for reconciliation.

The current implementation supports native NEAR shared groups and token-bound USDC/NEP-141 groups. The browser executes configured testnet FT plans. Private notes creates encrypted notes and deposit plans; invoice checkout connects an original-group note to local proof generation, fee review, wallet approval and finalized confirmation. Local proofs remains available for standalone proofs and proof-file verification. Native/private-transfer proving remains in the settlement CLI.

Before you start

• Obtain a deployment policy independently from your group operator. Check its network, registry, token, denomination, fee recipient, and contract/verifier hashes.
• Use a compatible wallet and fund the accounts required by your independently reviewed deployment. A native NEAR reference group is published under Contract addresses; browser checkout still needs a separately configured FT group and its services.
• Run the matching read-only Settlement API and finalized index. Keep wallet keys, private notes, passwords, and business documents outside API requests.
• Keep encrypted private-note backups and a separate encrypted browser-operation backup. The journal is not a backup of spendable notes.

Choose a workspace

The website and these guides default to English; repository READMEs also support Korean and Simplified Chinese. The Sites preview is owner-private, including checkout links. Self-hosted access follows the host configuration. External customers need suitable access and an independently configured funded deployment.

Run local verification

Check out Core and Contract as siblings. Use Node.js 22.16 or later and the pinned Rust/C/C++ tooling for contract builds.

The November 14, 2026 Core validation passed 595 tests; the latest contract review passed 63 unit cases. Native NEAR public-testnet settlement has separate recorded evidence. Browser tests and local TESTUSD sandbox runs do not establish public USDC, a live backend or production readiness.

git clone https://github.com/Company-privacy-settlement/Contract.git
git clone https://github.com/Company-privacy-settlement/Core.git
cd Core
npm ci
npm run check
npm test

# Build the sibling contracts for the local-chain demo.
(cd ../Contract && npm ci)
npm run contract:build
npm run zk:setup
(cd ../Contract && npm run build:test-ft)
npm run demo:ft

Your first settlement

1. Obtain a group policy independently of the API; verify network, registry, token, denomination, treasury and code/verifier hashes. Inspect approved capacity and recipient readiness.
2. Create an FT note locally in Private notes. Download its encrypted backup and reopen it before preparing a public deposit plan.
3. Import the deposit plan in Settlements with the same policy and an encrypted journal. Review each prerequisite/payment call, then verify its bound Active record.
4. In invoice checkout, select a unit and open its original-group encrypted note. Import trusted proving files and an independently obtained manifest hash, then generate the local proof with its signed recipient and reference derived automatically. Local proofs and the CLI remain alternatives.
5. Import the public withdrawal plan and review each wallet call. A wallet response or timeout does not establish failure or completion.
6. Confirm the bound withdrawal Complete state and indexed invoice totals/coverage. Keep separate backups and disclose only the evidence you intend to share.

Where the code lives