> For the complete documentation index, see [llms.txt](https://docs.hyperswitch.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/forte.md).

# Forte

Configure Forte card payments with Hyperswitch.

Forte processes credit and debit card payments in Canada and the United States. Both routes support refunds and automatic, manual, and sequential automatic capture. Mandates and 3DS are not available for these card payments.

### Status and capabilities

**Integration status:** sandbox

**Category:** payment gateway

**Webhook flows:** None declared in code

| Payment method | Type        | Mandates      | Refunds   | Capture methods                         | 3DS           | Card networks                                                  | Countries | Currencies |
| -------------- | ----------- | ------------- | --------- | --------------------------------------- | ------------- | -------------------------------------------------------------- | --------- | ---------- |
| card           | Credit Card | not supported | supported | automatic, manual, sequential automatic | not supported | American Express, Diners Club, Discover, JCB, Mastercard, Visa | CAN, USA  | CAD, USD   |
| card           | Debit Card  | not supported | supported | automatic, manual, sequential automatic | not supported | American Express, Diners Club, Discover, JCB, Mastercard, Visa | CAN, USA  | CAD, USD   |

3DS is not supported. A card request sent with 3DS set is rejected with a "not supported" error before anything reaches Forte ([`FortePaymentsRequest`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte/transformers.rs#L98-L105)), so route cards to another connector if your profile enables 3DS.

Capture method changes what the create response reports. A manual-capture authorization returns `Authorized`, and a capture returns `Charged`. An automatic-capture sale returns `Pending` even when Forte approved it, and the payment moves to `Charged` only when a sync reports Forte's status as complete or settled ([`get_status`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte/transformers.rs#L217-L227), [status mapping](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte/transformers.rs#L205-L215)). Sync after every automatic payment before treating it as paid.

### Authentication

Provide the **API Access ID**, **Organization ID**, **API Secure Key**, and **Location ID** shown in the connector form. The labels and accepted multi-auth fields are defined by the [`forte.connector_auth.MultiAuthKey` configuration](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/connector_configs/toml/sandbox.toml#L2759-L2763) and [`ForteAuthType::try_from()`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte/transformers.rs#L174-L192).

They are not all used the same way. The **API Access ID** and **API Secure Key** are combined and sent as HTTP Basic authentication in the `Authorization` header. The **Organization ID** is sent in the `X-Forte-Auth-Organization-Id` header and, together with the **Location ID**, forms the request path, `/organizations/{organization id}/locations/{location id}/transactions` ([`get_auth_header`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte.rs#L123-L146), [`get_url`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte.rs#L220-L225)). A wrong Access ID or Secure Key fails authentication; a wrong Organization ID or Location ID sends the request to the wrong endpoint.

### Before you start

1. Create or sign in to your [Forte account](https://www.forte.net/) and obtain the **API Access ID**, **Organization ID**, **API Secure Key**, and **Location ID**.
2. Sign in to the [Hyperswitch control center](https://app.hyperswitch.io/) and open Forte.
3. Enter the four credentials.

To connect Forte to your Hyperswitch account, follow [Activate a connector on Hyperswitch](/integrations/connectors-integrations/activate-connector-on-hyperswitch.md), then return here for what Forte supports.

### Webhooks

Forte webhooks are not currently supported. Event lookup returns `EventNotSupported`, while object and resource lookup return `WebhooksNotImplemented`; use payment sync for payment status and refund sync for refund status. See [`IncomingWebhook for Forte`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte.rs#L710-L733), [`ConnectorIntegration<PSync>`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte.rs#L296-L357), and [`ConnectorIntegration<RSync>`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte.rs#L635-L694).

The connector form exposes a **Source verification key**, but the current webhook implementation does not consume it because callbacks are unsupported. See [`forte.connector_webhook_details`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/connector_configs/toml/sandbox.toml#L2764-L2765) and [`IncomingWebhook for Forte`](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte.rs#L710-L733).

### Source reference

Authentication and webhook behavior on this page is tied to Hyperswitch `d03f8547d6367fab56690e4f5043590be4935dcd`. See [Forte connector source](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte.rs) and [Forte transformers](https://github.com/juspay/hyperswitch/blob/d03f8547d6367fab56690e4f5043590be4935dcd/crates/hyperswitch_connectors/src/connectors/forte/transformers.rs).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hyperswitch.io/integrations/connectors-integrations/payment-processor-capabilities/available-connectors/forte.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.