Transactions

Audit every credit movement in your organization, page through the history, and report issues on individual entries.

The Transactions tab on the Billing page logs every credit movement in the organization: purchases, transfers in and out, member-to-member transfers, seat-assignment credits, refunds, and deductions.

Open the transactions table

1. Switch to your organization

   Open the workspace switcher in the top-left of the dashboard and select your organization.

2. Open Billing

   Click Billing in the sidebar.
3. Open the Transactions tab

   The third tab on the Billing page.

What the table shows

Four columns: Date, Type, Description, and Amount.

The header shows the total transaction count next to the title (e.g. “1,247 transactions”). 20 rows are displayed per page; use the pagination controls at the bottom to move through them.

The org transactions tab is a paginated audit log. There aren’t filter dropdowns or a date-range picker here today. To narrow by user or transaction type, page through or use the wallet’s Payment History for finer filtering of your qBraid Default workspace view.

See more detail

1. Click a row

   A side panel opens with the full transaction details.

You’ll see:

• The exact date and time.
• The full description.
• Amount and the running balance after the transaction.
• A View Receipt link if it’s a Stripe purchase.
• A Report Issue button to flag the transaction with our team.

Refresh

Click Refresh in the top-right to re-fetch the latest transactions without reloading the page.

Report a problem with a transaction

1. Switch to your organization

   Open the workspace switcher and select your organization.

2. Open Billing

   Click Billing in the sidebar.
3. Open the Transactions tab

   The third tab on the Billing page.

4. Find the transaction

   Page through the table to locate it.
5. Open the row

   Click the row to open the detail panel.
6. Click Report Issue

   A pre-filled dialog opens with the transaction ID, type, amount, and date already attached.

7. Add a description

   Explain what looks wrong.
8. Submit

   Our team reviews and follows up.

For a CSV export of credit movements, run the Payment History export from the wallet of the org’s owner or admin (which uses the org context when you’re switched into it).