Hypersoft Pay Communication

If payments cannot be made, communication is the most important thing to clarify. The first stage is the alignment of expectations based on the topics described at Technical and commercial risks. In addition, it depends on whether the POS system waits for the payment or whether the payments are executed in the background.

Then there are a number of terminal messages, which the payment terminal displays to the operator or the customer. We have optimised these as much as possible but they are very general in terms of the source of information. Thus, there are actually many different reasons for the message "Payment refused". Did you know that a low battery level at payment terminals can be the reason for a payment order rejection? For this reason, Hypersoft Pay powered by Adyen evaluates further data centre information in real time and additionally displays this as data centre information.

Data centre information

Data centre information is displayed in Hypersoft Pay powered by Adyen in addition to the terminal messages. If a payment is cancelled, additional information is logged in the log file. Not everything is clear-cut. Unique and already known information is additionally displayed at the POS.

 

  • Payment cancelled via the cancel key on the terminal/ Text: Payment cancelled via cancel key on the terminal

  • Cancellation by the cash register due to timeout / Text: Timeout for payment reached, payment process cancelled by the cash register.

  • Timeout by terminal because no card was presented/ Text: Timeout, card not presented

  • Payment rejected online by Adyen (error code 214) / Text: Payment rejected by provider

  • Sending a payment if a message dialogue is still displayed on the terminal (Android terminals)/ Text: Execution not possible, please answer the query on the terminal first.

  • Payment is not executed because the battery level is too low/ Text: Battery level too low, payment cannot be executed

 

The state of charge of the battery is additionally entered in the transaction log. Example:

27.10.2021 - 11:20:48 [BATTERY] => 85%

27.10.2021 - 11:20:48 [PAYMENT] => OUTFILE ARRIVED **SUCCESS**

27.10.2021 - 11:20:48 [PAYMENT] => Function:00

27.10.2021 - 11:20:48 [PAYMENT] => AMOUNT:1490

Example decoded additional information:

27.10.2021 - 10:22:03 [ADDITIONAL] => { "additionalData": { "backendGiftcardIndicator": "false", "batteryLevel": "92%", "cardScheme": "wechatpay_pos", "cardType": "wechatpay_pos", "giftcardIndicator": "false", "iso8601TxDate": "2021-10-27T08:21:28.0000000+0000", "merchantReference": "1700237285", "mid": "1", "offline": "false", "paymentMethod": "wechatpay_pos", "paymentMethodVariant": "wechatpay_pos", "posAmountCashbackValue": "0", "posAmountGratuityValue": "0", "posAuthAmountCurrency": "EUR", "posAuthAmountValue": "1490", "posEntryMode": "BAR", "posOriginalAmountValue": "1490", "posadditionalamounts.originalAmountCurrency": "EUR", "posadditionalamounts.originalAmountValue": "1490", "pspReference": "861635322911581E", "tid": "47299593", "transactionReferenceNumber": "861635322911581E", "transactionType": "GOODS_SERVICES", "txdate": "27-10-2021", "txtime": "10:21:28" }, "message": "108 Shopper cancelled tx", "refusalReason": "108 Shopper cancelled tx" }

Hypersoft Pay@Table Messages

With Hypersoft Pay@Table, transaction closings can be made directly at the payment terminal. If settings are not correct, this is reported to the operator directly to the mobile Hypersoft Pay Adyen Terminals.

Example Error messages directly on the Saturn F2...

Additional messages appear if the settings for Pay@Table are incorrect.

Note title Note text

Cause
NoCOO is Inactive To use this function, you must activate NoCOO in your system. This must be corrected in order to be able to settle. This message appears if NoCOO is not activated, because Pay@Table only works with NoCOO.
Data directory wrong The data directory of the ward and the subsystem are not identical. This must be corrected in order to be able to settle.

If the NoCOO subsystem has been assigned a different data exchange directory than the cashier station that initiated the payment order, Pay@Table will not work. See also NoCOO Onboarding at the POS.
Form wrong The NoCOO short document is not set up as a form for this function. This must be corrected in order to be able to settle. The NoCOO short receipt must be set up as form 1 otherwise the terminal cannot print a receipt.
BZV settings You must activate the "Do not wait for Quick-Service" and "Do not wait for Full-Service" functions to receive a bill receipt at the terminal. This must be corrected in order to be able to settle. The current settings are not compatible with the intended use Pay@Table.
No authorisation Unfortunately, you are not authorised to work at the payment terminal. Operators can be blocked for cashless payment.
Operator-Z You have already made a Operator-Z trade and now you can no longer make payments. You can use the programme to block operators (after accounting).
Table is used The table has been used by operators "Bedienername" since "Uhrzeit" and is not available. The process is open somewhere. If there is an error, wait a few minutes. In an absolute emergency, restart Windows at the checkout station that "Blocks" the operation.
Time recording Please log in to the time registration first to make payments at the terminal. You can use the Compulsory registration for time recording. This then also applies here.

Back to the parent page: Hypersoft Pay Adyen Terminals