Ошибка код 579

• Message has been processed and sent to the next instance, i.e., a mobile operator with request acknowledgment from their platform. The delivery report has not yet been received and is awaited, so the status is still pending.

• Message has been processed and sent to the next instance, i.e., mobile operator.

• Message has been accepted and processed, and it`s ready to be sent to the next instance, i.e., operator.

• Message has been sent to the operator, whereas the request was rejected, or a delivery report with status REJECTED was reverted.

• Message has been sent to the operator but has failed to deliver since a delivery report with status UNDELIVERED was reverted from the operator. 

• Message has been successfully sent and delivered to the operator.

• Message has been successfully processed and delivered to the recipient.

• Message was received and sent to the operator. However, it has been pending until the validity period has expired or the operator returned EXPIRED status in the meantime.

• Message has been received and forwarded to the operator for delivery. However, the delivery report from the operator has not been formatted correctly or has not been recognized as valid.

• Message has been received, but the network is either out of our coverage or is not set up on your account. Your Account Manager can inform you about the coverage status or set up the network in question.

• Message has been received but has been rejected as the number is not recognized due to an incorrect number prefix or number length. This information is different for each network and is regularly updated.

• Message has been received and rejected due to the user being subscribed to DND (Do Not Disturb) services, disabling any service traffic to their number.

• Your account is set to accept only registered sender IDs, and the sender ID defined in the request has not been registered on your account.

• Your account is out of credits for further submission. Top up your account. For further assistance in topping up or applying for an online account top-up service, you may contact your Account Manager.

• The sender ID has been blocklisted on your account via Infobip web interface. Remove the blocklist on your account or contact Support for further assistance.

• The destination number has been blocklisted either at the operator request or on your account via web interface, please remove the blocklist on your account via Infobip web interface or contact Support for more information.

• Account credits are past their validity period. Top up your sub-account with credits to extend the validity period.

• Your account has been set up for submission only to a single number for testing purposes, contact your Account Manager to remove the limitation.

• Message has been received on the system. However, your account has not been set up to send messages, i.e., no routes on your account are available for further submission. Your Account Manager will be able to set up your account based on your preference.

• Message has been rejected due to an anti-flooding mechanism. By default, a single number can only receive 20 varied messages and 6 identical messages per hour. If there is a requirement, the limitation can be extended per account on request to your Account Manager.

• The request has been rejected due to an expected system error. Retry the submission or contact our technical support team for more details.

• The request has been rejected due to a duplicate message ID specified in the submit request; the message IDs should be a unique value. For more information, refer to SMS on the Infobip API Developer Hub.

• Message has been received and our system detected the message was formatted incorrectly because of either an invalid ESM class parameter (fully featured binary message API method) or an inaccurate amount of characters when using esmclass:64 (UDH). For more information, visit the articles below or contact our Support team for clarification.
  User Data Header
  Concatenated SMS

• Message has been received, but the total message length is more than 25 parts or the message text exceeds 4000 bytes as per our system limitation.

• The request has been received, however, the to parameter has not been set or it is empty, i.e., there must be valid recipients to send the message.

• The request has been received, however, the destination is invalid—the number prefix is not correct as it does not match a valid number prefix by any mobile operator. Number length is also taken into consideration when verifying number validity.

• The URL of the audio file is invalid and could not be read properly.

• The language submitted within the request is not supported and request couldn’t be processed correctly.

• Native to Voice services, this status is returned in case there is no text sent in your Voice message request.

• Native to Voice services, this status is returned in case the notifyUrl parameter is not formatted properly. Refer to Send Voice over API for more information.

• Native to Voice services, this status is returned in case the notifyContentType parameter is not formatted properly. Refer to Send Voice over API for more information.

• Defined value for repeating message is invalid and must be a positive number.

• Defined value for the waiting period is invalid and must be a positive number.

• Defined value for the duration of the call is invalid and must be a positive number.

• Defined value for the total period of the call is invalid and must be a positive number.

• The action which attempts to detect answering machines at the beginning of the call is invalid.

• Actions submitted in HTTP API request are invalid.

• Action groups submitted in HTTP API request are invalid.

• Machine detection is not enabled. Contact your dedicated Account manager.

• Invalid deliveryTimeWindow. The time gap between from and to cannot be less than 1 hour.

• Status is returned when notifyUrl parameter is not formatted properly.

• Message has been received, but the textual part of message length exceeds 1600 characters set as our system limitation.

• This status code is returned by the API when a user’s free trial has been exceeded. It means that the user has exceeded the allowed number of messages or other usage limits during the trial period and must upgrade to their plan to continue using the service.

• This status code is returned by the API when there is an error in the data transformation process while creating the data needed to proceed with sending a mail. The error can be caused by the placeholders size exceeding limits, or data failing to parse, for example, custom headers.

• This status code is returned by the API when there is an internal error with the system processing a message. It is set when a message goes over the limit of retries or when internal data fails to parse.

• This status code is returned by the API when a validation check fails during the message processing. The validation error can be caused by issues such as an invalid sender, an invalid landing page, invalid preserved recipients, a missing template, and so on.

• The status occurs when in a Push API call in object TO defined filter which doesn’t resolve any pushRegistrationIds as destinations for Push delivery. Field to is used to query the message recipient segment. For example, you can try to target according to a “tag” which doesn’t exist at any of instances of the requested ApplicationCode; it will return no destinations as we couldn’t find anything that would satisfy the requested conditions in our database. In another example, you may want to target all application instances (devices) with the Android OS. In this case, you have to use CloudType: GCM and API internally will resolve all destinations and will send the message to all Android devices linked to the requested ApplicationCode. You can also check your valid registrations by using filtering in our web interface. You can more information about User Data at our SDK pages: iOS and Android.

• The status occurs when an invalid or non-existent ApplicationCode is used in the field from in a Push API call. Each application profile has its own unique ApplicationCode. ApplicationCode is used in SDK as a key identifier for the Application installed on an end user’s device able to communicate with our platform. For the paired device + installed app, pushRegistrationId is issued and it is uniquely linked to ApplicationCode. You should be able to get all available applications or check the configuration.

• There is no error description provided. Mostly returned for successful delivery, or when error code was not returned by the operator.

• The number does not exist or it has not been assigned to any active subscriber in the operator’s user database.

• Unidentified Subscriber

• The subscriber is detected unavailable as there was no paging response from the handset. This is often due to the handset being switched off or low signal area. Applies to MAP protocol version 3.

• The mobile device has not been recognized by EIR (Equipment Identity Register) during device verification on the MAP protocol level at operator’s infrastructure.

• The subscriber is currently in roaming in another country or other operator’s infrastructure — roaming delivery is not guaranteed due to lack of roaming agreements between many different operators.

• Illegal Subscriber

• The subscriber’s mobile service has been suspended by the operator.

• Illegal Equipment

• Message is rejected due to barring of message service; blocking is set by operator or subscriber for the number.

• Facility Not Supported

• The subscriber is offline in the network, as confirmed by the handset’s paging response. This is often due to the handset being switched off.

• Subscriber Busy For Mt SMS

• SM Delivery Failure

• Message Waiting List Full

• System Failure

• Data Missing

• Unexpected Data Value

• Unknown Error

• There has been a mobile subscriber equipment error whereas the handset memory has been exceeded.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• There has been a mobile subscriber equipment error.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• The message has been successfully processed and forwarded to the operator, but no response was returned from the operator upon the message submit request, or such error was reverted by the operator. The error also applies to similar errors on SS7 network level.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• End users connected to this MVNO cannot receive Short Code messages. The mobile operator rejected the message as the end user is connected to their network via a mobile virtual network operator (MVNO). This restriction is on Short Code messages.

• The end user has asked their mobile operator to block any messages sent from your Short Code. Additional messages from the same Short Code must not be sent to the phone number unless the end user opts in again.

• End user out of prepay credit. The end user does not have enough credit on their phone account to receive the message. Message sending can be retried every 24 hours for no more than seven days.

• Temporary handset failure.

• Destination address unable to receive SMS.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• General network protocol error caused by incompatible operator network protocol versions or parameters between two network components.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• No Translation For This Specific Address

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Mobile subscriber was not reachable due to a network operator protocol error.

• Message was aborted by network peer because of a network protocol error.

• Message was aborted by network peer because of a network protocol error.

• Message was aborted by network peer because of a network protocol error.

• Message was aborted by network peer because of a network protocol error.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• Message was aborted due to other network protocol errors.

• The request type was invalid.

• Invalid destination address. Possible reasons for receiving this error for the following mobile operators might be:
  Any operator:
  -The mobile number is not on the mobile operator’s network.
  -The mobile number has been deactivated.
  T-Mobile and MetroPCS:
  -The phone number belongs to a prepaid user who does not have enough credit to receive a message.
  T-Mobile:
  -The end user is not provisioned to receive a message from all short codes (or from specific short codes).
  -The end user is on an MVNO connected via T-Mobile.
  -T-Mobile does not deliver messages from short codes to end users on MVNOs.
  AT&T (US):
• The phone number belongs to a prepaid user who does not have enough credit to receive a message, the phone number is not provisioned for any messages, or the phone number could be blocked due to a spam complaint.

• Invalid request — destination address country code is not recognized.

• Message text is too long.

• Invalid source address value. The mobile operator rejected the message with an invalid MT source address error. Contact your account manager to determine if your MT source address should be supported by the end user’s mobile operator.

• Source address (recipient) is blocked or is not provisioned.

• Account access denied.

• »Toll-Free Number Not Verified» which indicates that the number has either gone over the limit or they are trying to send to Canada and the number is not verified. Contact your account manager to get the TFN verified.

• Carrier sending limit has been reached. The message was blocked by AT&T because the TPS (transactions per second) limit on your messaging campaign has been exceeded.

• Carrier daily quota reached. The message was blocked by T-Mobile because the daily volume limit for your brand has been exceeded. You cannot resend the message until the next day.

• Program ID or campaign ID is not provisioned for this mobile operator or is not active.

• Account not provisioned to use SMS demo short code.

• Exceeded the time limit for using SMS demo.

• Destination address not in whitelist for SMS demo.

• Exceeded the maximum number of demo requests.

• Invalid global campaign ID.

• Account is not provisioned with the address that can reach the destination.

• Interaction not supported for message destination.

• Account is not provisioned for global two-way SMS.

• Content blocked by user opt-out (MO: STOP). This code can be returned in a delivery receipt for an MT originating from a North American, SMS-enabled toll-free number or an SMS-enabled landline number. Messaging can resume to the end user if the end user opts back in to your program.

• Content blocked by campaign blocklist.

• This message was identified as spam and cannot be delivered

• IMSI blocklisted

• The destination number has been blocklisted either at the operator`s request or on your account via the Infobip web interface. Go to the Infobip web interface to remove the blocklist on your account or contact Support for more information.

• The sender number has been blocklisted either at the operator request or on your account via Infobip web interface. Go to the Infobip web interface to remove the blocklist on your account or contact Support for more information.

• Source address is blocklisted on the Infobip account.

• Invalid PDU Format

• Your account monthly credit limit has been reached. For further financial assistance, please contact your account manager.

• The request was received, but has not been sent to the next instance within its validity period and has expired with the appropriate error code EC_MESSAGE_CANCELED, or the same error code was reverted from the operator.

• The message was sent to the next instance and has not been delivered within the message validity period, thus it has expired with the appropriate error code EC_VALIDITYEXPIRED or the error code was reverted from the operator.

• Inbound SM can not be transferred via SMPP due to the lack of SMPP connectivity.

• Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of messages sent to a single number.

• Related to status REJECTED_FLOODING_FILTER, the message is rejected due to the number of identical messages sent to a single number.

• Bearer Service Not Provisioned

• SS Incompatibility

• Indicates that invoked MAP operation could not be finished due to the network congestion — this is an SS7 network congestion error on the MAP protocol level.

• Unknown Alphabet

• Mobile operator not found for the destination address. The service performed a dynamic carrier lookup for the destination address, but it could not be identified; or, the MT source address is not a North American toll-free phone number or landline.

• Invalid Response Received

• Mobile operator blocking the end user from this Short Code

• Content blocked by mobile operator for this end user.

• Short code not provisioned with mobile operator. Contact your dedicated Account Manager if you believe that you are provisioned for the operator or if you want to begin provisioning.

• Short code expired with mobile operator. Contact your dedicated Account Manager if you believe that you are provisioned for the operator or if you want to begin provisioning.

• Short Code blocked by mobile operator. The mobile operator rejected the message as the Short Code is currently blocked from sending messages across their network. Contact your dedicated Account Manager if you are unsure why you received this error.

• The mobile operator is blocking the phone number from receiving messages from Short Codes. This is likely due to the end-user’s account being suspended or barred in some way.

• Destination address not provisioned for SMS.

• Destination address suspended by the mobile operator.

• Program ID or Campaign ID rejected by mobile operator. This error applies to messages sent to US mobile operators. The error indicates the program ID or campaign ID in the message request is not provisioned with the mobile operator. Contact your dedicated Account Manager if you are unsure why you received this error.

• New subscriptions for this short code are blocked by the mobile operator. Indicates that for a given Short Code, new subscribers are not allowed to receive or send messages. However, existing subscribers are still allowed to receive and send messages.

• Destination overloaded.

• Mobile operator network error.

• SMS rejected by the mobile operator for attempted destination address.

• Message failed due to an unknown mobile operator error.

• Failed message delivery.

• Message expired before it reached handset.

• Message submitted to but not acknowledged by the mobile operator.

• Time Out

• The number was flagged as blocklisted in the DND (Do Not Disturb) blocklist provided by the operator, or the same error code was reverted by the operator.

• Text blocklisted

• Not Submitted To GMSC

• Not Submitted To Smpp Channel

• The same message has already been sent to this destination address.

• The call has been received and answered.

• The call has been received and answered by a voice machine.

• Destination address is currently not available.

• Destination does not wish to participate in the call or cannot do so.

• The end user is currently busy to receive the Voice call.

• The end user received a call but didn’t answer it.

• The file specified in the HTTP request is inaccessible and could not have been downloaded.

• The format of the file specified is not supported.

• The received request was rejected because it wasn’t formatted correctly.

• The received request was rejected by the operator.

• The server has definitive information that the user does not exist at the domain specified in the Request-URI.

• The request requires user authentication on the operator’s end.

• There was no coverage for a specific destination number or the end user couldn’t be found in time during the call.

• The user existed once, but operator doesn’t support destination address anymore.

• Request entity-body is larger than the server is willing or able to process.

• The server is refusing to process the request because the Request-URI is longer than the server is willing to interpret (destination too long).

• Format of the file is not supported.

• Call or Transaction does not exist.

• Specified destination number is incomplete.

• Request has been terminated with a cancel button and end user refused to receive a voice call.

• The format of the request is not acceptable on the operator’s end.

• Server has some pending request from the same dialog.

• The submitted request is not supported on the operator’s end.

• The service failed to complete the request.

• The call ended due to a hangup initiated by the caller, callee, or API.

• Another device answered the call.

• A voice machine answered the call.

• A person (not a voice machine) answered the call.

• Max call or conference duration reached.

• Permission to use camera and/or microphone was denied.

• Camera and/or microphone not found.

• Camera and/or microphone not available.

• Media invalid or unavailable.

• The end user received a call but didn’t answer it.

• The end user is currently busy to receive the voice call.

• The end user canceled the call.

• The destination cannot join the call at the moment.

• The destination is temporarily unavailable.

• The received request was rejected.

• Insufficient funds to make a call.

• The request requires user authentication on the operator’s end.

• The server has definitive information that the user does not exist.

• The destination is currently out of service.

• The specified destination is invalid.

• The format of the request is invalid.

• There was no coverage for a specific destination, or the end user could not be reached in time for the call.

• There has been a network connection error.

• Service is currently unavailable.

• The call has ended due to an unknown reason.

• The requested feature is not enabled.

• Service is currently congested.

• The specified application URL does not exist or cannot be found.

• The specified application URL is unreachable.

• Specified application returned a response with an invalid format.

• The call has been received and answered.

• The call was answered on another device.

• The peer connection hasn’t been established.

• Invalid DTMF configuration (no audio track).

• DTMF options is not available.

• Invalid DTMF tone sent. Allowed tones are digits 1-9, * and #.

• Local stream was not initialized.

• The audio track is missing.

• The video track is missing.

• Display media API is not available.

• Unknown screen share error.

• The end user received the call but did not answer it.

• The end user is currently busy and not able to receive the call.

• Permission to use camera and/or microphone was denied.

• Device does not have a camera and/or microphone connected/enabled.

• Camera or microphone is already in use.

• The end user received an incoming call while they were on another active call.

• Call terminated.

• The end user is already joined on another device.

• The maximum number of users was already reached.

• The maximum number of users that are publishing a video was already reached.

• Could not read the client’s URL.

• Could not reach the client’s URL.

• The received request was rejected.

• There was no coverage for a specific destination number, or the end user could not be reached in time for the call.

• The server could not process the request because of an unexpected error.

• The server has definitive information that the end user does not exist within the domain specified in the Request-URI.

• The service is temporary unavailable.

• The server has a pending request from the same dialog.

• The specified destination number is incomplete.

• The destination address is currently unavailable.

• There has been a connection error.

• There has been an unknown WebRTC error.

• User has uninstalled the application on device or device cloud token expired.

• FCM responded with MismatchSenderId in response error field. Sender ID is a unique numerical value created when you create your Firebase project, available in the Cloud Messaging tab of the Firebase console`s Settings panel. The sender ID is used to identify each app server that can send messages to the client app. Check your application build configuration.

• Application with provided ApplicationCode is not found at Infobip Push service. Check your message target parameters.

• Registration with provided PushRegistrationId does not exist or has expired.

• Failed to send push notification. Cloud (FCM or APNS) responded with error while processing the request.

• Invalid cloud authentication data (Server Key). FCM responded with status 401 (Unauthorized). Check your Application configuration for Android on the Infobip web interface.

• Invalid certificate for APNS. Check your Application configuration for iOS on the Infobip web interface.

• Cloud type was disabled by client for the application. Request is targeted to registration with cloud type that was disabled by the client. Check your Application configuration on the Infobip web interface.

• Internal error. Please try again later and, if the problem persists, contact Support for further assistance.

• Invalid push payload data. Please contact Support for further assistance.

• Internal error. Please try again later and if problem persists, contact Support for further assistance.

• Push Cloud (FCM or APNS) is temporarily unavailable. Message is pending in retry.

• The sender name used is a part of real-time database which consists of forbidden domains/sender names/IPs that are categorized as spam-friendly.

• Emails are dropped due to spam content.

• Got Bounced message as sender possibly is being unsubscribed by recipient.

• Confirmation that email cannot be delivered as bounce message was reverted on the previous attempt.

• Recipient had previously bounced, unsubscribed, or complained of spam so we will not attempt delivery and the message will be dropped.

• Sender domain blocked. This generally happens when the sender domain exceeds the bounce threshold.

• Sender IP address is blocklisted, in which case the IP needs delisting.

• There are one or more validation errors present when forming the email gateway request. Contact support.

• There are one or more Handlebars syntax errors.

• End-user’s name is not a valid one — Either invalid characters or either invalid domain was used.

• End-user’s mailbox might be temporarily unavailable on the server.

• End-user’s mailbox has reached its full capacity defined on the server.

• End-user’s mailbox might have restricted access or simply does not exist on the server.

• End-user’s mailbox has reached its full capacity defined on the server.

• We received a bounced message (Non-delivery receipt). Possible reasons: Recipient email address does not exist; Domain name does not exist; Recipient email server has completely blocked delivery.

• Email has been undelivered even though the recipient’s email address is correct.

• Temporary Sending Error. The system will retry sending.

• Most commonly the issue lies within the domain used as the sender as it probably has not been registered yet.

• Sending email failed due to internal error.

• Email template cannot been found.

• Email contains invalid tracking parameters.

• Landing page placeholders size is exceeded.

• Email contains invalid custom headers.

• Email response parsing has failed.

• Email has been sent from an invalid sender.

• Email contains an invalid landing page.

• The preserved recipients are invalid.

• Email has expired due to an internal error.

• Application used to send the message does not exist. Make sure you have created the application and that you are using a valid application key.

• Receiving user does not exist. Check that the user has subscribed to the service and that you are using the correct user key.

• Receiving user has blocked communication.

• Invalid or unrecognized service access credentials. Make sure that you are using the correct access credentials issued by the service provider.

• Authentication was recognized, but not allowed. Check that your application is allowed to send messages, and that it is published or approved by the provider.

• The received request was incomplete or invalid (invalid parameter value, consecutive spaces etc.)

• Attempt to send a message with not allowed type.

• Message does not match the template. Check template arguments and text.

• Template used to send the message does not exist. Make sure the template is created and that you are using a valid template.

• User did not initiate a session and therefore cannot be contacted.

• There is a problem with your account. Contact our Support team for more information.

• Issue with WhatsApp deployment

• Provided media link has issues related to hosting.

• Issue with media upload to provider

• Issue with provided media metadata, content-type, size, etc.

• Message failed because there are restrictions (related to WhatsApp sender quality rating) on how many messages can be sent from this sender to unique end users during the rolling 24 hour period.

• Sending speed is too high

• Internal bad request

• Billing error on provider`s side (for now Viber only)

• Error displaying content on the end-user device

• Product functionality limited on the provider`s side.

• The media format is not supported.

• Data mismatch between local and remotely synced source.

• Message sent outsite of allowed time window.

• Unsupported mobile application version.

• Supplier API limit exhausted for specific message type.

• Message content has been blocked.

EC_USER_IDENTITY_CHANGED

• User identity has changed.

• Data mismatch between local and remotely synced source.

• The receiving user does not have a device that can receive this type of message.

• Internal service provider error.

• Connection to service provider timed out.

• Provider error in delivery report, non-retryable due to platform limitations.

• Unable to send message to this user (blocked or not followed).

• User is not following you.

• Text size over limit.

Код

Причина

Решение

12

Терминал неправильно подключен (через PC-3, а не PC-2). Если такая ошибка возникает только иногда, то проблема кроется в самом разъеме (например, поврежден).

Необходимо переподключить оборудование на PC-2. Если это уже сделано или не помогает, подключить через USB-порт. Если и это не помогает – обратиться к специалистам банка.

99

Нет связи с ПИН-падом (панелью ввода ПИН-кода). Возможно отошли контакты.

Проверить контакты, подходящие к ПИН-паду. Попробовать переподключить. Если не помогает, менять ПИН-пад или провода.

361

362

363

364

Все ошибки указывают на то, что чип карты не считывается. Проблема или в карте, или в ридере.

Попробовать вставить любую другую карту. Если чип не будет считан ни на одной из карт, значит проблема в ридере. Нужна диагностика.

403

Неверно введен ПИН-код.

Проверить правильность введения ПИН-кода. Повторить попытку. Если не помогает и клиент уверен, что он все делает правильно – обращаться в службу поддержки.

405

Вводимый ПИН-код заблокирован.

Клиент должен обратиться в службу поддержки или в ближайшее отделение Сбербанка.

444 507

Карта не активна (истек срок ее действия)

Использовать другую карту.

518

Неверная дата на терминале.

Установить верные данные.

521

Не хватает денег для совершения операции.

Использовать другую карту или пополнить счет.

572

Аналогична ошибкам 444 и 507 – истек срок действия платежного решения.

См.решение проблемы с ошибками 444 и 507.

574

579

Платежное средство заблокировано.

Использовать другую карту.

584

585

Период обслуживания платежного средства завершен.

Повторить попытку.

705

706

707

Ошибки аналогичны 574 и 579. Платежное средство заблокировано.

См.решение проблемы с ошибками 574 и 579.

708 709

Ошибки аналогичны 405. Вводимый ПИН-код заблокирован.

См.решение проблемы с ошибкой 405.

2000

Скорее всего клиент самостоятельно отменил операцию, нажав на кнопку отмены. В редких случаях проблема может быть в том, что терминал еще не провел сверку итогов и на данный момент не готов к работе.

Рекомендуется повторить операцию.

2002

Слишком долгий ввод ПИН-кода.

Достать карту из терминала и повторить попытку.

2004

2005 2006 2007 2405 2406 2407

Ошибки аналогичны 574 и 579. Платежное средство заблокировано.

См.решение проблемы с ошибками 574 и 579.

3001

Не хватает средств для пополнения карты.

Проверить, сколько денег вносилось и сколько должно быть перечислено на счет. Если данные совпадают – обращаться в службу поддержки.

3002

Предыдущее пополнение через терминал не было завершено.

Завершить операцию пополнения счета.

3019

3020

3021

Сервера Сбербанка находятся на обслуживании/ремонте/

регламентных работах.

Подождать окончания работ.

4100

Нет связи с банком.

Подождать или воспользоваться другим устройством.

4101 4102

Терминал не был проинкассирован.

Произвести инкассацию.

4103 4104

Обмен данными между терминалом и чипом карты был нарушен.

Повторить операцию еще раз. Если не получается – воспользоваться другим устройством.

4108

Номер карты был указан неверно (или был неверно прочитан).

Повторить операцию еще раз.

4110 4111 4112

Предупреждение о том, что нужна инкассация.

Провести инкассацию.

4113 4114

Превышен лимит операций.

Связаться со службой поддержки.

4115

Нельзя вводить карту вручную.

Воспользоваться другой картой.

4116

Последние 4 цифры номера карты введены неверно.

Проверить данные. Повторить попытку.

4117

ПИН-код не был введен

Ввести ПИН-код.

4119

Нет связи с банком.

Связаться со службой поддержки.

4120

ПИН-пад не получил код KLK.

Связаться со службой поддержки.

4121

Проблемы терминала на программном уровне.

Сообщить специалистам банка.

4122

Неверно произведена смена ключей.

Сообщить специалистам банка.

4123

4124

Нет ключей для рабочего сеанса.

Сообщить специалистам банка.

4125

Вместо чипа карты считана магнитная полоса.

Вставить карту в ридер для чипов.

4128

Неверный ключ KLK.

Сообщить специалистам банка.

4130

Забита память устройства.

Произвести сверку итогов.

4131

Проблема с ПИН-падом (неверная загрузка ПО).

Сообщить специалистам банка.

4132

Операция отменена.

Ошибка возникает тогда, когда карту достают из терминала быстрее, чем пройдет оплата. Необходимо повторить операцию.

4134

Давно не было сверки итогов.

Выполнить сверку итогов. Повторить операцию.

4136

Старая версия прошивки.

Нужно обновить прошивку.

4137

Ошибка в вводе ПИН-кода

Проверить данные. Повторить попытку.

4138

Номера карт получателя и отправителя средств совпадают.

Совершить платеж с другой карты.

4139

Нет нужного варианта связи для операции.

Произвести перенастройку терминала или связаться со службой поддержки.

4140

Неверный код или сумма операции.

Проверить и изменить данные. Повторить попытку.

4141

Программная ошибка. Нет нужного файла.

Повторить попытку. Если операция не проходит – связываться со службой поддержки.

4142

Не удается выполнить команду.

Повторить попытку. Если операция не проходит – связываться со службой поддержки.

4143

Старый СТОП-лист.

Обновить СТОП-лист.

4144 4145 4146 4147

Неправильный формат СТОП-листа.

Изменить формат СТОП-листа на правильный. Повторить попытку.

4148

Карта находится в СТОП-листе.

Использовать другую карту или убрать текущую из СТОП-листа.

4149

На платежном средстве нет фамилии клиента.

Использовать другую карту.

4150

Превышен лимит операций без связи с банком.

Обеспечить связь с банком.

4160

Биометрические данные считаны некорректно.

Повторить попытку. Если проблема повторяется – связываться со службой поддержки.

4161

Нет нужного файла для работы с биометрическими данными.

Установить нужный файл или связаться со службой поддержки.

4162 4163 4164

Ошибка в работе с сертификатом проверки биометрических данных.

Попробовать повторить попытку. Если проблема остается, связываться со службой поддержки банка.

4165 4166 4167

Биометрический сканер и терминал некорректно взаимодействуют.

Проверить подключение устройств и их синхронизацию. Если очевидных проблем нет – связываться со службой поддержки банка.

4168 4169

Ошибка в проверке отпечатков пальцев.

Повторить попытку. Если проблема сохраняется – связываться со службой поддержки.

4171

Отсутствует биометрическая криптограмма.

Установить требуемое ПО или обращаться в службу поддержки.

4202

Ошибка при загрузке данных.

Повторить попытку.

4203

При загрузке данных не был указан код для активации или он был указан неверно.

Проверить данные и указать правильный код активации.

4208

Ошибка при удаленной загрузке данных. На сервере нет нужного шаблона.

Связаться со службой поддержки.

4209

Ошибка при удаленной загрузке данных. На сервере нет доступа к базе данных.

Связаться со службой поддержки.

4211

Нет ключа №62 на терминале.

При невозможности самостоятельно решить проблему и загрузить нужный ключ — связаться со службой поддержки.

4300

Введены не все необходимые настройки/параметры.

Указать всю необходимую для работы устройства информацию. Если проблема сохраняется или непонятно, что именно нужно вносить, обращаться в поддержку банка.

4301

Невозможный тип операции.

Повторить попытку. Если проблема сохраняется, попробовать произвести любую другую аналогичную операцию. Если и в такой ситуации сохраняется проблема – обращаться в службу поддержки.

4302

Невозможный тип карты.

Попробовать другую карту. Если проблема актуальна с любой картой, возможно проблема в ПО или ридере. Рекомендуется обращаться в службу поддержки.

4303

Проблемы с передачей типа карты. Возможно неверные настройки устройства.

Обращаться в службу поддержки банка.

4305

Нужна более свежая библиотека данных.

Обновить библиотеку kernel.

4306

Нет нужной библиотеки kernel. Проблема обычно возникает после обновления библиотеки. Данные уже есть, но устройство их еще не успело обработать.

Повторить попытку через несколько минут. Если ошибка сохраняется, обращаться в службу поддержки.

4309

Нет данных для печати.

Распространенная ошибка, которая возникает при неправильной настройке или синхронизации баз данных, ПО, оборудования и так далее. Рекомендуется пошагово проверять каждый из элементов и его взаимодействие в комплексе.

4313

Несоответствие номеров карты.

Повторить попытку. Если проблема сохраняется – использовать другую карту.

4314

Устройство воспринимает отечественную карту как зарубежную.

Повторить попытку. Если проблема сохраняется – использовать другую карту.

4332

Не выполнена сверка итогов.

Выполнить сверку итогов.

4334

Карта не читается либо вышло время ожидания.

Повторить попытку. Если проблема сохраняется – использовать другую карту.

4335

Не введена сумма операции.

Ввести сумму и повторить попытку.

4336

Указан неправильный код валюты.

Указать правильный код валюты.

4339

Операцию невозможно выполнить для этой карты.

Использовать другую карту.

5002

Карта обладает дефектом: повреждена, изначально выпущена с дефектом и так далее.

Использовать другую карту.