Transactions page

Transactions are what actually happened on-chain. A payment session, an invoice, a storefront purchase or a subscription charge becomes a transaction once its payment confirms. Refunds appear here too.

The layout

The table lists transactions in this mode, most recent first. Columns:

• ID: opens the transaction's page
• Kind: Payment, Subscription charge, Invoice payment, Storefront purchase or Refund
• Amount and Net: in the transaction's own currency. Net is what reached your payout address after the Strimz fee.
• Payer: the wallet that paid
• Status: confirmed, pending or failed
• When: the block time

Filter by kind, status and date above the table. For dates, pick Last 7 days, This month or Last month, or choose Custom and set a first and last day. Both days are included, and days follow your computer's time zone.

Export CSV downloads the rows you've loaded, with amounts in base units (6 decimals). When a date range is set, the file is named after it, for example transactions-2026-09-01-to-2026-09-30.csv.

A transaction's page

Each transaction shows:

• Amounts: the amount, the Strimz fee and the net amount;
• Wallets: the payer and the payout address it went to;
• Chain: the block, plus a link to the transaction on Arcscan;
• Links: the payment session, subscription, customer or refund it belongs to.

Confirmed payments have a Refund button. It opens the refund dialog with this transaction already filled in. See Refunds.

From the API

GET /v1/transactions takes the same filters, plus sessionId and subscriptionId to list the transactions of one payment session or one subscription.

To list a period, pass from and to as ISO-8601 timestamps with a time zone. from is included and to is not, so one month is:

await strimz.transactions.list({ from: '2026-10-01T00:00:00Z', to: '2026-11-01T00:00:00Z' })

The range applies to when the payment settled on Arc. See the endpoint list.