StrimzStrimz
Dashboard

Payment sessions page

One-time payment links, created from the dashboard or the API.

A payment session is a one-time checkout: a customer pays you a fixed amount, once. Recurring charges live under Subscriptions instead.

The Payment sessions page lists every session in this mode, most recent first, whether you created it here, from the API, from an invoice or from a storefront product.

The layout

At the top:

  • Cards: total sessions, confirmed, in flight, and the conversion rate.
  • New session: creates a payment link from the dashboard.
  • Export CSV: downloads the loaded rows, with amounts in base units (6 decimals).

Below, a table with one row per session. Filter it by status. The session ID opens the session's page.

Creating a session

Click New session and fill in:

  • Amount (required): at least 1.00.
  • Currency (required): USDC or EURC.
  • Description (optional): what the customer is paying for, up to 500 characters.
  • Customer email (optional).
  • Expires in (optional): 1 to 1440 minutes; 30 if left empty.
  • Success URL and Cancel URL (optional): where the checkout sends the customer afterwards. They must start with http:// or https://.

The dialog then shows the checkout link with a Copy button. Send it by email or chat, or open the session.

A session's page

Each session shows:

  • Amount: the amount, the Strimz fee and the net amount.
  • Payer: the payer wallet and email once paid.
  • Link: the payment link with a copy button, and when it expires.
  • Payment: the on-chain transaction with an Arcscan link, and its transaction, which opens the transaction's page.

Actions:

  • Cancel, while the session is created or awaiting_payment. The link stops accepting the payment.
  • Refund, once the payment is confirmed. It opens the refund dialog for that transaction. See Refunds.

Statuses

  • created and awaiting payment: the link is open and nothing is paid yet.
  • submitted: the payment was sent and Strimz is waiting to see it on-chain.
  • confirmed: the payment confirmed. The payment.completed webhook fires, and the payer gets a receipt if they left an email.
  • failed: the payment did not go through.
  • expired: nothing was paid before the expiry. Create a new session to collect it.
  • cancelled: you cancelled the session.

Common workflows

A customer says they paid but the session is not confirmed. Open the session. If it shows a payer and an on-chain transaction, it is moments from confirming. If not, the payment has not reached the chain yet.

Reconciling with your books. Use Transactions for what actually settled, or Export CSV here with the confirmed filter.

On this page