Solidgate • Connectors

Connectors

Explore payment connectors with details on supported payment methods, currencies, regions, and integration specifications

Understanding connectors helps you choose the right setup for your business requirements.

Connectors serve as the foundation of your payment processing infrastructure by defining available capabilities for payments. They determine which payment methods, operations, and authentication options you can use for transactions.

Connector flow

From browsing available options to routing live transactions, activating a connector involves a sequence of decisions and configurations that depend on one another:

Review available options, browse the connector list, and capabilities.
Check features to ensure connectors meet your payment needs.
Set up the connector account and assign your first MID.
Configure payment routing rules.

Setting up a connector account involves steps that vary by provider. Onboarding guides cover what is required to complete configuration before going live.

Hub

To find a connector guide

Go to Orchestration > Connectors.
Find the connector ID and select it.
The connector details page opens.
Navigate to the top right corner to download the connector guide.

Once a connector account is ready, go to Orchestration > Connector accounts to find it in the connector account list. Each connector account shows its operational status:

Active available for routing configuration and payment processing.
Inactive unavailable for routing configuration, but can still be used for processing.
Pending being set up.
Archived no longer supported, and hidden from the connector account list.

Connector components

Routing configurations comprise connectors and connector accounts, both of which are essential for the payment processing infrastructure.

Connector

Defines the technical interface and available capabilities for payment processing.

Connector account

Serves as the bridge between your business and payment service providers.

Connector

Each connector includes:

General information

Name, description, supported acquirers, and connector accounts.

Payment capabilities

Supported payment operations, methods, and authentication.

Other specifics

Currency support, settlement requirements, and special configurations.

Expand all

Payment operations

AUTH
SETTLE
PARTIAL_SETTLE
VOID
REFUND
PARTIAL_REFUND
CHARGE

Payment methods

Card
Traditional card payments using a PAN.
Card-on-File (CoF)
Stored card (PAN) or digital wallet (DPAN) data.
PSP token
A token issued by the payment service provider (PSP) that represents the underlying stored card or digital wallet data.
Network token
A network or scheme issued card identifier that replaces the sensitive PAN.
Apple Pay
Apple digital wallet.
Google Pay
Google digital wallet.
Click to Pay
Multi-network digital card checkout.

Payment authentication

3DS
Clarifies whether 3D Secure (3DS) is supported for payment authentication.

Options

Cardinal MPI
A service for handling 3D Secure transactions.
Solidgate MPI
Solidgate's version of the 3D Secure protocol.
External MPI Data
Uses third-party authentication services for 3D Secure.
Built-in MPI
A built-in 3D Secure implementation.
Stripe MPI
3D Secure authentication provided by Stripe.
Checkout MPI
3D Secure authentication provided by Checkout.
Netcetera MPI
3D Secure authentication provided by Netcetera.

Features

3RI
Requestor Initiated Authentication, where merchants initiate authentication without cardholder involvement.
Data only
Transmits only authentication data without completing the full transaction, enforcing 3DS challenge flow.

Payment features

Card verification (Auth0)
Performs Guide
Validate and store customer card details without charging by using zero-amount authorization requests for future payment token creation. zero-amount transactions to verify card details
Address verification service (AVS)
Guide
Decode AVS, CVV, and ANI results returned by card schemes and issuing banks to verify the cardholder's billing address, security code, and name against issuer records for fraud prevention. Verifies the cardholder's billing address for fraud prevention purposes
Dynamic descriptor
Customizes the transaction description on the cardholder’s statement

Network tokens

Initial payment with network token, Recurring payment with network token
Clarify which payments can use network tokens.

Card-on-File

Card-on-File with PAN, Card-on-File with DPAN
Clarify which card data type can be used for CoF processing.

Additional payment results

Acquirer reference number (ARN)
A unique identifier for transactions, used by acquirers for tracking
Mastercard merchant advice codes (MACs)
Guide
Decode merchant advice codes returned on declined transactions to determine whether to retry, update credentials, or stop future attempts. Codes used to communicate updates or issues related to Mastercard transactions
Scheme transaction ID (trace ID)
A unique identifier used by card schemes for tracking transactions
Auth code
An authorization code issued by the bank to approve a transaction

Other specifics

Require settlement currency mapping
Indicates whether the settlement currency requires mapping
Non-standard max settle period
Maximum time allowed for transaction settlement, differing from the Guide
Typical transaction settlements that occur automatically within the standard period. standard settlement period

Connector account

Each connector account includes:

General information

Account name, description, and legal entity details.

Payment capabilities

Supported payment methods and authentication options, including 3DS and MPI features.

Other specifics

Includes dynamic descriptors, processing currencies, and other special configurations such as network token support.

Payment authentication and features are the same as for the connector.

Default recurring strategy

Defines how recurring payments behave on a connector account when no custom Solidgate Tokens configuration is set. By default, the strategy:

Picks the first available payment method in this order: PSP token, then Card-on-File.
Decides whether the customer-initiated transaction (CIT) requires 3DS.

You can override the default strategy:

Build a cascade from the available payment methods, such as network token, PSP token, and Card-on-File. A network token cannot be the only method in a cascade.
If a payment fails with the first method, the system picks the next one and retries.
Force 3DS logic still applies. Soft decline fallback also applies, so the next attempt is sent to 3DS.

Other specifics

Dynamic descriptors
Transaction descriptions that appear on the cardholder's statement
Use card brand prefix
Adds the prefix of the card brand used for the payment before the dynamic billing descriptor. Prefixes are set per card brand. Applies to dynamic descriptors only.
Use descriptor suffix from initial payment
Lets a recurring payment without a descriptor suffix reuse the suffix of the initial payment. Applies to dynamic descriptors only.
Enabled card brands
Card networks supported by the connector
Processing currencies
Currencies in which payments can be processed
Required fields
Mandatory fields for payment processing in certain regions

They must be included in the API request and may expand over time. For example, zip_code is required for payments in the United States.

List connector accounts

Connector accounts process the payments of your routing configurations. List them to find the identifier that a routing step refers to, or to check which accounts are active.

API

Send a request to the list connector accounts API v2 endpoint with an account-level API key.

Filter by status , connector_id , or name .
Paginate with next_page_token . Omit it on the first request. The token is empty on the last page.
- Each item returns the connector account id , name , status , connector_id , and legal_entity_id , plus its payment, authentication, and descriptor settings.
Pass id to get connector account API v2 to retrieve one connector account.
- The connector account id is the connector_account_id of routing configuration steps and of the routing events report.

To retrieve dynamic descriptors, pass the connector_account_id to the list descriptors API v2 endpoint. Descriptors are sorted newest first.

Filter by status . Only ACTIVE descriptors can be set in routing configuration steps.
The descriptor value is the descriptor of a routing configuration step.
The list is empty for a connector account with the static descriptor type.

Hub

To view the connector account list

Go to Orchestration > Connector accounts.
Filter the list by:
- ID
- Name
- Connector
- Legal entity
- Status

To view dynamic descriptors

Go to Orchestration > Connector accounts.
Open a connector account with the dynamic descriptor type.
Scroll down to the Dynamic descriptors section. It lists each descriptor with its Active or Inactive status.

Looking for help? Contact us

Stay informed with Changelog