> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/getting-started/billing-and-payments.md).
# Billing and Payments
To avoid breaking the bank, **Pump is 100% free.** Instead, we (as a cloud reseller) make our tiny margin from AWS, GCP, and Azure! Pump is a **net positive** by helping you save money on your cloud costs for free.
As soon as you join Pump, your cloud usage (AWS/GCP/Azure) starts being billed to us. Our finance team sends you an invoice based on your cloud usage data on **the third day of every month.** Two days later, if you're on autopay, we'll charge your preferred payment method.
To Surface Invoices:
1. Go to your organization's [**invoice dashboard**](https://app.pump.co/invoices).
2. View the outstanding invoices, and to select a specific invoice, select "**View\_pdf**."
**Adding a Payment Method**
1. Go to your organization's [**billing preferences**](https://app.pump.co/settings/billing).
2. Click "Add payment method"
**Payment Methods**
Invoices to Pump can be paid with a bank account via [GoCardless](https://gocardless.com/), wire transfer via ACH, SWIFT, or Credit Card. We support direct debit for the US, UK, the Euro zone, Australia, Canada and 30 other countries. TLDR: We support payment methods for customers across the globe!
We do offer customers the option to pay via credit card. For credit card, we add a 2.9% fee since we are a free product and are charged a 2.9% fee for credit card.
Please include your **Company ID** (it can be found [**here**](https://app.pump.co/settings/company)) and **Month(s)** you are paying for in the memo line. Once paid, feel free to confirm with our accounts recievable team () or find the updated invoice state [**here**](https://app.pump.co/invoices).
Find payment instructions here:
---
# 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.pump.co/getting-started/billing-and-payments.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.
