Console

What the Console is, how it is organized and how you work with it.

The Console is the web interface of your payment infrastructure. It is where your teams configure the platform, follow payment activity and act on it, without writing code. Think of it as your back office: one place, organized in sections, where every object you work with (a contract, a routing rule, a webhook, a transaction) has its own table, detail page and, when you are allowed to change it, an edit mode.

What you do in the Console

GoalWhat it coversStart here
Monitor performanceCharts and KPIs on approval rates, volumes, refunds and chargebacks.Dashboards
Follow paymentsEvery checkout, order and transaction, with its status, operations and notifications.Transactions
Connect providersContracts with payment, payout, risk and network tokenization providers, and the payment methods they process.Contracts
Decide where payments goRouting rules, fallbacks and retries, SCA rules and exemptions, and the lists they use.Routing Matrix
Connect your systemsAPI keys, webhook endpoints, capture procedure and hosted page settings.API keys
Control accessWhich accounts each user can see, and what each user profile can view and change.User profiles

How the Console is organized

The left sidebar groups the modules into sections. Select a section to see its modules.

The sections and modules you see depend on your user profile. If a module is missing, your profile does not give you access to it.

How every module works

All modules follow the same pattern, so once you know one, you know them all.

flowchart LR
  A[Table] -->|Select a row| B[Detail page, read-only]
  B -->|Edit| C[Edit mode]
  C -->|Save| B
  C -->|Reset| C
PageWhat you do there
TableFind objects: Quick search by ID, Advanced Search, sorting, pagination, column configuration and cell menus such as Open in.
Detail pageReview one object safely. Nothing changes here. Use Prev and Next to move through the same result set.
Edit modeChange the object. Changes stay local until you select Save. Reset discards them.

To move around, use the left sidebar to switch modules and the breadcrumbs to go back up a level. Keyboard shortcuts cover most actions. See Console navigation and Keyboard shortcuts.

Changes are deliberate

The Console is built so that nothing changes by accident:

  • Detail pages are read-only. You enter edit mode explicitly.
  • Edits are staged. They apply only when you save, and leaving a page with unsaved changes asks for confirmation.
  • Sensitive actions, such as publishing, unpublishing or revoking a contract, webhook or API key, ask for confirmation. Some require you to type a confirmation text.
  • Actions your profile does not allow are not displayed.

The Console and the API

The Console and the API work on the same objects. What you set up in the Console decides how the platform processes the payments your integration sends:

  • API keys you create in the Console authenticate your API calls.
  • Contracts and the Routing Matrix decide which provider processes each payment.
  • Webhooks decide which events reach your systems.
  • Checkouts, orders and transactions created through the API appear in the Console, with their full history.

Related pages