Accounts and Wallets

Accounts and wallets model who pays and what balance is available. They are project-scoped resources: Portal only shows the accounts, wallets, ledgers, voucher grants, and routes that belong to the current project URL.

/projects/:projectId

Account

An account is the billable entity inside one project. It usually represents a customer, organization, team, workspace, or subscription owner.

Create an account when you need:

• customer-level balance or credit limit;
• organization-level spend tracking;
• subject routing from many users to one payer;
• wallet operations such as top-ups, voucher grants, or credit limit changes.

In the Portal, open Accounts and select Create account.

Common fields:

• Name: a human-readable label.
• Primary subject type: for example organization, workspace, or customer.
• Primary subject ID: your application-side ID for that entity.

The primary subject is descriptive account identity. It does not replace subject routing for usage producers. The same primary subject can exist in another project and point to a different account.

Wallet

A wallet belongs to an account, project, and currency. It stores balance, available balance, credit limit, and related realtime balance state.

One account can have multiple wallets, usually one per currency:

Account acct_org_001
  Wallet USD
  Wallet CNY

Create a wallet from an account’s Wallets tab.

Common fields:

• Currency: for example USD.
• Balance: starting cash balance.
• Credit limit: allowed negative spend or postpaid credit.

Account and wallet relationship

The account answers who pays.

The wallet answers which currency balance pays.

Usage debit chooses a wallet by project, account, and currency. For example, if user/u_01 routes to acct_org_001 in proj_gateway and an event rates to USD, Meterry debits the USD wallet for acct_org_001 in that same project.

Wallet operations

From the wallet row actions you can:

• set credit limit;
• top up the wallet;
• inspect realtime balance state.

Voucher grants are fund buckets attached to an account, project, and currency. They are consumed before cash balance when active.

Recommended setup

For a SaaS organization:

1. Open the project that should own the billing state.
2. Create one account for the organization in that project.
3. Create one wallet per billing currency.
4. Bind each user, workspace, API key, or agent subject to the organization account.
5. Add usage controls when each subject needs its own monthly, weekly, or daily limit.