> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/getting-started/account-set-up-and-configuration/getting-my-customers-started-on-alternative-payments.md).

# Getting my Customers Started on Alternative Payments

**Getting started with Alternative Payments is a straightforward process for your customers. Here's how.**

***

Alternative Payments is extremely easy to use for your customers and for you. Once you send your billing link to your customers, they can log in and start making payments right away.

### 1. Create the customer in your dashboard

Before your customer can access the payment portal, you need to create a customer record in your Partner Dashboard (or sync them from your connected PSA/accounting integration).

### 2. Send your billing link

Once the customer exists in the system, send them your billing link.

### 3. Customer completes setup and pays

They will be asked to confirm their business details, link their bank account or credit card, and select an invoice to pay.

{% hint style="info" %}
**Note:** Credit card processing fees are passed through to the customer by default. Your specific rates may vary based on your plan.
{% endhint %}

Read more: [Settling an invoice: A step-by-step guide to making easy payments through Alternative](/end-customer-faqs/end-customer-faqs/making-invoice-payments.md)


---

# 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://help.alternativepayments.io/getting-started/account-set-up-and-configuration/getting-my-customers-started-on-alternative-payments.md?ask=<question>&goal=<user_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.