> 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/integration-guide/control-center/connectors.md).

# Connectors

## Connectors

**Connectors** are the integrations that actually move money — payment processors like your acquirer or gateway, plus specialized processors for fraud, tax, 3DS, and more. Connecting at least one **payment processor** is what turns your account from empty into functional.

Remember: **connectors are attached at the Business Profile level.** Make sure you're on the right profile and mode before you begin — see Getting Started.

This section covers:

* Connect a payment processor
* Configure payment methods (PMTs)
* Other processor types

***

### Connect a payment processor

The **Connectors → Payment Processors** screen lists everything you've connected and lets you add more.

{% embed url="<https://scribehow.com/o/qzpN4gAaRXWhBwFWaO3hnQ/viewer/How_to_Connect_Adyen_Payment_Processor_in_Hyperswitch__FH8Z-axoT4S44XvmHppEKg>" %}

#### Adding a processor

1. Go to **Connectors → Payment Processors → + Connect**.
2. **Pick your processor** from the list of supported connectors.
3. **Enter credentials** — API keys, secrets, and any processor-specific fields.
4. **Select the payment methods** you want to enable through this processor (cards, wallets, bank transfers, etc.).
5. **Save**. The connector becomes active and is now eligible to process payments for this profile.

#### Tips

* **Test first.** Connect in Test mode, run a payment, confirm success, *then* repeat with live credentials.
* **Multiple connectors** for the same profile are normal — that's what enables **Routing** (see the Workflow section) to choose the best one per transaction.
* **Credentials live per profile.** The same processor connected under two profiles is two separate connector records.

> 🔐 Credentials are stored securely. Anyone with access to the profile can *use* a connector, but editing keys should be restricted via **Roles** — see the Settings section.

***

### Other processor types

Beyond payment processors, the Connectors section supports specialized processors. You only need the ones relevant to your setup.

| Processor type           | What it does                                                   |
| ------------------------ | -------------------------------------------------------------- |
| **Payment Processor**    | Core acquiring/gateway that charges the customer               |
| **Payout Processor**     | Sends money *out* to recipients (powers the Payouts screen)    |
| **Fraud & Risk**         | Screens transactions for fraud before/after authorization      |
| **3DS / Authentication** | Handles 3D Secure authentication for cards                     |
| **PM Auth Processor**    | Payment-method authentication (e.g. bank account verification) |
| **Tax Processor**        | Calculates tax on transactions                                 |
| **Billing Processor**    | Handles subscription / recurring billing                       |
| **Surcharge Processor**  | Applies surcharges to transactions                             |
| **Vault Processor**      | Securely stores and tokenizes payment credentials              |

Each is connected the same way as a payment processor: pick it, enter credentials, save. Several of these pair with a **Workflow** feature — for example, the 3DS processor is driven by the **3DS Decision Manager**, and the Surcharge processor by **Surcharge** rules.

***

### Where to go next

* **Workflow** → route across your connected processors and add 3DS, surcharge, and fraud rules.


---

# 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://docs.hyperswitch.io/integration-guide/control-center/connectors.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.