> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/customers-and-sales/credit-management/payment-methods-and-flows.md).

# Payment Methods and Flows

You will have set up a number of ‘Payment Methods’ within your Pakk account. Each Payment Method has an associated ‘Flow’. The main flows are:

* Credit card (via Stripe)
* PayPal
* Invoice

For example, you may have set up a Payment Method that you have called ‘Bank Transfer’. Since this is a ‘post-payment’ type method (I.e. you have to wait for payment to come in), this would be an ‘Invoice’ flow type Payment Method. Any Payment Method that allows the customer to pay after ordering (even if its just a few hours or days) has an invoice flow.

To make a Payment Method available on your store or stores: 

`Payment Method > Web > check Web Enabled and choose which sites`

By default, any payment method you make available online will be available to all customers. For example, if you create a ‘Credit Cart’ method and make it available on a site, all customers will be able to use that method. Likewise, if you make a method called ‘Invoice’ (logically with an invoice flow), this would, by default, be available to all customers.

However, it’s unlikely that you want to offer credit to all customers, so you will probably want to mark any ‘invoice flow’ Payment Methods as ‘Customer Restricted’. This means that customers will only be able to see or use that Payment Method if they have been specifically allowed.

To specifically allow a customer to use a Payment Method: 

`Customer > Credit Management > Allowed Payment Methods > Add any Payment Methods you want to allow`

In summary, by giving a customer access to a ‘restricted’ payment method with invoice flow, you are granting them the ability to pay after ordering (i.e. giving them credit).


---

# 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://docs.pakk.io/customers-and-sales/credit-management/payment-methods-and-flows.md?ask=<question>&goal=<endgoal>
```

`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.