> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluz.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Bring your own MID

> Connect a merchant account you already have with a supported gateway to your Fluz app. Your customers add cards, you run transactions, and funds settle to you as they do today.

If you already have a merchant account (MID) with one of the gateways below, you can use it in your Fluz app. You bring the MID. We connect it to your app as its payment gateway. Your customers add their cards, you run transactions through Fluz on that MID, and the funds settle to you the same way they do today.

You keep your gateway relationship, your MID and your settlement account. Nothing changes on the gateway side.

## How it works

**1. Bring your MID**

Send us the details for your gateway. Each gateway page below lists exactly what to include. You never email your API credentials. We reply with a secure way to share them.

**2. We connect it to your Fluz app**

We board your MID in Fluz and assign it as the payment gateway on your application, in staging, production or both. This takes 2–5 business days for most gateways.

**3. Add cards and run transactions**

Your customers add their cards in your app. The payments your app runs on their behalf process through your MID, with your descriptor on their card statements.

**4. Funds settle to you**

Your gateway settles the funds to your account on its normal schedule, just as it does today.

## Supported gateways

> [card] [Stripe](https://docs.fluz.app/connectors/payments/stripe.md)
>
> 2–5 business days

> [card] [Braintree](https://docs.fluz.app/connectors/payments/braintree.md)
>
> 2–5 business days

> [card] [Authorize.net](https://docs.fluz.app/connectors/payments/authorize-net.md)
>
> 2–5 business days

> [card] [Finix](https://docs.fluz.app/connectors/payments/finix.md)
>
> 2–5 business days

> [card] [Sola / Cardknox](https://docs.fluz.app/connectors/payments/sola.md)
>
> 2–5 business days

> [card] [PayArc](https://docs.fluz.app/connectors/payments/payarc.md)
>
> 2–5 business days

> [card] [Highnote](https://docs.fluz.app/connectors/payments/highnote.md)
>
> 2–5 business days

> [card] [Worldpay](https://docs.fluz.app/connectors/payments/world-pay.md)
>
> On request

> [card] [TSYS](https://docs.fluz.app/connectors/payments/tsys.md)
>
> On request

> [card] [Checkout.com](https://docs.fluz.app/connectors/payments/checkout.md)
>
> On request

> [card] [TabaPay](https://docs.fluz.app/connectors/payments/tabapay.md)
>
> On request

For gateways marked **On request**, we confirm the timeline when we review your request.

## Before you request

* **Fill in Marketed URLs.** List every website or app where you offer Fluz services in the **Marketed URLs** section of your app's settings, on both your staging and production apps. We can't connect a MID to an app that leaves it blank.
* **Decide which environments you need.** We can connect your MID in staging, production or both. For both, have your gateway's test credentials for staging and live credentials for production.
* **Read the payment collection requirements.** Every app that takes payments from its customers goes through the same review. See [Collect payments from your customers](https://docs.fluz.app/build-a-platform.md#collect-payments-from-your-customers).

> [!NOTE]
>
> **Seeing `PG-0003` on a customer's payment?** Calls return `PG-0003` (`NoPaymentGatewaysAvailable`) until a payment gateway is assigned to your app. Retry the same call once we confirm your MID is connected.

> [card] [Request a BYO MID](mailto:platforms@fluz.app?subject=BYO%20MID%20request)
>
> Fill out the request form, or email [platforms@fluz.app](mailto:platforms@fluz.app) until the form is available. Include the details listed on your gateway's page, without your API credentials.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.