Operations

Payment Charges

Track standalone payment charges, checkout URLs, statuses, gateway data, manual review, and custom invoices.

Charges are standalone payment records. They are useful when you need to request a payment that is not tied to a normal storefront product flow, such as a custom invoice, service fee, balance collection, or manual deal.

Open Charges to view them.


What a charge includes

A charge can store:

  1. Customer email.
  2. Reference text.
  3. Status.
  4. Checkout URL.
  5. Payment method and gateway data.
  6. Currency and totals.
  7. VAT and fee data.
  8. Description, deliverable data, metadata, webhook, return URL, and cancel URL.

Use the reference field to make charges easy to recognize later.


Charge statuses

The Charges dashboard shows status, customer, revenue, and payment method. You can search by charge ID.

For custom payments, customer confirmation or proof submission changes Pending to Review. Open the charge to inspect the payment method and privately stored proof. Confirm receipt independently before marking it completed; a customer confirmation or redirect return does not verify receipt. Authorized staff can complete or void a reviewed custom payment. Reviewed custom charges can be approved at any amount.

Ordinary pending or voided charges retain the existing manual-completion controls. Wallet top-ups have stricter rules: only an initialized custom payment can be approved manually, from Pending or Review. Voided custom top-ups cannot be revived.


Charge analytics

The top of the Charges dashboard summarizes revenue and completed charge count for the selected date range. Choose Revenue or Orders to switch the chart.

Each metric includes the previous period for comparison and shows whether the result increased or decreased. Available date presets include today, the last 7 days, last month, last quarter, last year, this month, all time, and a custom range.

Charge analytics only include standalone charges. Product purchases remain in the main order and dashboard analytics.


When to use charges

Use charges when the customer should pay a specific amount without browsing a public product page. They can help with manual payment flows, custom work, one-off services, or payment links that should not become reusable storefront products.

Use products when the offer should be discoverable, reusable, and part of the normal storefront catalog.

Custom payment methods

Charges support the instruction and redirect methods configured in your store's payment settings. Product assignments do not limit their availability on charges. A charge keeps its allowed methods from creation; checkout rechecks that an uninitialized method is still enabled and usable. Once initialized, its saved instructions, redirect settings, and proof requirements remain available even if the method is edited or deleted.

In templates, {id}, {invoice_id}, and {charge_id} all identify the charge. {product_name} uses its description, then reference, then Charge #ID; {quantity} is 1. Prices and email come from the charge. {return_url} opens its signed checkout or processing page according to your redirect settings.

Custom-method discounts and fees apply to ordinary charges. Wallet top-ups use the exact deposit amount instead.

On this page