Connect the organiser’s payment account
This payment route connects the organisation to its own Mollie account. Payments are processed there rather than held by TixBeam for later settlement. Mollie’s verification, payment-method availability and payout conditions still apply. Keep account access restricted and connect it through actual organisation payment settings, not through a marketing example.
Check which Mollie account is connected to the organisation.
Separate test mode from real sales
Practise with test payments before taking real sales. Deliberately check the active environment and available payment methods afterwards. A successful test payment is not money received in your bank account. This demonstration only switches example states; it starts no Mollie payment, connection or verification and needs no credentials or customer data.
Check the payment environment before sharing the shop link.
Let confirmed payment determine ticket issuance
A visitor can return while payment processing is still underway. Opening the checkout or showing a banking screenshot does not establish that an order is paid. TixBeam uses the verified payment state and issues tickets after success. A failed or pending payment should not expose a paid QR ticket. The interactive journey illustrates that distinction.
Test successful, pending and failed payments in test mode.
Separate platform costs from provider settlement
Platform fees and Mollie charges are separate budget items. Applicable provider fees and payout timing depend on your agreement and payment methods. This page therefore promises neither a universal Mollie price nor a guaranteed bank settlement date. Reconcile order states with the provider’s administration and contact the responsible party when records differ.
Use the costs calculator with your own provider terms.