> 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/launch-a-project/enable-fiat-contributions.md).

# Enable Fiat Contributions

Geyser allows contributors to fund your project using traditional payment methods like credit cards or bank transfers, and to support you with recurring contributions.

There are two ways this can happen:

* **Stripe** - contributors pay in fiat and the money goes directly to your bank account (RECOMMENDED)
* **Banxa** - contributors buy Bitcoin with fiat and that Bitcoin is sent to your project

If you configure Stripe, contributors will use the Stripe flow to pay.\
If you do not configure Stripe, Banxa is enabled automatically.

***

#### Recurring Contributions

Recurring contributions allow supporters to contribute to your project on a regular basis instead of making a one-time payment.

* **Stripe** - fully automated recurring payments. Contributors subscribe once and payments repeat automatically.
* **Banxa** - recurring contributions are manual. Contributors receive monthly reminders and must complete the payment each time.

To enable automated recurring contributions, you must configure Stripe.

***

#### Stripe Payments (recommended)

Stripe creates the simplest and fastest experience for contributors. Payments are processed as a normal fiat transaction and the funds go directly to your Stripe account and bank account.

There is no Bitcoin conversion, no swap, and the checkout experience is very familiar for anyone paying with a credit card.

You can configure Stripe in two places:

* during the project creation flow
* from Project Dashboard → Payment Settings → Configure Stripe

Once Stripe is connected, contributors will see the Stripe checkout when they choose to pay with credit card or bank transfer.

Contributed funds go directly into your own bank account that you set up in the Stripe configuration.

**Fees:**\
Stripe has a processing fee of 2.9% + $0.30

**Verification:**\
There is no KYC required for contributors and no Bitcoin involved in the transaction.\
However, creators must configure their Stripe account and undergo ID verification with Stripe.

***

#### Banxa payments

If Stripe is not configured, Geyser automatically enables Banxa.

Banxa allows contributors to buy Bitcoin using fiat and send it directly to your project.

From the contributor's perspective:

* They click Contribute
* They select Continue with Credit Card or Bank Transfer
* They choose their currency
* They complete the purchase through Banxa

Behind the scenes:

* Banxa processes the fiat payment
* Banxa converts the fiat into Bitcoin
* The Bitcoin is immediately sent to the project

This means you receive Bitcoin, not fiat.

**Fees:**\
Banxa fee is \~3.5%

**Verification:**\
Banxa does not require verification for creators (receivers), but may require verification from contributors depending on their location and transaction size.

For contributors in the US or Europe, this is often light verification like name and address. In other regions, ID verification may be required.

If verification is necessary, Banxa will prompt the contributor 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/launch-a-project/enable-fiat-contributions.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.