A physical payment terminal changes the context of a WooCommerce order. The customer may be in a showroom, a staff member may guide the payment, and the browser must follow status without deciding that an order is paid. Yindle Terminal Payments uses an authorized WooCommerce order as its basis and lets Mollie confirm the terminal payment.
Check the prerequisites
You need WooCommerce, a Mollie account, and at least one active Mollie POS device. Decide whether the gateway uses test or live data and where the API key comes from. Then bind the correct Mollie profile and terminal. A terminal can be physically available yet still belong to another profile or environment, so verify the complete combination in settings.
Put authorization before payment
A staff member or explicitly permitted showroom customer starts payment for an authorized order. The plugin first stores an immutable local payment attempt, then uses the same authenticated verification path for browser polling, webhooks, and recovery jobs. The order remains unpaid until Mollie verifies the payment. With split tender, the other portion must also be confirmed according to the operating profile.
Design showroom access carefully
Showroom customers can be allowed without an account, but access still requires an enabled, non-empty list of exact public IP addresses and authorization for the specific order. Check the real client IP and configure trusted proxies only for a hosting network you control. Keep the original browser session through payment. Cash confirmation also requires an employee ID and a confidential PIN; a guest needs the original checkout session as well.
Test every outcome
A simulated local provider does not prove live terminal or webhook delivery. Test on staging with a terminal that belongs to the selected Mollie environment. Check a card payment, a failed or abandoned attempt, retrying, delayed webhooks, browser refresh, guest access, and staff access. Also verify that a customer can read payment status after leaving the showroom, while starting again requires showroom access and order authorization.
Write the operating procedure
A terminal payment involves more than a settings screen. Describe who may start an order, who confirms a card or cash payment, how staff recognize an abandoned attempt , and when support should wait for a webhook. State that there is no default PIN and that the PIN remains confidential. Practise the case where the terminal or connection does not respond temporarily. A clear procedure prevents someone from manually marking an unverified order as paid.
Connect it to the customer journey afterwards
Terminal Payments is not part of the Yindle Commerce Bundle. For a guided online checkout, see Yindle Checkout ; for shared selections, Yindle Share Cart supports Classic and Cart Block. Read the Terminal Payments product page alongside the configuration documentation and schedule a live acceptance test with real network, Mollie, and terminal conditions before opening the gateway to customers.