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

# Forte

> How to configure Forte for ACH and credit card payments in Nexudus.

## Overview

The **Forte ACH** gateway lets customers pay via ACH bank transfer (eCheck) directly from their bank account. Payments are processed securely through Forte's payment platform.

To take card payments through Forte as well, add Forte as a card gateway. See [Card gateways (Spreedly)](/platform/finance/payment-gateways/spreedly).

Forte is available in two scenarios:

* **Plan signup checkout** — Customers can select Forte when signing up for a membership plan
* **Pay via invoice** — Customers who receive an invoice can pay it using Forte from **My Invoices** in the Members Portal

## Features

| Feature | Supported |
| - | - |
| Card payments | Through the separate Forte card gateway |
| ACH / eCheck payments | Yes |
| Recurring payments | Yes |
| 3D Secure | No |
| Sandbox mode | Yes |

## Configuration Parameters

To configure Forte, go to **Settings → Billing and payments → Payments and currency → Payment methods** and select **Forte ACH**.

### Required Settings

| Setting | Description |
| - | - |
| **Enable ACH bank payments** | Master switch to enable or disable ACH/eCheck payments via Forte. |
| **Account ID** | Your Forte account ID, digits only. Nexudus adds the `act_` prefix. |
| **Location ID** | Your Forte location ID, digits only. Nexudus adds the `loc_` prefix. |
| **API Access ID (REST)** | The API Access ID of a set of Forte REST API credentials. Used for recurring ACH payments, payment status checks and Forte payments in the Members Portal. |
| **API Secure Key (REST)** | The API Secure Key created with that API Access ID. |

### Previous Members Portal only

The previous version of the Members Portal uses Forte's older Checkout v1, which signs payments with a different pair of credentials. Fill these in only while customers still pay through that version.

| Setting | Description |
| - | - |
| **API Login ID (Virtual Terminal, previous portal only)** | The API Login ID from Forte Virtual Terminal. |
| **Secure Transaction Key (Virtual Terminal, previous portal only)** | The Secure Transaction Key paired with that API Login ID. |
| **Enable for credit/debit card payments** | Offers Forte card payments on invoices in the previous Members Portal. In the current Members Portal, take Forte card payments through the [Forte card gateway](/platform/finance/payment-gateways/spreedly). |

### Optional Settings

| Setting | Description |
| - | - |
| **Use test servers** | Enable sandbox mode for testing with Forte's sandbox environment. |

## Obtaining Forte Credentials

Forte issues two different kinds of credentials, and Nexudus uses each for a different job:

| Credential | Where to find it | Used for |
| - | - | - |
| **Account ID** and **Location ID** | In [Dex](https://dex.forte.net), your organization and location IDs. Enter the digits only, without the prefix. | Everything |
| **API Access ID (REST)** and **API Secure Key (REST)** | In Dex, under **Developer > API Credentials**. Select **Create**, name the credentials and copy both values. See [Working with API Credentials](https://dexdocs.forte.net/merchant/content/admin/working_with_api_keys.htm). | Recurring ACH payments, payment status checks and Forte payments in the Members Portal |
| **API Login ID (Virtual Terminal)** and **Secure Transaction Key (Virtual Terminal)** | In Forte Virtual Terminal, under **Gateway Settings > Gateway Key** | The previous version of the Members Portal only |

<Warning>The two pairs are not interchangeable. Forte rejects a Virtual Terminal API Login ID where an API Access ID is expected, and the other way round. A Virtual Terminal API Login ID is much shorter (typically 10 characters) than an API Access ID (32 characters), so a short value in **API Access ID (REST)** is a sign the pairs have been swapped.</Warning>

<Note>Dex shows the API Secure Key only once, when you create the credentials. If you lose it, regenerate it in Dex and update it in Nexudus.</Note>

### Moving to the new Members Portal

The new Members Portal uses the same **API Access ID (REST)** and **API Secure Key (REST)** as recurring ACH payments. If you already collect recurring ACH payments through Nexudus, these are filled in and there is nothing to change. Keep the Virtual Terminal credentials only while customers still pay through the previous version of the Members Portal.

## Setting up Forte

1. Create an account with Forte at [forte.net](https://www.forte.net)
2. Complete the Forte onboarding process to receive your credentials
3. Create a set of API credentials in Dex and note your account and location IDs, as described above
4. In Nexudus, go to **Settings → Billing and payments → Payments and currency → Payment methods**
5. Select **Forte ACH** and fill in your credentials:
   * Account ID and Location ID
   * API Access ID (REST) and API Secure Key (REST)
   * API Login ID (Virtual Terminal) and Secure Transaction Key (Virtual Terminal), only if customers still pay through the previous version of the Members Portal
6. Enable "Enable ACH bank payments" to activate the gateway
7. Toggle "Use test servers" for sandbox testing before going live

### How Forte works in checkout

1. When a customer selects Forte during checkout, Nexudus signs the payment details with your API Secure Key
2. Forte Checkout v2 is loaded from `https://checkout.forte.net/v2/js`
3. A payment button is rendered with Forte data attributes containing your API Access ID and the signed payment details
4. When clicked, the customer is presented with Forte's secure payment interface
5. After payment, Forte returns the result to Nexudus, which checks its signature and sends the customer to the payment complete page
6. Invoice status changes to "Processing" until the payment clears.
7. Customer and payment tokens are stored for recurring billing

<Note>The Forte integration supports both plan signup checkout and booking/product/event checkout. Customer tokens are stored automatically to enable recurring payments without re-authentication.</Note>

### Sandbox testing

When sandbox mode is enabled:

* Forte Checkout is loaded from `https://sandbox.forte.net/checkout/v2/js` instead of the production endpoint
* All API calls are routed to Forte's sandbox environment
* Use the account ID, location ID and API credentials from your Forte sandbox account

## Troubleshooting

* **Payment button not appearing** — Verify all required credentials are configured and ACH payments are enabled
* **"Forte is not configured for this location"** — Fill in both **API Access ID (REST)** and **API Secure Key (REST)**
* **Forte rejects the payment form or its signature** — Check that **API Access ID (REST)** holds an API Access ID from Dex, not the shorter Virtual Terminal API Login ID, and that the API Secure Key belongs to the same set of credentials
* **Recurring payments not working** — Ensure the customer has completed at least one successful payment to generate tokens
* **Sandbox mode not working** — Confirm "Use test servers" is enabled and you are using sandbox credentials

## Related

* [Payment gateways](/platform/finance/payment-gateways)
* [Card gateways (Spreedly)](/platform/finance/payment-gateways/spreedly)
* [Customer payment methods](/platform/finance/payment-gateways/customer-payment-methods)


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