Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.
Acquirer & Reseller

Merchant Setup


You can follow the steps outlined in this section or use the to register merchants. Contact your Regional Sales Lead to obtain additional information.

Complete these nine tasks to set up a merchant account.

Merchant Agreement

A merchant agreement is a contract between you and the merchant. The agreement specifies each party's respective rights, duties, and obligations for participation.

Merchants must evaluate or modify their system to process transactions through a authorization and capture platform.

Existing merchant agreements need to be updated to reflect participation in processing. It is important that you review changes to the merchant relationship relative to transaction processing and document them in the merchant agreement, regardless of the connectivity option selected by the merchant.

A new merchant agreement, or an addendum to an existing agreement, can include these items:

  • Terminal requirements, costs, and installation considerations
  • Pricing changes, if relevant
  • Support for authorization and clearing messages at the point of sale
  • Receipt of new information on reports, if relevant
  • Network participation and compliance with related rules and regulations

Register the Merchant

Merchants must register an evaluation account with , using one of these methods:

  • Direct merchants can use this location: Sandbox signup.
  • You can register merchants directly using tools available in the .

After a merchant completes registration, they receive an email with instructions to set up their user account for the .

An evaluation account cannot be directly taken to production. There are still contractual business steps that must be completed before processes production transactions for a merchant. For more information, see Submit the Quote and Contracts.

Choose an Integration Method

Many merchants connect to for transaction processing by downloading one of the prebuilt API clients.

These API clients fall into these categories:

  • The development platform with REST-based connection
  • Simple Order API (prebuilt API using either an Extensible Markup Language (XML) or name-value pair data scheme)
  • SOAP Toolkit API alternative hosted and secured options

There are alternate means to send transaction requests, although many merchants use some form of the API clients as their default processing model (linked to the payment pages of their website).

Find API clients on the Documentation Hub.

Download Documentation

Find documentation for the client application and tools on the Documentation Hub.

Create an Encryption Key

When an evaluation account is set up, the merchant is ready to start integration with a test environment.

The first step is to generate an encryption key that is used with whatever API or connection method the merchant uses to send transaction requests to .

Code and Test the Merchant Connection

When the merchant downloads the software and documentation for its connection method, instruct the merchant to code its software for the test environment.

The specifics of this testing vary depending on the connection method the merchant uses. The merchant should send test transactions to that mimic successful, declined, or erroneous transactions.

Submit the Quote and Contracts

The merchant must submit a signed quote and any contracts before they can go live in . The merchant is not permitted to process in a production environment until they complete this step.

After receives the signed quote/contract from the merchant, the merchant's account is classified as a Test account rather than an evaluation account.

This step is optional if the merchant is enabled on your behalf.

Configure Merchant Banking

Before a merchant can go live in , they must provide acquiring banking information.

Banking information differs depending on the banks or institutions with which the merchant does business. Merchant banking information can include these parameters:

  • Merchant ID (MID)/terminal ID (TID) values for each transaction currency supported (often different from funding currency)
  • Merchant address data

Configure Products

In addition to the banking entities and processor setup required within merchant banking configuration, setup can also be required for products or connection methods the merchant chooses to use.

Some of these setups can be completed by the merchant, and some setup items must be configured by Customer Support on behalf of the merchant account (specific reporting configurations, PayPal, or other payment type setup).

Go Live

The merchant is ready to request account enablement in the production environment.

Account enablement can happen before, or when, the merchant opens their site or application to the public, or at the beginning of a suite of tests from the merchant side.

Last published: November 18, 2026

Not available for your audience

This page isn't available for your current audience selection.