Skip to content

Step-by-step guide to signing in, configuring your project, and using the main sections of the personal account. For API integration, see Documentation.

What you need


Initial setup

Sign in to the personal account

After receiving your credentials, open the sign-in page and enter your login and password:

1Payment personal account sign-in page

Project API key

  1. Go to Projects.
  2. Open project editing (pencil icon).
  3. Set the project API key if each site or project uses a separate key.

Projects section in the personal account

API key configuration in the project card

If the API key is not set for a project, the global key from Settings → API settings is used:

Global API key in account settings

The key is required to sign API requests — see API request format.

Callbacks (notify_url)

Set notify_url in project settings to receive transaction status notifications:

notify_url field in project settings

1Payment sends POST callbacks with payment data. Your server must respond with HTTP 200 OK. Format and signature verification — in API request format.

SUCCESS and FAIL URLs (payment form)

When integrating via the payment form, you can set URLs to redirect the payer after successful or failed payment:

SUCCESS and FAIL URLs in project settings

Payment form and GATE (host2host)

  • Payment form — redirect the user to the 1Payment page (example: init_form).
  • GATE (host2host) — charge without redirect; PCI DSS certificate is required. Contact your account manager and see API documentation.

Payment and payout fees

The Payment fees and Payout fees tabs show enabled methods, per-transaction fee, minimum and maximum amounts, and settlement times:

Payment acceptance fees

Payout fees


Dashboard

Summary transaction statistics for a period: Today, Week, Last week, Month, Last month, or a custom range (Select period).

Dashboard — chart and filters

The site header shows two balance figures:

  • blue — total payout balance (funds available for withdrawal right now);
  • gray — total expected balance (payments accepted during the current day that have not yet been credited to the payout balance).

Funds for the previous day are credited to the payout balance at 11:00 (MSK) on the current day.

Balance in the personal account header


Statistics

Search payments by phone, account, transaction number (order_id or user_data). Export to CSV, filter by project and payment method:

Statistics section

For a selected transaction you can:

  • request a refund (full or partial, with amount);
  • view refund attempt history.

Transaction refund dialog

Refund attempt history

Refunds via API are described in refund documentation.


Payouts

Payout statistics for a period, transaction search, status filter, CSV export by initiation time or status time:

Payouts section

Initiate payouts via API — in the Payouts documentation section.


Disputes

List of chargeback cases. Respond by attaching documents: Files → Send.

Disputes list

Attach files to a dispute


Reporting

Project currency, balance credit history (by default funds are available for payout the next day), holds (chargeback reserves):

Reporting — balance and credits

Holds in reporting

Configure automatic payment registry email delivery:

Automatic registry email delivery


Staff

Add staff members with access to sections: statistics, projects, payouts, disputes, reporting, refund access.

Staff sign-in: https://clientpanel.1payment.com

Add staff member

Staff access permissions


Wallets

Before adding a payout wallet (USDT or card), enable 2FA in Settings → Security:

Enable 2FA before adding a wallet

Available payout methods depend on enabled channels — confirm with your 1Payment account manager.

FieldDescription
CredentialPayment details (required).
DescriptionOptional label for the saved wallet.

Add payout wallet


Settings

Profile

Contact details: name, phone, Skype, Telegram.

Profile tab

Security and 2FA

Change password, enable and disable two-factor authentication (2FA).

Four modes are available:

  1. No 2FA.
  2. 2FA via email.
  3. 2FA via QR code (authenticator app).
  4. 2FA via both email and QR code.

The QR code is shown when enabling the corresponding option. For staff, the QR is shown at sign-in if the partner enabled this option for them.

At sign-in, a session identifier (4 digits) is displayed so you enter the code for the correct session. A session lasts 60 seconds; resending the email is possible after the timer on the code entry page expires.

Security tab

API settings

Global API KEY for all projects (if no project-level key is set):

API settings tab

Activity

Sign-in log: time, IP, browser.

Activity tab

IP allowlist

Add IPs from which API requests are allowed. After adding at least one address, requests from other IPs are rejected:

Partner IP allowlist

Our IP addresses

IPs from which 1Payment sends callbacks. Add them to your allowlist (for example, when using Cloudflare):

1Payment callback IP addresses


Support

Was this article helpful?