AI PadelAPI documentation Back to site

1C (Russian accounting system) — payment import

For clubs that keep their books in 1C:Enterprise, the most common accounting system in Russia. Payments taken at the club and posted in 1C reach the player's wallet in the AISOLUS Padel app. 1C pushes payments to the cloud on a schedule — the 1C database does not need to be exposed.

How it works

  1. 1C sends a batch of new payments: POST /v1/integrations/1c/payments with the X-1C-Token header.
  2. The cloud finds the player by phone. Found — the amount is credited to the wallet (applied). No player with this phone yet — the payment is stored as unmatched and credited after the player signs up, on POST /v1/integrations/1c/payments/retry. Phone not recognized — rejected.
  3. For reconciliation 1C reads what the cloud has received: GET /v1/integrations/1c/payments. Connectivity and token check: GET /v1/integrations/1c/ping.

Every payment from 1C is credited to the wallet as a top-up. The kind field (topup, membership, booking, other) is kept for reconciliation only.

Sending payments

curl -X POST "https://your-server/api/v1/integrations/1c/payments" \
  -H "X-1C-Token: <1C token>" \
  -H "Content-Type: application/json" \
  -d '{"payments": [
        {"ext_id": "00-000123", "phone": "+79000000001", "amount": 3500,
         "paid_at": "2026-10-02T10:15:00+03:00", "purpose": "Court booking", "kind": "booking"}]}'
# → {"ok": true, "applied": 1, "unmatched": 0, "duplicate": 0, "rejected": 0, "items": [ … ]}

The 1C token is issued by your platform administrator.