Help Center/Admin Operations/Create, rename, enable and disable a payment processor
Admin Operations•Last updated: 2026-10-20•4 min read

Create, rename, enable and disable a payment processor

A processor (gateway) moves the money. The page shows readiness, why a processor is not ready, whether credentials are configured (yes or no, never their values) and the latest health check.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the page

Open "Finance & Payments" then "Payment Processors" (/admin/payments/processors).

2

Read a row

Code, Name, Type, Crypto Architecture, State, Ready, Why Not Ready, Credentials Configured (yes/no), Credential Purposes (names only) and Latest Health.

3

Create

Click "New Record" (super admin). Enter "Code", "Name", choose the "Type" (Manual, Automatic or Crypto), the "Crypto architecture" for Crypto, and tick "Enabled" if wanted. The processor starts with no settings or credentials.

4

Enable or disable

Use the row buttons "Enable" or "Disable", or the pencil to rename it. Enabling is only a flag: members see the processor once its readiness checks also pass.

5

Store credentials and settings

Credentials and proof settings are stored in the Payments Console credential vault, never on this page.

Expected Operational Outcome

The processor row changes in the database; "Ready" tells you whether members can actually use it.

Troubleshooting & Failure Modes

Symptom: "A processor with the code ... already exists."
Likely Cause: Codes are unique.
Resolution: Pick another code or edit the existing row.

Was this guide helpful?

Help us refine our platform documentation