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

# Default payment gateways — configuring payment providers per channel

> Set which payment gateway is used for each checkout channel — invoices, order forms, payment links, subscriptions, and calendars — and understand per-channel gateway support.

When you connect multiple payment gateways to the HoopAI Platform, you need to designate which gateway processes payments for each channel. Without a clear default assignment, the platform cannot determine which processor to route a given transaction through. This guide explains how to set defaults, understand capability differences across gateways, and manage gateway routing for each payment channel.

<Note>
  Stripe is strongly recommended as your primary gateway. It is the only processor that supports the full range of HoopAI payment features, including Apple Pay, Google Pay, ACH, Text-to-Pay, Tap to Pay, and Buy Now Pay Later options.
</Note>

***

## Why default gateways matter

Each payment channel in the HoopAI Platform — order forms, invoices, payment links, subscriptions, calendar bookings, and memberships — can be configured to route through a different gateway. This matters for two reasons:

1. **Feature availability differs by gateway.** Not every gateway supports every feature. PayPal, for example, works on order forms and subscriptions but cannot process invoice payments or payment links.
2. **Existing subscriptions stay on their original gateway.** If you change your default gateway, active subscriptions continue billing through the gateway they were created with. Only new subscriptions use the updated default.

***

## Gateway capability matrix

Use this table to understand which payment channels each gateway supports before assigning defaults.

| Channel                               | Stripe | PayPal | Authorize.net | NMI | Square | Adyen |
| ------------------------------------- | ------ | ------ | ------------- | --- | ------ | ----- |
| Order forms                           | Yes    | Yes    | Yes           | Yes | Yes    | Yes   |
| Invoices                              | Yes    | No     | Yes           | Yes | Yes    | Yes   |
| Payment links                         | Yes    | No     | Yes           | No  | No     | —     |
| Subscriptions                         | Yes    | Yes    | Yes           | Yes | Yes    | —     |
| Calendar bookings                     | Yes    | No     | Yes           | No  | Yes    | —     |
| Memberships                           | Yes    | No     | Yes           | No  | —      | —     |
| Apple Pay / Google Pay                | Yes    | No     | No            | No  | No     | No    |
| Tap to Pay (iPhone)                   | Yes    | No     | No            | No  | No     | No    |
| Text-to-Pay                           | Yes    | No     | No            | No  | No     | No    |
| Buy Now Pay Later (Klarna / Afterpay) | Yes    | No     | No            | No  | No     | No    |
| ACH / SEPA bank transfers             | Yes    | No     | No            | No  | No     | No    |

<Warning>
  A dash (—) in the table above means the gateway has no defined integration for that channel. Attempting to use an unsupported combination may result in the payment option not appearing to customers or transactions failing silently. Always test your gateway configuration in test mode before going live.
</Warning>

***

## Navigating to gateway settings

<Steps>
  <Step title="Open Payment Integrations">
    Go to **Payments → Payment Integrations** in the HoopAI web app. Click the **Integrations** option in the upper-right of the Payments tab if the Payment Integrations page is not already open.
  </Step>

  <Step title="Review connected gateways">
    The Payment Integrations screen shows:

    * **Default provider** — the gateway currently set as the primary default
    * **Connected providers** — additional gateways with a **Manage** button
    * **Available providers** — gateways not yet connected
  </Step>

  <Step title="Open gateway management">
    Click **Manage** on any connected gateway to access its settings, including the option to set it as the default for specific channels.
  </Step>
</Steps>

***

## Setting the default gateway for a channel

<Steps>
  <Step title="Open the gateway you want to configure">
    From **Payments → Payment Integrations**, click **Manage** on the gateway you want to designate as the default.
  </Step>

  <Step title="Find the Set as Default option">
    For NMI, Authorize.net, and Square: a **Set as Default** toggle or button is available directly in the management screen. Click it to make that gateway the default for the channels it supports.

    For Stripe: Stripe is automatically the default for all channels it supports. If another gateway is also connected and supports the same channel, you can choose which to use from the channel configuration screen.
  </Step>

  <Step title="Configure by channel">
    For more granular control, go to **Payments → Payment Integrations → Configure by channel**. This screen lets you assign a specific gateway to each individual channel (order forms, invoices, payment links, in-person, subscriptions, calendar bookings).
  </Step>

  <Step title="Save your changes">
    Click **Save**. The selected gateway will now process all new payments for the channels you assigned it to.
  </Step>
</Steps>

<Note>
  Only one gateway can be the default at a time for any given channel where gateways overlap. If you have both Stripe and Authorize.net connected, and both support invoices, you must designate one as the default for that channel.
</Note>

***

## PayPal alongside other gateways

PayPal can run simultaneously with Stripe, NMI, or Authorize.net on order forms. When configured this way:

* Customers see a **Pay with PayPal** button as an additional payment option alongside the standard card fields
* PayPal handles the PayPal-specific checkout flow and returns a confirmation to the platform
* The primary gateway (Stripe, NMI, or Authorize.net) continues to process all card transactions

<Warning>
  PayPal is not available for invoices or payment links — only for order forms and subscriptions. If you send an invoice to a customer who prefers to pay via PayPal, they will not have that option. Consider creating a payment link connected to an order form product if you need to offer PayPal on a per-transaction basis.
</Warning>

***

## NMI and Authorize.net notes

Both NMI and Authorize.net are full-featured gateways but have specific limitations compared to Stripe:

* **Calendar bookings** — setting NMI or Authorize.net as the default does not automatically apply them to calendar payment bookings. Calendar payment settings are configured separately within each calendar's settings.
* **Membership payments** — NMI supports invoice and subscription payments, but membership-specific billing within the platform's membership module may default to Stripe. Verify your membership payment configuration after switching defaults.
* **Apple Pay and Google Pay** — neither NMI nor Authorize.net supports digital wallet payments. If you want to offer Apple Pay or Google Pay, Stripe must be your gateway for those channels.

***

## Setting gateway for calendar bookings

Calendar payment gateway settings are independent of the global default gateway configuration.

<Steps>
  <Step title="Open the calendar">
    Go to **Calendars** and click on the specific calendar you want to configure.
  </Step>

  <Step title="Open Forms and Payments settings">
    Inside the calendar settings, navigate to **Forms & Payments**.
  </Step>

  <Step title="Enable Accept Payments">
    Toggle on **Accept Payments** for this calendar.
  </Step>

  <Step title="Select a gateway">
    From the gateway dropdown, choose **Stripe**, **Square**, or **Authorize.net** for this calendar. The available options depend on which gateways are connected to your account.
  </Step>

  <Step title="Save">
    Click **Save**. Appointment bookings on this calendar will now charge through the selected gateway.
  </Step>
</Steps>

***

## Setting gateway for invoices

Invoice payment gateway is determined by the gateway configured in your Payment Integrations as the default for the invoice channel. It cannot be overridden on a per-invoice basis.

If you need different gateways for different invoice types, you can achieve this indirectly by:

* Using payment links (which have their own gateway assignment) instead of invoices for transactions where you want a specific gateway
* Configuring separate accounts if your use case genuinely requires completely separate gateway routing

***

## Testing your gateway setup

Before going live with a new or changed gateway default, always verify the setup with a test transaction.

<Steps>
  <Step title="Enable test mode">
    In **Payments → Payment Integrations**, toggle the **Test Mode** switch on for the gateway you want to test. Stripe uses Stripe test keys; other gateways use their own sandbox credentials.
  </Step>

  <Step title="Process a test payment">
    Navigate to the channel you configured (create a test order, send a test invoice, or open a payment link) and complete a payment using the gateway's test card numbers.

    For Stripe test cards: `4242 4242 4242 4242` with any future expiry and any CVC.
  </Step>

  <Step title="Verify the transaction">
    Check **Payments → Transactions** to confirm the test transaction was recorded and shows the correct gateway in the source column.
  </Step>

  <Step title="Switch to live mode">
    Once you have confirmed the gateway is working correctly, disable test mode and switch to live credentials. Remove all test transactions from your records if needed.
  </Step>
</Steps>

<Tip>
  Run test transactions for every channel you plan to use — do not assume that because Stripe works on order forms it will automatically work on payment links or calendar bookings without individual verification.
</Tip>

***

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Can I use two gateways at the same time?">
    Yes, with limitations. Stripe and PayPal can run simultaneously on order forms — customers see both options at checkout. For other gateway combinations, one must be designated as the default and the other as secondary. For channels where only one gateway is supported at a time, you must choose one.
  </Accordion>

  <Accordion title="If I switch my default gateway, does it affect existing subscriptions?">
    No. Existing subscriptions continue to bill through the gateway they were originally created with. Only new subscriptions created after the change will use the new default gateway. To migrate existing subscriptions to a new gateway, customers would need to re-subscribe through the new payment flow.
  </Accordion>

  <Accordion title="Can I set different gateways for different products?">
    Not currently. The default gateway applies account-wide per channel, not per product. If you need different gateways for different products, consider using separate payment links for each product and assigning different gateways to each link through the channel configuration.
  </Accordion>

  <Accordion title="Why can't I select NMI for payment links?">
    NMI does not support the standalone payment link channel. Use Stripe or Authorize.net for payment links. If you need to use NMI for a specific product, create an order form in a funnel or website — NMI is fully supported on order forms.
  </Accordion>

  <Accordion title="What gateway is used for calendar payment bookings?">
    Calendar payment gateway is set per calendar, not by the global default. Go to **Calendars → \[your calendar] → Settings → Forms & Payments → Accept Payments** and choose Stripe, Square, or Authorize.net from the dropdown.
  </Accordion>

  <Accordion title="Can I offer PayPal on invoices?">
    No. PayPal is not supported for invoice payments. Only Stripe, NMI, Authorize.net, Square, and Adyen can process invoice payments. If a customer specifically needs to pay via PayPal, create a product in your catalog and send them a payment link connected to an order form, where PayPal is available as an option.
  </Accordion>

  <Accordion title="What happens if no default gateway is set?">
    If you have connected gateways but have not designated a default, the platform may fall back to Stripe (if connected) or prompt an error when a customer attempts to pay. Always confirm a default is set for every channel you use by reviewing the Configure by Channel screen.
  </Accordion>

  <Accordion title="Does switching gateways affect my Stripe Connect configuration?">
    No. Switching which gateway is the default for a channel does not affect your underlying Stripe Connect setup or Stripe account configuration. Your Stripe account remains connected and can be reassigned as the default at any time.
  </Accordion>
</AccordionGroup>