Go Live
Follow the tasks on this page to go from registering as a technology partner to processing live payment on behalf of merchants.
Before You Begin
You must have a developed product that you are ready to integrate payment processing into.
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.
On the left navigation panel, choose Partner Management > Solutions.
The Solutions page appears.
Click Create Solution on the top right of the screen.
The Create Solutions page appears.
Under Add details and contacts, enter your Solution details and business contact information.
When done, click Next.
Under Scope configuration, check the boxes that correspond to the payment products you want to enable for your
Solution.When done, click Next.
Under Review and create Solution, click Create solution to approve your choices and submitted information. The Success window displays.
Save the solution ID that displays and then 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 4 Set Up Authentication.
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:
After you integrate to the REST API, verify that these fields are correctly set for a technology partner integration:
- Your Solution ID is included in every payment API request as
clientReferenceInformation.partner.solutionId. For more information, see OAuth 2.0 and Partner Solution Key. - The
v-c-merchant-idJWS body claim is set to the transacting merchant's ID, not your own organization or portfolio ID. - The
issJWS body claim is set to the account ID that created the P12 certificate or shared secret key pair. If you are using a partner solution key, set it the account ID that created the key. For more information, see Partner Solution Key.
Create Test Merchant Account
The REST Get Started guide explains how to create a merchant test account in Step 1. This is not a requirement for technology partners, but it can be useful to have a merchant test account for testing purposes.
AI-Assisted Development Using Developer MCP SDK Optional
You have the option to 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.
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:
OAuth 2.0 Limited Availability
Use OAuth 2.0 when working directly with individual merchant businesses. OAuth 2.0 is an industry-standard authorization protocol that enables the merchants you work with to grant your Solution limited access to their systems. Each merchant completes a one-time authorization setup that grants your Solution access using short-lived access and refresh tokens.
Partner Solution Key PILOT
Use a partner solution key when working with a partner reseller who manages multiple merchants. A partner solution key enables your Solution to process payments across multiple merchant systems. Instead of creating a REST API key for each individual merchant, you create a single partner solution key that enables your Solution to transact on behalf of a portfolio of merchants.
Which Authentication Method to Use
| OAuth 2.0 | Partner Solution Key | |
|---|---|---|
| Use when | Working directly with individual merchant businesses | Working with a partner reseller who manages a portfolio of multiple merchants |
Test Your Integration
After making your system REST-compliant and setting up your authentication method, 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/paymentsCreate 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:
- Your authentication method, either OAuth 2.0 or Partner Solution Key, is configured and working.
- Your Solution ID is included in all payment API requests.
- All required API requests and responses are sent and received as intended.
- Payment errors and uncommon scenarios are handled by your
solution.
Additional Validation for Partner Solution Keys
- If you are using the partner solution key authentication method, you must also coordinate with the partner reseller to verify that merchant authorization works as intended.
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
Solutionagain 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 for OAuth 2.0 or partner solution key.
- Update your system and solution with the production endpoints and your new production credentials.
Refer Merchants
OptionalYou 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:
Submit Banking Information
Submit your banking information using the to receive your commission payments. You will be prompted to submit these details upon first login to the production environment when you are set up for referrals.
Set Up Referrals
Referring to
Follow these steps to refer a merchant to the self-service onboarding option through :
On the left navigation panel, choose Partner Management > Referrals
The Referrals page appears.
Find the package you want to activate in the table and toggle its link status to Active in the Link status column.
In the Link column, click the copy icon next to the package URL.
Send the copied URL to the merchant you are referring.
The merchant uses the link and completes self-service onboarding.
Referring to
Follow these steps to refer a merchant to the sales-assisted onboarding option through :
Sign up for a Partner Portal account using the New Partner Registration page.
Receive an email notification with your log-in credentials within 5–7 business days.
Log in to the Partner Portal.
On the left navigation panel, choose Submit a lead.
The Register New Lead page appears.
Enter the required merchant details and click Submit when done.
A sales representative is assigned to your created lead and contacts the merchant to begin onboarding.
Thanks for your feedback!
Last published: November 18, 2026