> For the complete documentation index, see [llms.txt](https://guide.geyser.fund/geyser-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.geyser.fund/geyser-docs/product-guides/contribute-on-geyser/contribute-with-fiat.md).

# Contribute with Fiat

Geyser supports two fiat funding options:

* **Stripe**\
  Fiat payments go straight into the project creator’s Stripe account. No Bitcoin swap.
* **Banxa**\
  Contributors use fiat to buy Bitcoin, which is sent directly to the project.

***

## Stripe 

For projects that have configured a Stripe account, the payment experience is seamless. 

How it works:

Once you click Contribute and "**Continue with Credit Card ot Bank Transfer"** you simply add your credit card details, and make the payment. No KYC required, no limits. It just works!

***

## Banxa

For projects that did not configure Stripe, you can pay with credit card via the Banxa service that allows you to buy Bitcoin and instantly send it to the project.

**How it works:**

Once you click Contribute and "**Continue with Credit Card ot Bank Transfer"** you will be prompted to select the currency and then finalize the flow on Banxa. You may be required to undergo document verification

**What happens behind the scenes:**

* Your fiat payment is processed by Banxa
* Banxa converts the fiat into Bitcoin
* The Bitcoin is sent immediately to the project
* The project creator receives Bitcoin, not fiat
* All funds end up as Bitcoin.

**Fees:**

Expect roughly an additional \~3.5% fee for the Banxa. These fees cover payment processing, conversion, and compliance.

**Verification and KYC**

Banxa may request verification depending on your location.

* **Europe and the US**\
  Light verification such as name and address
* **Other regions**\
  ID verification may be required

If verification is required, Banxa will prompt you during checkout.


---

# 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://guide.geyser.fund/geyser-docs/product-guides/contribute-on-geyser/contribute-with-fiat.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.