Skip to main content
Before making transactions through Orchestra, you need to connect at least one payment provider. Orchestra supports gateways including Stripe, Adyen, Worldpay, Authorize.net, and more.
Need a gateway we don’t support? Request an integration — we add new providers at no cost within 2-4 weeks.

​
Prerequisites

  • An Orchestra account (sign up here)
  • A payment gateway account with API credentials

​
Add a Provider

1

Navigate to Payment Gateway Accounts

In the Orchestra portal, go to Resources > Payment Gateway Account > Create.
2

Configure the Connection

Fill in the required fields:
FieldDescription
NameA friendly identifier you’ll use in API calls (e.g., “StripeTest”, “Adyen_Production”)
UsernameSelect to assign this account to your user or restrict this account to a specific user
Payment Gateway NameSelect your payment provider from the dropdown
CredentialsEnter the API credentials for your gateway
The credentials fields change based on the gateway you select. Common fields include API keys, terminal IDs, merchant IDs, and secret keys.
3

Save

Click Save. Your provider is now connected and ready for transactions.

​
Gateway Credentials

Each gateway requires different credentials. Here are examples for common providers:
  • API Key: Your Stripe secret key (starts with sk_test_ or sk_live_)
Find these in your Stripe Dashboard under Developers > API Keys.
  • 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 under Developers > API credentials.
  • 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).

​
Test vs Production Credentials

Always use test/sandbox credentials during development. Production credentials will process real transactions.
Most gateways provide separate test and production credentials:
EnvironmentUse For
Test/SandboxDevelopment, testing, CI/CD
Production/LiveReal 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

Generate API Key

Create credentials for API access

Quickstart

Make your first charge