Payment appears complete, but no receipt comes out of the printer. Customers may feel that the transaction failed. The counter employee must therefore assess the payment outcome first and resolve the document question afterwards. A missing printout is a visible problem, but does not itself show whether an amount was processed. Include this as a separate terminal pilot exercise.
Start with the right question
In a fictional store, the customer waits for paper proof while the employee sees an empty paper roll. The first question is not whether the customer should pay by card again. The employee checks the existing order and payment attempt through the agreed route. Technical status should come from verified provider information, with an amount and currency matching the right order. The printer supplies a document; it is not the source determining payment.
Record in the pilot which employee may assess that status and where unclear outcomes are followed up. The existing Yindle terminal component provides a foundation for retrieving and processing payment information. General printer integration, receipt reprints or digital replacements do not automatically follow. The store must establish its own device and communication capabilities. Give employees instructions only for features checked in that specific environment.
Help the customer through the available document route
Once the payment outcome is known, the employee can explain what happens to the document. A supported reprint or agreed digital message may be available. Present it as the store's actual route, not a universal Mollie terminal property. Check which details appear on the document and how customers can find the order later. Avoid a rushed screenshot containing unnecessary customer or device details as the default solution.
Use understandable wording: the printing issue is being investigated, and the existing payment will not be restarted because of it. Customers need no technical terminology. They need to know the confirmed outcome and which form of confirmation they will receive under the store's procedure. If payment remains unclear, it stays a separate open case with an owner. A promised receipt must not conceal that uncertainty.
Practise with a fictional printer failure
Create one test scenario where payment information is known but the document is missing, and another where both still need review. Have the employee explain the difference and choose the correct next action. Do not test arbitrary actions on real equipment during a customer payment. Use the agreed separate training setup and let device management determine how physical failures can be simulated responsibly. Training should test the decision process, not merely paper replacement.
Include in the instructions which reference support needs if the customer later calls only about the missing receipt. This keeps the document question linked to the same verified order and payment attempt.
Retain short instructions covering status checks, document options and the contact for equipment problems. Update them when the device or email route changes. For customer-facing explanations, you can explore online store customer service as a starting point. The terminal application's scope can be assessed with Yindle. The result is a counter team that calmly treats a missing receipt as a document question while continuing to assess the existing payment attempt correctly.