> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/payment-methods/pay-by-bank/merchant-best-practices.md). # Merchant Best Practices Following these recommendations will help you build a reliable, secure, and user-friendly Pay by Bank integration. #### Order Processing and Notifications * Fulfil orders only after receiving the **Webhook (also referred to as callback notifications)** confirming the Settled status. Never fulfil immediately after the customer’s browser returns. * Keep orders in a pending state while the customer completes authentication, and wait for the final status of payments that remain Initialized. * Ensure Webhook processing is idempotent. Duplicate notifications must not create duplicate orders or refunds. #### Customer Experience * Clearly explain that the customer will be redirected to their selected bank, and that authentication methods may vary between banks. * Provide clear, non-technical messages if the customer cancels or abandons the payment, and make it easy to retry or choose another payment method. * Offer alternative payment methods if Pay by Bank or a specific bank is unavailable. #### Monitoring and Reconciliation * Reconcile payments daily using stored payment references. * Monitor Webhook delivery, failed and cancelled payments, and investigate payments that remain Initialized longer than expected. #### Security * Always use HTTPS and protect your API credentials. * Restrict access to payment administration functions, including refund initiation. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ecommerce.seb.ee/payment-methods/pay-by-bank/merchant-best-practices.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.