The bank terminal check slip is not printing
A slip receipt is confirmation of a card payment made through a bank POS terminal.
In Torgsoft, slip receipt data can be automatically transferred to the fiscal receipt of a hardware registrar (ECR), to the receipt of a software ECR (pECR), and can also be printed on a non-fiscal sales receipt (if the corresponding variables are configured in the template). However, since in the case of cashless payment the customer must receive a fiscal receipt, using only a non-fiscal receipt as proof of payment is fundamentally incorrect. If the bank transaction data (acquiring details) do not get into the fiscal receipt of the ECR or pECR, it is considered to be issued in violation of the rules.
This instruction concerns not only printing the receipt, but also the correct transfer of bank transaction details to the fiscal document, so it should be followed carefully. If you repeat the payment without verification, change print templates, or disable the transfer of bank data, you may get a duplicate transaction or a receipt issued in violation of the rules. Before making changes, make sure you understand whether the problem is specifically in printing, in the template, in the bank terminal, or in the operation of Windows/RDP. If you have doubts about the correctness of the fiscal receipt, it is better to contact technical support.
When the slip receipt is not printed after payment

-
After a successful card payment, the terminal confirmed the transaction, but the receipt was not printed (the data did not reach the printer memory, or a physical problem with the device occurred).
-
The fiscal receipt was generated, but without the bank transaction data.
-
When trying to send the amount to the terminal, a DeviceBusy error appears (because of this, the payment is interrupted, and receipt printing is not initiated at all).
How to understand at which stage the problem occurred
-
The printer stays silent after card payment.
-
There is a receipt, but without the bank terminal block (RRN, AID, authorization code).
-
The slip receipt text is cut off at the edges.
-
The cash register “freezes” after payment confirmation.
Why the slip receipt is not printed or does not get into the receipt
-
Torgsoft settings
The transfer of data from the bank terminal is disabled, or no printer is selected for the current Windows user. -
Print template
The template does not contain the slip receipt variable (SLIP-check). -
Bank / terminal settings
The terminal works under a protocol without waiting for confirmation from the cash register (for example, BPOS is set instead of BPOS1). Because of this, the terminal does not successfully synchronize the completed payment with the subsequent printing algorithm in Torgsoft. -
Technical problems with Windows / RDP
The print queue is clogged on the local PC or server, the Print Spooler service is frozen, or the system disables power to USB ports to save energy. When working remotely (RDP), the cause of the printing failure is not the fact that the printer wakes up, but the instability of the internet connection or a system “freeze” of the redirected driver in the Windows Server session.
How to find the cause and restore slip receipt printing
A. Check the settings in Torgsoft
-
Open Settings → Parameters → Receipt.
-
Enable the option «Transfer bank terminal payment information».
-
Go to Settings → Printer Selection and make sure that:
-
in the field «Print the non-fiscal receipt on the printer», your receipt printer is selected from the list of devices installed in the system,
-
the settings are configured specifically for the current workstation (for the current program user), since printer selection in Torgsoft is stored locally.
-
Check: perform a test sale for the minimum amount.
B. Check the print template
-
Open Settings → Print Template Settings.
-
For 57/58 mm paper, use a template of the «56 mm» type.
-
Make sure that the SLIP-check element is present in the template.
If the template was edited manually, the absence of this variable means: the data will be sent to the tax authority, but will not appear on paper.
C. Check the bank terminal
-
Slip receipt transfer
For the slip receipt to be printed, the bank terminal must return the transaction information back to the cash register program. Some banks’ terminals do not return slip receipt data to the cash register by default. If this situation occurs, this setting can be changed only by contacting the technical support of your acquiring bank.
-
Separate merchants for payment and refund
Depending on the configuration of the acquiring bank (this concerns different terminal models such as Ingenico, PAX, Verifone, and others), for correct processing of operations it is sometimes necessary to create two separate merchants in Torgsoft: one is configured exclusively for the «Payment» operation type, and the other for «Refund».
-
DeviceBusy error (Device is busy)
This error relates directly to the payment processing stage, not to the printer itself. It occurs when Torgsoft tries to send the amount to the terminal, but the device rejects the request. Since the transaction does not even start, the receipt is not generated and is not printed at all. For the payment to go through successfully, make sure that the terminal:
-
is not in the service menu (for example, the cashier printed the X-balance and forgot to return to the main screen);
-
is not performing another background operation and is ready to receive commands from the cash register.
D. Check Windows and RDP
-
Print queue
Clear the queue and restart the Print Spooler service.
-
USB power saving
Disable the option that allows USB devices to be turned off to save power.
-
Problems with remote access (RDP) and the network
Failures during remote work (RDP) affect the receipt printing process as a whole, not the disappearance of the slip receipt specifically. Usually, standard printer redirection (Easy Print) works quite stably. However, if the receipt is not printed, the cause may be a frozen print service (Print Spooler) on the server or a short-term internet interruption. If standard printer redirection from the local PC to the server conflicts with your version of Windows Server, there are alternative setup options:
-
Printing through the LPR/LPD service (a reliable workaround for RDP sessions).
-
Printing by IP address (possible only if your printer model has a built-in Ethernet network port or Wi-Fi module).
How to check that the receipt is printed correctly
-
Process a card payment.
-
The printer must print a receipt with the bank data block.
-
The fiscal receipt contains acquiring information without validation errors.
How to avoid problems with slip receipt printing
-
Do not edit standard templates without a backup copy.
-
Update Torgsoft regularly.
-
29.01.2026
Exceeded number of workstations" error when working with a banking POS terminal
How to fix the license error when connecting a banking POS terminal to Torgsoft. Guide on clearing old workstation bindings.
-
28.01.2026
Setting up the PAX A930 bank terminal (JSON / Wi-Fi)
Guide on connecting and configuring the PAX A930 Android banking terminal in the Torgsoft program via the JSON (COM/TCP) protocol over Wi-Fi
-
22.01.2026
The bank terminal check slip is not printing
The bank terminal slip check is not printed: how to check the printer, template, terminal and transfer of details to the fiscal check









Go back to the previous step