SpicePay

Control Center

A tour of the SpicePay dashboard.

The Control Center at dashboard.spicepay.net is where you configure and monitor everything. This page maps its main areas.

Overview

The landing page after sign-in: volume, approval rate, and error trends for the selected time range, plus recent transactions and open disputes. Use it as your morning health check.

Payments

  • Transactions — every payment attempt across all connectors, with full lifecycle detail: connector response codes, timeline, and raw request metadata on the detail page.
  • Refunds — full and partial refunds, filterable by status and connector.
  • Disputes — chargebacks from all processors in one queue, with evidence submission and deadline tracking.
  • Payment analytics — approval-rate breakdowns by connector, payment method, currency, region, and failure reason.

Commerce

  • Customers — unified customer records with saved payment methods and payment history.
  • Subscriptions — recurring plans, upcoming invoices, retry state, and dunning progress.
  • Shops & projects — checkout branding, enabled payment methods, and webhook configuration per storefront.

Orchestration

  • Connectors — connect, edit, and disable processors; per-connector health and credentials management.
  • Surcharges — surcharge rules by payment method, region, and amount, with a dry-run evaluator.
  • Payment method availability — which methods appear at checkout per region and currency.
  • Blocklist — block cards, emails, or IPs from checkout.
  • Fees & regions — fee schedules and regional configuration.

Administration

  • Employees & roles — invite teammates and scope them with role-based access control.
  • Login activity — audit of sign-ins, with device and location.
  • Merchant account & billing — company details, payout configuration, and your SpicePay invoice history.
  • Profile — password, TOTP two-factor authentication, and personal preferences.

Tip: everything in the Control Center is also available via the API — the dashboard is a client of the same endpoints you integrate with. See API authentication.