Subscription payment creation (recurring)

Recurring SBP payments let you automatically charge a customer's bank account without their repeated involvement. The account is identified by a token issued during the initial binding.

Contact your 1Payment account manager to enable this feature for your project.

The SBP subscription flow consists of four steps:

1. Account binding (first request) — you complete a successful payment with an amount greater than 0 and subscribe=1 via the payment form or GATE. The payer confirms binding in the bank app.
2. Receiving the token — after bank confirmation, 1Payment sends a callback with a unique token. Store it for subsequent charges.
3. Automatic charge (recurring) — for repeat payments, your server calls GATE (init_payment) with the stored token. The charge completes without payer involvement.
4. Notification — after each charge attempt, a callback arrives with the final transaction result.

Response format: JSON. For SBP, specify payment_type=sbp in requests.

To register a subscription, complete a successful payment with an amount greater than 0 and subscribe=1. See Form payment creation and Host-to-host payment creation (GATE) for form and GATE parameters. Below is the required set for binding.

Signature for form registration — prefix init_form. Via GATE — prefix init_payment.

MD5(init_form + <параметры_без_sign_в_алфавитном_порядке_через_&> + <API_KEY>)

MD5(init_payment + <параметры_без_sign_в_алфавитном_порядке_через_&> + <API_KEY>)

To charge automatically, send a GATE request with the stored token. With an active subscription, customer involvement is not required.

MD5(init_payment + <параметры_без_sign_в_алфавитном_порядке_через_&> + <API_KEY>)

const crypto = require('crypto');
const axios = require('axios');

// 1. Инициация подписки (первичная привязка)
async function setupSbpSubscription(apiKey, params) {
  const sortedKeys = Object.keys(params).sort();
  const queryString = sortedKeys.map((k) => `${k}=${params[k]}`).join('&');

  const baseString = `init_form${queryString}${apiKey}`;
  params.sign = crypto.createHash('md5').update(baseString).digest('hex');

  const response = await axios.post('https://api.1payment.com/init_form', params);
  return response.data; // ссылка для подтверждения в приложении банка
}

// 2. Рекуррентное списание (по токену)
async function chargeSbpByToken(apiKey, params) {
  const sortedKeys = Object.keys(params).sort();
  const queryString = sortedKeys.map((k) => `${k}=${params[k]}`).join('&');

  const baseString = `init_payment${queryString}${apiKey}`;
  params.sign = crypto.createHash('md5').update(baseString).digest('hex');

  const response = await axios.post('https://api.1payment.com/init_payment', params);
  return response.data;
}

const secretKey = process.env.ONEPAYMENT_API_KEY;

// Пример: привязка
const setupData = {
  partner_id: 1234,
  project_id: 5678,
  amount: '50.00',
  subscribe: 1,
  payment_type: 'sbp',
  user_data: 'sbp_setup_777',
  shop_url: 'http://myshop.ru',
};
// setupSbpSubscription(secretKey, setupData).then(console.log);

// Пример: списание
const recurringData = {
  partner_id: 1234,
  payment_type: 'sbp',
  project_id: 5678,
  token: 'sbp_t_1a2b3c',
  amount: '500.00',
  user_data: 'sbp_order_888',
  shop_url: 'http://myshop.ru',
};
chargeSbpByToken(secretKey, recurringData).then(console.log);

On a successful recurring request (200):

{
  "order_id": "8p3brmb19gfg0sg8gcwhws8kgc748s87",
  "status": 2,
  "status_description": "PENDING"
}

For form registration, the response includes url (see Form payment creation); via GATE — redirect_url (see Host-to-host payment creation (GATE)).

Request error (400):

{
  "error_code": 2
}

On successful binding or charge, the system sends a POST request in JSON format to your notify_url.

Important: your server must return HTTP 200 OK. Otherwise the system retries the callback once per minute for 10 minutes.

Callback signature verification: MD5 of parameters in alphabetical order joined by & + API_KEY (without the init_payment prefix). See API request format.

• Form payment creation
• Host-to-host payment creation (GATE)
• Payment status
• Payment refunds
• Transaction statuses
• Error codes (API)
• Decline error codes