> 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/aws/using-pump/payments.md). # Payments 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 US and a few international countries at the moment. 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 3% fee since we are a free product and are charged a 3% fee for credit card. SWIFT Code: CMFGUS33 Account Number: 8305310325 Bank Name: Community Federal Savings Bank Bank Address: , US SWIFT **Beneficiary Name:** Pump Billing Inc **Beneficiary Address:** 1390 Market St, San Francisco, CA 94102 Go to [**this page to see payment instructuions**](/getting-started/billing-and-payments/supported-payment-methods.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.pump.co/aws/using-pump/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.