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

# Adding a Payment Provider

> Connect a payment gateway account to Orchestra with your API credentials so you can start routing real transactions.

Before making transactions through Orchestra, you need to connect at least one payment provider. Orchestra supports [{supportedIntegrations} gateways](https://orchestrasolutions.com/integrations/) including Stripe, Adyen, Worldpay, Authorize.net, and more.

<Tip>
  Need a gateway we don't support? [Request an integration](https://orchestrasolutions.com/integration-request/). We add new providers at no cost within 2-4 weeks.
</Tip>

## Prerequisites

* An Orchestra account ([sign up here](https://portal.orchestrasolutions.com))
* A payment gateway account with API credentials

## Add a Provider

<Steps>
  <Step title="Navigate to Payment Gateway Accounts">
    In the Orchestra portal, go to **[Payment Gateway Account > Create](https://portal.orchestrasolutions.com/#/resource/paymentGateway/create)**.
  </Step>

  <Step title="Configure the Connection">
    Fill in the required fields:

    | Field                    | Description                                                                                                                              |
    | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
    | **Name**                 | A unique identifier for this gateway account (e.g., "stripeTest", "adyenProduction"). Used in API calls to specify which gateway to use. |
    | **Username**             | (Create only) Optionally assign this gateway account to a specific user. If blank, the account is available to all users.                |
    | **Payment Gateway Name** | Select your payment provider from the dropdown                                                                                           |
    | **Credentials**          | Provider-specific fields appear after selecting a gateway. Enter your API credentials from your gateway's dashboard.                     |

    <Note>
      The credentials fields change based on the gateway you select. Common fields include API keys, terminal IDs, merchant IDs, and secret keys.
    </Note>
  </Step>

  <Step title="Save">
    Click **Save**. Your provider is now connected and ready for transactions.
  </Step>
</Steps>

## Gateway Credentials

Each gateway requires different credentials. Here are examples for common providers:

<Accordion title="Stripe">
  * **API Key**: Your Stripe secret key (starts with `sk_test_` or `sk_live_`)

  Find these in your [Stripe Dashboard](https://dashboard.stripe.com/apikeys) under Developers > API Keys.
</Accordion>

<Accordion title="Adyen">
  * **Merchant Account**: Your merchant account name
  * **Username** and **Password**: Your Adyen username and password
  * **Company Name**: Your company name in Adyen

  Find these in your [Adyen Customer Area](https://ca-test.adyen.com/) under Developers > API credentials.
</Accordion>

<Accordion title="Worldpay">
  * **SecurenetId**: Your unique merchant identifier for Worldpay's API.
  * **SecureNetKey**: Your API authentication key for Worldpay backend configurations.

  Find these in your Worldpay Virtual Terminal under Settings > Key Management (or Settings > Obtain Secure Key).
</Accordion>

## Test vs Production Credentials

<Warning>
  Always use test/sandbox credentials during development. Production credentials will process real transactions.
</Warning>

Most gateways provide separate test and production credentials:

| Environment     | Use For                     |
| --------------- | --------------------------- |
| Test/Sandbox    | Development, testing, CI/CD |
| Production/Live | Real customer transactions  |

When you're ready to go live, create a new Payment Gateway Account with your production credentials. You can keep both test and production accounts configured and reference them by name in your API calls.

## Next Steps

<CardGroup cols={2}>
  <Card title="Generate API Key" icon="key" href="/getting-started/generate-api-key">
    Create credentials for API access
  </Card>

  <Card title="Quickstart" icon="code" href="/quickstart">
    Make your first charge
  </Card>
</CardGroup>