Sign Up to be a Technology Partner

Complete the Become a Partner registration form on the developer center. When completing the form, enter an Organization ID that you want to represent your organization in all future transactions.

After your registration is approved, you receive these credentials:

• A test partner account for your organization, which includes your organization ID.
• An activation email is sent to your registered email address. You must follow the instructions included in the email within 24 hours to complete registration.
• A member of the regional partnership team is assigned to assist you with your onboarding journey.

During onboarding, you set up and test your Solution's checkout experience with payment processing in the test environment. After your Solution setup is validated by , your account is transitioned to the production environment.

Register Your Solution

When you receive your test account credentials, log in and register your Solution in the . Registering your Solution creates a Solution ID, which is needed to begin processing payments on behalf of merchants.

1. Log in to your test account:

2. On the left navigation panel, choose Partner Management > Solutions.

   The Solutions page appears.

3. Click Create Solution on the top right of the screen.

   The Create Solutions page appears.

   

4. Under Configure your Solution, choose one of these referral options:

• SMB: To refer a small to medium-sized merchant business to .

  

• Enterprise: To refer a medium to large-sized merchant business to .

  

  When done, click Next.

5. Under Add details and contacts, enter your Solution details and business contact information. When choosing an industry type, you can select up to five.

   

   When done, click Next.

6. Under Scope configuration, check the boxes that correspond to the payment products you want to enable for your Solution.

   

   When done, click Next.

7. Under Review and create Solution, click Create solution to approve your choices and submitted information. The Success window displays. You can click Go to solution details to return to the Solutions page.

   

After registering your Solution, you have the option to begin creating your authentication credentials. To know which authentication method to use, see Step 3 Set Up Authentication.

Set Up Authentication

offers OAuth 2.0 and the partner solution key as the merchant authentication methods that you can integrate into your Solution. Merchant authentication is what enables your Solution to securely process payments on behalf of merchants. The authentication method that you use is dependent on the merchant-type you are working with. Review these descriptions to determine which authentication method to use:

Which Authentication Method to Use

Set Up REST

To enable your system and solution to communicate with , you must integrate it to the REST API. uses the REST API to exchange request and response messages over HTTPS.

You have two options for setting up your system to send and receive REST API messages:

• Create a custom REST API integration.
• Install the REST Client SDK.

Include Your Solution ID

When you send API requests on-behalf of merchants, you must include your Solution ID in as a request. The details about how to configure your REST setup to include your Solution ID are explained in the OAuth 2.0 guide.

(Optional) AI-Assisted Development Using Developer MCP SDK

You can use the Developer MCP SDK with an AI-enabled IDE to help set up your REST API integration. The tool provides AI-assisted access to SDK documentation, sample code generation, and guided prompts for APIs such as payments, tokenization, transaction search, and webhooks.

Test Your Integration

After setting up your authentication method and making your system REST-compliant, you must validate that your Solution can successfully process payments on behalf of a merchant. At this point in your setup journey, you have received your test organization ID and Solution ID. Include these credentials in your test requests to enable customer service to track, assist, and validate your requests.

Test Endpoints

To send test requests, use endpoints that begin with the domain hostname:

For example, to send an authorization test request, use the endpoint:

/pts/v2/payments

Create a Test Merchant Account

Your test requests require a merchant ID, which represents the merchant business you are making transactions on behalf of. To obtain a test merchant ID, you can create a test merchant account using the merchant sign-up page.

Validation Checklist

Review and complete these requirements before notifying your partnership contact that your Solution is ready for validation:

Additional Validation for Partner Solution Keys

Receive Production Approval

Notify your partnership contact that your Solution can successfully complete transactions in the test environment. Your contact will begin the process of verifying your test transactions.

The review team uses your Solution ID to retrieve and review your test requests. After confirming that your Solution is configured correctly, your partnership contact notifies you that your Solution is approved for the production environment.

Go live

When you are ready to go live, notify your partnership contact to create your production account. When your new account is created, you can log in to the production :

Go-live Checklist

When you log in to your production account for the first time, you must:

• Register your Solution again to create your production Solution ID.
• Create your production REST API keys:
  • P12 Certificate or Shared Secret Key Pair
  • MLE Response Key
• Create your production authentication credentials:
  • OAuth 2.0:
  • Partner Solution Key:
• Update your system and solution with the production endpoints and your new production credentials.

(Optional) Refer Merchants

You can refer merchants to or to earn a monthly commission from their gateway payment volume. For an overview about referring merchants, see Refer Merchants.

If you are working with referred merchants, complete these additional requirements before processing live payments: