Error 4309 Sberbank what to do. Sberbank terminal error codes: overview, how to fix. Sberbank Online - why is it not available? Possible errors and ways to solve them

Good afternoon everyone. My first post - I hope it will help someone, it’s just that an incredible amount of time was spent on all this.

The problem is like everyone else's - with this notorious "p" file when working through an RDP terminal session with a server, with Sberbank terminals (at the same time with cash registers - we have ATOL 30F).

1. Cash desks. Normal work and acceptable printing speed was achieved only by implementing port forwarding via VSPE.
At local stations, all cash registers are connected to ports 10 and 11, in the VSPE client part a unique port is set for each computer - for example 5001, 5002, etc., on the VSPE server it listens to them. In 1c (we have KA1.1), a separate device is created for each cash register and the required port is selected. Those. There are a lot of cash registers in commercial equipment. The conf has been slightly modified so that a specific instance of a cash register can be linked to a department.

2. Acquiring. (I’ll immediately express my disapproval to Sberbank and the office that sets up and maintains the equipment). From the very beginning, the task was such that sellers could not enter numbers into the terminal by hand, and the data for the operation came from 1C. There was only one acquirer - Sber, because... online cash register systems were not yet planned - integrated (externally controlled) terminals with a receipt printer were needed. We were supplied with Ingenico IPP480 devices at all points (about 100). The software was installed on the server - folder sc552, dlls were added from it, one equipment was created in 1c with 1 fixed com port(7). Forwarding is done using RDP - each session has its own com port, there is no confusion. After installing the cash register, no problems arose - the acquiring receipt was printed on the terminal, and the cash receipt was printed on the cash register.
After some time, I transferred about half of the terminals to another bank (due to the bank’s complete lack of customer focus - for six months (this is not an exaggeration) - they changed me the legal entity on which the point operates. My individual entrepreneur has been closed for a long time - and I have money for my account come from acquiring...) The new acquirer has an Arcus2 system, Ingenico IPP320 terminals without a printer. Having dug deeper, we achieved normal printing of acquiring receipts on cash registers. With one caveat - this system, by analogy with Sberbank, creates files cheq.out and chek.out in the server directory C:\Arcus2\ - which contain the text for printing a check; equipment processing grabs them and transfers them to the cash register for printing. Typically, files appear when a payment is made and then are deleted on their own. It is clear that with simultaneous access there will be an error (they do exist - but rarely), and sometimes the file freezes and is not deleted for some unknown reason. All terminals stop working due to a file access error. For such cases, a batch file has been written that every 10 minutes checks the current time and the time the cheq was created - if the difference is more than 10 minutes, then the file is frozen and the batch file deletes cheq.out. In 20% of cases it does not remove and has to be removed by hand. It's bad - but it works.

There was a need for 3 more terminals from Sberbank - they said they no longer produce IPP480, they brought 3 Verifone VX820 without a printer, of course. The work of the installers is of course touching - they put the SC552 folder on the local computer, run the USB driver on the device and run loadparm - reconciling the results - do you see the windows running through, the reconciliation was completed? do you see the "p" file appearing? Well, everything is ready!! And the fact that the 1c terminal doesn’t see them point-blank and I need not 9 com but the 7th, and the fact that the check on the cash register is not printed - they are deeply violet...

Further on the actual topic:
On the client computer in our situation - working via RDP with terminal server- you only need to install USB driver on the device itself. SC552 is needed only for initial (or further) testing of the terminal itself without 1c. Those. it can be safely deleted and no libraries need to be registered. Even if this folder exists on the local computer, no calls to it occur when working with RDP - i.e. for example, it is useless to edit the pinpad.ini file there - when running from the server, only the folder on the server C:\SC552\ works and the settings are read from there. There is no need to scatter SC552 folders among user folders and register libraries from there. Everything is done from the 1st folder on the server.
Because We already had a folder on the server - the first terminal started successfully - I created a file on the server in the folder C:\SC552\p. The reconciliation went through, the payments went through - there was no receipt for RRN/
The server had a DLL version of approximately 23 - and new terminals are designed for 29 (their firmware version must match the DLL version - this is in theory, in practice - depending on how it goes - it may work, or maybe not). We took a risk - we updated the DLL on the server - we were afraid the old terminals would stop working. No, lucky - they work. And the new VX820 began printing receipts on cash registers.
But it turned out that after one terminal created the p file - when trying to perform an operation on another - there was no access to this file. We slightly increased the rights for all users to the SC552 folder - and access appeared - one by one the terminals carried out operations, created a p file and issued a check to the cash register.
Old terminals that have a printer - they don’t care about this file - they don’t use it.

coming age=sign\ Show


This is what our file looked like initially.
If you comment out PrinterFile=p, the receipt will not be printed on the cash register.
If you write something else - for example PrinterFile=p22 - a p22 file will be created.
The task is to distribute these files - each terminal has its own.
It has been established that %UserProfile% does not work for us - the reason became obvious almost immediately - our users are set to Cyrillic.
For example, having specified PrinterFile=Vanya1, I received file “1”.
After reading about Windows system variables, I started trying different options - so that the files could somehow differ from each other.
I came across %CLIENTNAME% - the name of the computer connected to the RDP session. First of all, with us it is specified in Latin letters and is unique - i.e. each terminal can be identified by %CLIENTNAME%. And it took off. Now the line looks like this:

PrinterFile=%CLIENTNAME%


Instead of a mess with all sorts of SUBST, creating SC552 folders for each user along the %UserProfile% path and renaming users to Latin names - all printed files are in one folder, but with different names.
It would be nice to do this in Arcus - but it hasn’t worked out there yet.

PS - and one more thing - there is a program called TLvEdit - which reads and writes the firmware parameters of the terminal itself - so there is a setting there - the order of interaction with the cash register - there must be the correct checkbox - on the item (I don’t remember verbatim) - “Print a receipt on the cash register " - if the checkbox is not checked, you will not receive a receipt at the cash register.

When working with a Sberbank terminal, everyone may encounter various errors displayed on its screen, and errors can arise both due to problems in the operation of the terminal itself (software, bank), and when an operation is carried out incorrectly on the client’s side (input errors data, problems with the card, etc.). In this review, we will look at the most common error codes of Sberbank terminals, find out what they mean and what to do if they appear.

The most popular Sberbank terminal error codes

The full list of error codes is quite large and is constantly being updated, as new functions appear in the operation of any software, in particular in bank terminals, the order of various operations changes, etc.

Below we will look at the most popular error codes and what they mean:

  • Error 05. Authorization was rejected, do not perform the operation.
  • Error 57. It is unacceptable to carry out an operation for this type of card (the terminal “does not allow” the operation)
  • Error 99. Card payments were not made.
  • Error 362. Indicates problems with the chip.
  • Error 2000. Transaction error in the terminal (payment by card was not made).
  • Error 4100. No connection with the bank.
  • Error 4118. The PIN code was entered incorrectly.
  • Error 4119. There is no connection between the terminal and the bank.
  • Error 4120. The terminal pinpad is faulty.
  • Error 4125. The card has a chip (you must use the chip, not the magnetic stripe on the card).
  • Error 4134. The results were not reconciled in the terminal for a long time.
  • Error 4309. No document found to print.
  • Error 4322. There is a problem with the operation of the terminal or the software installed in it.
  • Error 4401. Transaction authorization is required (you need to call the bank).
  • Error 4403. The terminal is locked.
  • Error 4405. The operation was not completed.
  • Error 4441. Command to withdraw the card from the client.
  • Error 4455. Error when entering card PIN code.
  • Error 4457. Sberbank blocked the transaction (reasons on the card side).
  • Error 4496. The terminal is not configured correctly.
  • Error 4497. Technical work is being carried out on the server.
  • Error 5001. There is a problem with the terminal settings or a problem with the bank card chip.

Having learned the most common errors of the Sberbank terminal, we will consider further how you can correct these errors and whether it is even possible to do it yourself.

Error code 05

Error code 05 in the terminal occurs if the user's authorization is rejected and it is recommended not to carry out the operation (there may be various reasons: the card or account is blocked, the limit has been exceeded, authorization was not completed correctly).

The card owner can correct this problem by contacting Sberbank employees at the branch or by calling the bank’s hotline.

Error code 57

Error 57 in the Sberbank terminal can be displayed for several reasons, and the problem is not in the terminal, but in the card: this card cannot be used for payments through terminals (for example, you can only withdraw money from this type of card at an ATM) or it may have expired card expiry date.

The card owner must solve this problem by calling the Sberbank support phone number or personally visiting a bank branch.

Error code 99

Error 99 in the terminal occurs when there is a problem with contact with the pinpad in the terminal (in most cases the problem is in the cable).

To correct this error, the first thing you need to do is check the cables going to the terminal pinpad; if they are in order and securely connected and there is no visible damage, then you need to contact Sberbank technical support (the service that installed the terminal).

Error code 362

Error 362 when working with a Sberbank terminal occurs when there is a problem with the chip in the bank card (there is no contact between the chip on the card and the terminal).

You can solve this problem if you remove the card from the terminal, clean the chip on it with a clean cloth and try to use the card again. If the problem is not solved, you can use another card with a working chip.

Error code 2000

Error code 2000 in the terminal usually occurs when you enter the PIN code incorrectly or press the red button on the terminal after entering the PIN code.

To correct this error, you need to re-execute the payment transaction through the terminal; if the problem arises again, you need to contact Sberbank technical support.

Error code 4100

Error 4100 is displayed in the terminal if there is no connection between the Sberbank terminal and the server.

To solve this problem, you need to repeat the operations after a few minutes. If after 2-3 attempts the problem is not resolved, you need to contact Sberbank support (the specialists who installed the terminal).

Error code 4118

Error 4118 in the Sberbank terminal occurs when the card PIN code is entered incorrectly.

To solve this problem, you need to perform the operation again, carefully entering the correct PIN code from the card.

Error code 4119

Error 4119 in the terminal occurs when there is a problem in the connection between the terminal and the bank.

To solve this error, you need to repeat this operation after a few minutes, and changing the dynamic IP address in the terminal’s Internet connection to a static one can also help.

Error code 4120

Error 4120 in the Sberbank terminal occurs when there is a problem with the terminal's pinpad (technical error).

Only the Sberbank specialist who installed this terminal can fix this problem.

Error code 4125

Error 4125 in the terminal occurs when you try to perform an operation in the terminal using a magnetic stripe when there is a chip on the card.

To solve this problem, just insert the card into the terminal and pay using the chip, and not through the magnetic stripe.

Error code 4134

Error 4134 in the Sberbank terminal occurs if the terminal has not reconciled results for a long time.

To correct this error, you need to reconcile the results in the terminal, after which you can immediately carry out the desired operation.

Error code 4309

Error 4309 in the terminal occurs if the terminal did not find a document to print (technical error).

You won’t be able to solve this error on your own; you need to contact the Sberbank specialists who installed this terminal.

Error code 4322

Error 4322 when operating the Sberbank terminal occurs when there are problems in the operation of the terminal software or there are malfunctions in the terminal itself.

This error can only be corrected by a bank specialist who installed this terminal.

Error code 4401

Error 4401 in the terminal occurs when there is an authorization problem in the terminal.

To solve this problem, you need to call the Sberbank authorization service and follow the operator’s instructions step by step.

Error code 4403

Error 4403 appears on the terminal screen if the terminal has been locked.

In this case, to solve the problem, you need to contact Sberbank support (the specialists who installed the terminal).

Error code 4405

Error 4405 in the Sberbank terminal occurs when an operation is canceled (the operation was not completed for a specific reason, for example: the PIN code was entered incorrectly, the operation sequence in the terminal was not completed correctly).

To fix this problem, you need to perform the operation again, but if the error occurs again, contact Sberbank technical support.

Error code 4441

Error 4441 is displayed in the terminal if the bank's security protocol has worked and the seller needs to seize this card from the client and refuse to carry out the transaction (perhaps the card was stolen or there are other problems).

Error code 4455

Error 4455 is displayed in the terminal when the cardholder has entered the PIN incorrectly.

To solve this error, just enter the correct PIN code for this bank card and the operation will be carried out.

Error code 4457

Error 4457 when working with a Sberbank terminal is displayed if the operation is not allowed due to problems with the card itself. If such an error occurs, the client must be denied the transaction.

To solve this problem, the cardholder needs to contact Sberbank support service.

Error code 4496

Error 4496 during terminal operation occurs if the terminal itself is incorrectly configured.

To fix this problem, you need to contact the Sberbank support service and the specialists who installed the terminal and configured it.

Error code 4497

Error 4497 ​​in the terminal occurs if technical work is being carried out on the Sberbank server.

It is impossible to carry out an operation through the terminal at this moment and you must wait (15-20 minutes until routine work is completed on the server) and carry out the operation again.

Error code 5001

Error 5001 in the Sberbank terminal is displayed if the terminal is configured incorrectly or there is a problem with the data on the card chip.

You cannot correct this error on your own and you must contact Sberbank technical support specialists.

We also read about (their description and correction methods).

In conclusion to this article, it can be noted that every business owner, seller or ordinary user may encounter errors when working with Sberbank terminals, so the main thing in such a situation is not to panic, but to immediately figure out what the problem is and how it can be quickly solved, guided by the instructions indicated above. We leave our feedback and useful tips on what errors the Sberbank terminal has and what to do if they occur in the comments to this article and share it on social networks if it was useful to you.

Sberbank of Russia software error codes

Error code

Possible reason

Cashier actions in case of error

Incorrect terminal setting

Lost contact with pinpad

Check the cables going to the pinpad. If everything is in place, contact the Sberbank staff who installed the terminal

361, 362, 363, 364

Lost contact with the card chip

Remove the card, wipe the chip with a soft cloth and repeat the operation

The client made a mistake when entering the PIN

Client PIN is blocked

Card has expired

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

The date set on the terminal is incorrect

Set the correct date on the terminal and repeat the operation

The operation is not possible. Refuse the client and advise to top up the card

Card has expired

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

Card blocked

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

The card service period has expired

Card blocked

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

Client PIN is blocked

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

Operation aborted by pressing CANCEL key

Perhaps, when entering a PIN, the client accidentally pressed the red key on the pinpad. Repeat the operation.

Customer takes too long to enter PIN

Repeat the operation. You have 1 minute to enter your PIN.

2004, 2005, 2006, 2007, 2405, 2406, 2407

Card blocked

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

Insufficient funds to load onto the card

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

The client's card shows an interrupted loading of funds

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

3019, 3020, 3021

No connection with the bank

Terminal card not collected

Card chip exchange error

Contact the Sberbank staff who installed the terminal

The card number was entered or read incorrectly

Repeat the operation. If the operation fails after 2-3 attempts, contact the Sberbank staff who installed the terminal

4110, 4111, 4112

It is required to collect the terminal card

Collect the terminal card and repeat the operation

The limit allowed without communication with the bank has been exceeded

The operation is not possible. Refuse the client and advise him to contact any Sberbank branch

Manual entry for such cards is prohibited

The operation is only possible if the card is read through a reader and not entered manually from the keyboard

The last 4 digits of the card number were entered incorrectly

Enter the last 4 digits of the card number again. If the error persists, abort the operation and remove the card.

The client refused to enter a PIN

Perhaps, when entering a PIN, the client accidentally pressed the red key on the pinpad. Repeat the operation, explaining to the client that the operation is impossible without entering the PIN.

The pinpad is faulty

Contact the Sberbank staff who installed the terminal

There is a chip on the card

Insert the card into the chip reader and continue the operation

Incorrect terminal setting

Contact the Sberbank staff who installed the terminal

Terminal memory is full

Reconcile the results and repeat the operation

The pinpad has been replaced

Contact the Sberbank staff who installed the terminal

The transaction was rejected by the card. The card may have been removed from the chip reader before the receipt was printed.

Repeat the operation. If the error repeats, refuse the client

It took too long to reconcile togs on the terminal

Reconcile the results and then repeat the operation

4300, 4301, 4302, 4303, 4305, 4306, 4308

The cash register is incorrectly configured

Contact the Sberbank staff who installed the terminal

Need to call the bank

Regulatory maintenance is being carried out on the server

Surgery is not possible at this time. Repeat the operation after 10-15 minutes.

Command received to remove card

Seize the card and refuse the client to carry out the transaction

There are not enough funds on the card

Card expired

Refuse the client to carry out the operation

The client made a mistake when entering the PIN

Explain to the client his error and repeat the operation

Transaction not allowed due to card related reasons

The operation is not possible. Refuse the client and advise him to call the Sberbank helpline

The operation is not allowed due to reasons related to the terminal settings

Contact the Sberbank staff who installed the terminal

Regulatory maintenance is being carried out on the server

Surgery is not possible at this time. Repeat the operation after 10-15 minutes.

The client made a mistake three times when entering his PIN and is now blocked

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

Incorrect terminal setting

Contact the Sberbank staff who installed the terminal

Regulatory maintenance is being carried out on the server

Surgery is not possible at this time. Repeat the operation after 10-15 minutes.

Incorrect terminal setting

Contact the Sberbank staff who installed the terminal

Incorrect terminal settings or data on the card chip is corrupted

Contact the Sberbank staff who installed the terminal

The data on the card chip is corrupted

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

Card has expired

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

The card's validity period has not yet begun

Operation not possible

This operation is not allowed for this card.

The operation is not possible. Refuse the client and advise him to contact the bank where the card was issued

5116, 5120Document

Disciplines (module) No. Code controlled competence (or its ... stylistic and logical errors, difficulties in drawing conclusions By material presented, ... problem): Bringing SWOT analysis Sberbank Russia (By materials from the official website) and development...

  • All-Russian competition of social projects on technology for primary and secondary school students “Social project Forward Russia!”

    Contest

    ... - By completeness (mono-subject, inter-subject); By quantity... errors. Appendix Application for participation in the competition: “Social project - Forward Russia... Branch No. 8615 Sberbank Russia Kemerovo... personal account number ( code) payer) Full name ...

  • Educational and methodological complex of the academic discipline “foreign (English) language in the professional sphere” in the direction of 080200. 62 Management (qualification (level) “bachelor”)

    Training and metodology complex

    128 Writing file in S.V. Analysis of typical errors By Test No. 3. 27. Unit 3: “... in your hands when you use the services Sberbank Russia"; - emphasis on relationships... communication can be seen as a certain code. Signal encoding and decoding...

  • Monitoring of the Russian media on pension issues September 8, 2014

    Document

    Billion rubles) and non-state pension funds Sberbank(RUB 73.6 billion). ...accepted reporting. Quantity errors became critical in the end... making mistakes with digital code Database". “Mistakes... of the Pension Fund Manager Russia By Murmansk region Lyubov Gubkina...

  • Information bulletin of local self-government Published by ASDG in agreement with OKMO since February 2008

    News bulletin

    2020. "To avoid errors and a waste of energy,... CMO: By registration of citizens By place of stay and By place... partially affects the training code municipal employee. I see... related to working with Sberbank Russia and VTB, we managed to restart...

  • Every citizen of Russia has a Sberbank plastic card. It refers to a different payment system - Visa, MasterCard or Maestro. It can also be cumulative, debit or credit. With its help, you can pay for purchases or services, pay traffic fines and top up your mobile device account balance. It is not always possible to pay for goods with a bank card, so a Sberbank client needs to withdraw cash from an ATM. The terminal is used to perform various types of transactions. For example, transferring funds to another bank client or paying for housing and communal services. Sometimes the user encounters a problem; instead of information about a successfully completed operation, an error message appears on the screen. They are often associated with an internal failure in the system. For this reason, it is necessary to know what the numbers that appear on the screen mean so that you can take appropriate action.

    Error 4309 Sberbank terminal in the 1c program is not related to the actions of the user himself. This problem occurs after configuration updates or the machine has run out of print ribbon. This error means there is nothing to print. When the receipt tape is present, but error 4309 is displayed, the internal terminal system cannot independently recognize its installation. The bank client checks to see if there are any scraps of checks or foreign objects in the device itself that issues checks. If there are no external signs that interfere with work, then contact the department staff for help. If the terminal is located in a remote place, then call the Sberbank technical service and explain what error occurred and under what actions.

    What does error 4405 mean on a Sberbank ATM?

    This code is one of the most common, and is found not only on Sberbank electronic ATMs, but also on mobile devices. Error 4405 is issued by the Sberbank terminal when transactions were not successfully completed. That is, payment or transfer is not based on a banking product. Often this code is accompanied by additional information. The device notifies you that there is a break in the signal or that a poor-quality network is being used.

    This problem is faced by users of banking services of third-party financial institutions who perform transactions at an ATM. Sberbank issues code 4405 when it suspects that a person wants to commit fraudulent actions, and then blocking occurs.

    Important. When a similar situation occurs, the bank client needs to contact the call center and explain what is happening with the terminal. In addition, send a message to the technical service to the short number 9000. Bank employees will contact the victim as soon as possible and help eliminate the reasons for the failure to complete transactions.

    If the error occurs directly on the mobile device, then try the following:

    • reboot the mobile device;
    • restart the application;
    • reconnect to the network.

    If these steps do not help, contact the bank's technical support.

    Why does error 4119 occur in the Sberbank payment machine?

    A bank client encounters error 4119 in the terminal. There can be many reasons why this code appears on the screen. First of all, it means that the connection between the ATM and the banking organization itself has been broken. In this case, it is impossible to complete any transaction. This happens when the Internet connection is disconnected or the payment terminal does not work correctly. Then, to restore its functionality, it is recommended to reboot the device. The user can wait approximately 10 minutes and then try the transaction again. If after several attempts no changes occur, you should contact technical service.

    Important. Error 4119 occurs when the KLK key that is entered for the pinpad is incorrect. This can only be corrected by ATM technical service specialists, as it is necessary to reduce the baud speed or change the current IP address.

    Error 4468 in the Sberbank terminal

    This error does not cause serious problems for the owner of the plastic product. It means that at this moment technical work is taking place in the system. During this period of time, you cannot carry out any transactions through a Sberbank ATM. But upon completion of the prevention, performance will be restored, and the client will be able to perform certain operations through the device. Sberbank carries out this technical work on a monthly basis; this is stipulated in the company’s regulations. As a rule, updating the server does not take much time, so you can try again to enter the plastic in 10-15 minutes.

    The most common Sberbank ATM errors

    Any system can fail, and the Sberbank payment terminal is no exception. Since they work around the clock and are subject to various types of malfunctions. Most often, it is impossible to fix the problem yourself, since it is necessary to make changes to the system itself; only Sberbank employees have access to it. Let's take a closer look at the errors that may appear on the payment terminal:

    • error 4134 is a problem with tags not being verified on the device for a long period of time. The violation is eliminated quite quickly, it is enough to calculate the results and you can immediately start using the device;
    • error 362 is not related to the operation of the terminal. The contact between the chip and the plastic has broken. The problem can be fixed on the spot; to do this, you need to rub a soft material over the chip that is installed on the credit card. Then try to insert the card into the terminal again. If code 362 appears on the monitor again, then you need to contact the bank branch;
    • error 4401 – authorization problem. To eliminate it, you need to contact Sberbank employees and, under their guidance, correct this problem;
    • error 4457 – the transaction is prohibited by the Bank due to problems;
    • error 4118 – error when entering the PIN code. The device cannot recognize the correctness of the input, the client entered it incorrectly or the red button was touched when pressing the keys. You should try to reinsert the plastic into the payment terminal, but if input problems persist, contact a specialist;
    • error 2000 - this problem occurs due to an error by the client itself. The cancel button was pressed while performing various operations. Then you need to remove the payment card from the device and try the operation again.

    Bank cards have become a part of human life; various transactions are made with their help. They are convenient to use when paying for goods or services. But sometimes you just need to withdraw cash or make a transfer to another person. Then you can’t do without the help of a Sberbank ATM. But the technical device does not always work properly, and in case of any failure in the system it displays an error on the screen.

    Each code means its own malfunction, and only technical service workers know how to fix the problem. Most errors are related to internal technical malfunctions, so the user of Sberbank banking services needs to report the error by calling the call center or sending a message to 9000. Then the employees will advise and describe in detail what actions need to be taken to resolve the problem.



    
    Top