Payments

Payments

Purpose

This page tracks payment events so teams can confirm settlement, investigate failures, and maintain accurate billing records.

Prerequisites

  • Payment providers should be configured and connected.
  • Orders/subscriptions should be generating billable events.
  • Users need permissions to access transaction details.

Main Actions

  • Review transaction outcomes.
  • Filter by status, provider, date, or customer.
  • Investigate failed or disputed payments.
  • Confirm successful settlement and retries.

Field/Status Reference

  • Transaction ID: Unique payment reference.
  • Provider: Payment processor handling the charge.
  • Payment Status: Succeeded, failed, pending, refunded, etc.
  • Amount/Currency: Monetary value and denomination.
  • Processed At: Timestamp for ledger and reconciliation timelines.

Workflow

  1. Open payment records for the target period.
  2. Filter to failed/pending items first.
  3. Review failure reason and related order/subscription.
  4. Confirm retry, correction, or resolution path.
  5. Recheck status and record closure notes.

Connections

  • Settles billing records referenced in Orders.
  • Drives renewal outcomes for Subscriptions.
  • Supports finance close, reconciliation, and exception reporting.

Common Mistakes

  • Assuming pending means failed.
  • Ignoring provider-specific failure codes.
  • Closing investigation without confirming final settlement state.

Troubleshooting

  • If payment status is missing, verify provider callback/webhook flow.
  • If amounts mismatch, check discounts, taxes, and currency handling.
  • If repeated failures occur, validate payment method and retry settings.

Quick Tips

  • Work failed and pending queues daily.
  • Group issues by provider to spot systemic problems.
  • Track common failure reasons to improve customer recovery flows.