1С/BAS ↔ WayForPay integration

Orders from 1С/BAS are paid through WayForPay, and holds, refunds and subscriptions are managed from the same documents

The order and the return are recorded in 1С/BAS, while payments, holds and refunds are handled in the WayForPay merchant dashboard by hand. We connect the two so an order in 1С/BAS opens a WayForPay payment, a held payment is charged or released from 1С/BAS, a return in 1С/BAS starts a full or partial refund, and a change to a subscription is made once instead of in two places.

Request an integration System page: 1С/BAS →System page: WayForPay →

What moves between the systems

1С/BAS → WayForPayAn order posted in 1С/BAS opens a WayForPay payment: a secure payment page, a form over your own site or a QR code the customer scans in a mobile app.
WayForPay → 1С/BASThe result of the payment is written into the same 1С/BAS document, so the warehouse sees which orders are paid without asking the accountant.
1С/BAS → WayForPayFor orders that need confirmation, the money is only held on the card; shipping in 1С/BAS charges it, and cancelling the order releases it.
1С/BAS → WayForPayA return registered in 1С/BAS starts a full or partial refund in WayForPay for exactly the returned part of the order.
1С/BAS → WayForPayA change to a subscription in 1С/BAS, such as a new amount, date or frequency, updates the existing WayForPay subscription instead of creating a new one.

What we connect

We look at your 1С/BAS configuration and which documents start a payment, confirm a shipment and register a return.
You give us the merchant details and secret key from WayForPay; we start with test merchant details, so no real money moves during setup.
We agree which orders are charged at once and which only hold the money, and set a reminder well before the hold window runs out.
We set up sending payments, charges, releases and refunds from 1С/BAS; every request is signed with your secret key, and each result is written back into the document.
We decide how the fiscal receipt is issued: WayForPay reaches the Checkbox cash register through an intermediate module, not directly, so we agree which side prints it.
We run test payments, holds, refunds and a subscription change end to end, then switch to live details and stay on call for the first working days.

Automation scenarios

A forgotten hold

Before the money is held, the order ships, but nobody finishes the charge in the dashboard until the hold window is almost over.

After shipping in 1С/BAS charges the held money, and an unfinished hold is flagged in time.

Refunds made twice by hand

Before the return is registered in 1С/BAS, then the manager opens the WayForPay dashboard and refunds the money separately, sometimes for the wrong part of the order.

After the return in 1С/BAS starts the refund for exactly the returned items.

Subscriptions that drift apart

Before a customer changes the plan date, 1С/BAS is updated, but the WayForPay subscription keeps charging on the old schedule.

After the change in 1С/BAS updates the same subscription in WayForPay.

Paid orders wait for a manual mark

Before the accountant checks the WayForPay dashboard and marks paid orders in 1С/BAS once or twice a day, and the warehouse waits.

After the payment result is written into the 1С/BAS document, and the warehouse starts packing right away.

How it works technically

For those who want to check: each point links to the official documentation page it comes from.

The official BAS support portal documents its integration technologies under the title «Технології інтеграції 1С:Підприємства 8.3» — BAS is built on the 1C:Enterprise 8.3 platform.
Source: its.bas-soft.eu ↗ checked 2026-09-25
According to the same documentation, the platform automatically builds a REST interface using the OData protocol, through which outside systems can read, change, create and delete data over HTTP.
Source: its.bas-soft.eu ↗ checked 2026-09-25
The Purchase method (accepting a payment on a secure WayForPay page) supports transaction types AUTO/AUTH/SALE through the merchantTransactionType parameter; AUTH is used for two-stage payment (funds held first, charged later).
Source: wiki.wayforpay.com ↗ checked 2026-09-25
With a hold (two-stage payment), funds can be held for a maximum of 20 days (1,728,000 seconds) and a minimum of 1 minute (60 seconds); the default is also 20 days.
Source: wiki.wayforpay.com ↗ checked 2026-09-25
A refund (full or partial, with the amount set as a separate parameter) is done through the Refund API method or manually from the M-portal merchant dashboard.
Source: wiki.wayforpay.com ↗ checked 2026-09-25
Recurring payments support 7 charge frequencies — once, daily, weekly, quarterly, monthly, every two months (bimonthly), half-yearly and yearly; a separate CHANGE call can update an existing subscription's amount, date or frequency.
Source: wiki.wayforpay.com ↗ checked 2026-09-25

Limits

The limits come from both systems. A hold can keep money blocked on a card for at most 20 days; after that it has to be charged or released, so the reminder is set well before. WayForPay does not issue fiscal receipts directly: a receipt reaches the Checkbox cash register through the AssetPayments module. Apple Pay and Google Pay support is not confirmed by the same WayForPay documentation, so we check it for your account before promising it. WayForPay's ready plugins cover website platforms such as 1С-Bitrix, not 1С/BAS, so the link is set up by us. 1С/BAS is on the official prohibited software list: we do not take projects for state bodies, critical infrastructure or systems with state data, and with private businesses we discuss the risk openly.

How to start

Three steps from a first message to work on your project.

01
Leave a request
Describe the task in the form — in text or by voice. Budget and timing are optional.
02
We review and estimate
A developer studies the brief, asks about anything unclear and sends an estimate.
03
We start
Once scope and price are agreed, the work begins.

Leave a request

or write to info@coreviaflow.space

Live project We built and run Gemalli — a B2B export platform with producer pages, a CRM and a deal chat. Read the case →

Questions

Can we refund only part of an order?

Yes. WayForPay supports full and partial refunds, and the part is taken from the return document in 1С/BAS, so the refund matches the items that actually came back.

Does the WayForPay dashboard stay in use?

Yes, for reports, settings and one-off manual refunds. Everyday payments, holds and returns go from 1С/BAS, and a refund made by hand in the dashboard is agreed as an exception.

Does our site need its own card data protection?

Not for the pop-up form: the payment is handled on the WayForPay side, so your site does not take card data itself.

Can we test without real money?

Yes. WayForPay provides test merchant details, so payments, holds and refunds from 1С/BAS are rehearsed first without touching real money.