Skip to content
Invoices, payments and books for businesses paid in USDC

Stablecoin payments.
Connected to your books.

Zetra monitors finalized NEAR payments and connects every confirmed transfer to the records in your books.

Paid straight to your wallet Every figure links to its transaction Exports to QuickBooks and Xero
Incoming payment· 2,000 USDC
ZetraExample
  • Payment record received
  • Example checks shown
  • Matched to Acme Ltd · INV-2041
  • Example invoice marked paid
Acme Ltd
INV-2041
Amount due
$2,000.00

Example: a block explorer shows that 2,000 USDC moved. Zetra can connect a payment record to invoice INV-2041 and the books.

How it works

From a wallet address to a full set of books.

Start with the wallet you already use. Zetra reads its activity. Send invoices, or let your store send its orders, only when you want to.

01

Connect

Add a public wallet address. Zetra only watches it. It never asks for keys and can't move your money.

02

Collect

Send a payment request, connect your checkout, or keep accepting USDC at your existing address.

03

Match

Zetra uses the payment reference, known customer wallets, the amount and the timing to work out what each payment is for. Anything uncertain waits for you.

04

Book

Matched payments post to a double-entry ledger. Money nobody has claimed stays out of revenue until you say what it was.

05

Close

Review profit and loss, balance sheet and cash flow. Every figure links back to the entries and transactions behind it.

Payments and payables

Know what you earned, spent and still owe.

Finalized NEAR receipts, invoices, bills and expenses land in the same ledger, with a source behind every posted entry.

Bills and expenses

Record what the business owes and what it has spent, approve the bill, then record the account used to pay it. Zetra records the accounting event; it does not move funds.

Double-entry books

Posted entries stay on record. A mistake is fixed with a reversing entry, so the history shows what changed and who changed it.

Reports your accountant can check

Profit and loss, balance sheet and cash flow come from posted entries. Export them as CSV or in QuickBooks and Xero import layouts.

Zetra currently accounts for USD stablecoins. Stripe Checkout is supported as a processor clearing source; bank feeds and tax filing are outside the product today.

Illustrative example

A sample transfer, connected to a business record.

Example transfer data · not a live transaction

event Transfer
asset USDC
from acme.near
to merchant.near
value 2,000.00
record Example only

Example invoice record

Acme Ltd paid INV-2041Paid
$2,000.00 USDC
  • Receiving wallet checked
  • Asset checked
  • Amount checked
  • Payment window checked
  • Invoice match shown
When a payment doesn't fit

Zetra doesn't guess with your money.

A partial payment, an overpayment, a payment in the wrong token or one nobody claims goes to a review list with the evidence and your options. Whatever you decide is recorded with your name and reason.

Partial and overpayments

$1,500 of $2,000 is tracked as partially paid with $500 remaining. $2,500 is paid, with the $500 difference held as customer credit.

Unknown payments

When nobody claims a payment, Zetra lists the invoices it could belong to and why each one fits. You assign it in two clicks, with a reason.

Nothing gets overwritten

Chain evidence can't be edited. A reversal or a resolution is a new entry, so you can always see what happened and when.

Illustrative workflow

A payment record can move from detection to bookkeeping.

This diagram describes an example product flow. It is not a live transaction or a timing measurement.

  • Payment details received. A payment record can be reviewed before it is applied to an invoice.
  • Matching is reviewed. The example shows checks for the receiving wallet, asset and amount before an invoice is marked paid.
  • Chain behavior is not implied. No transaction, confirmation or timing is represented by this illustration.
Example payment workflow · not a live transaction
ReceiveA payment record is received
ReviewThe example checks payment details
MatchThe example links the payment to INV-2041
RecordExample invoice status updated; payment.matched webhook shown

Illustration only. It does not show a live transaction or settlement timing.

POST /webhooks/zetra x-zetra-event-type: payment.matched x-zetra-signature: v1=6f1c…a09e { "type": "payment.matched", "data": { "type": "PAYMENT_MATCHED", "customer": { "name": "Acme Ltd" }, "invoice": { "number": "INV-2041", "status": "paid" }, "payment": { "amount": "2000.00", "asset": "USDC", "network": "near:mainnet", "transaction_hash": "near-tx-abc…" }, "evidence": { "block_number": "108488412", "rule_version": "match-v1.1" } } }
For developers

Everything in the console is in the API.

The API is versioned, with idempotency keys, cursor pagination and consistent errors. Webhooks are signed with HMAC, retried with backoff and can be replayed.

Non-custodial

Customers pay your wallet directly. Zetra reads public addresses only and never asks for keys, seed phrases or withdrawal rights.

One ledger

Invoices, bills, expenses and reports all post to the same journal. A correction adds an entry and leaves the original in place.

A source for every record

An onchain payment keeps its transaction evidence. A bill entered by hand keeps its document, the approval and the journal entry.

Explore Zetra.

Create a workspace to explore the product. Demo payments are simulated; no live transaction is shown.