> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/ecommerce-launch-mega-checklist/payment.md). # Payment * Have you negotiated rates with your chosen credit card provider (if you have existing volume)? Have these been applied to your account? * Have you integrated at least one credit/debit card processor, PayPal, then any industry specific payment processors you need. *Pakk sites - Stripe, PayPal, Paytriot and Viva Wallet are built in and mostly only require you to enter your account ID and enable. You might also need to set up webhook notifications.* * Have you tested your integration well? Have you tried both payment success and failure scenarios to see how your system handles them? Does the information flow through to your customer service team. *Pakk sites - for our built-in payment processors we record detailed transaction meta-data which can be inspected in the admin panel.* * Have you considered fraud? What tools do your payment processors provide for detecting fraud? Are you using them? What are you going to do internally to minimise fraud? *Pakk sites - use colour codes or 'stages' to mark orders that need to be reviewed.* * Do you understand the post-payment flow? How often is money paid to you? To which account? How is it batched up? How can you reconcile it? * Do you also want to offer 'offline' payment methods such as 'bank transfer'? If you set them up, make sure you provide the information the customer needs to make the payment. *Pakk sites - create and customise as many manual payment methods as you need.* --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://academy.pakk.io/ecommerce-launch-mega-checklist/payment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.