Differentiate Merchant Submissions

A Partner might have various use cases where they want or need to differentiate how they are submitting Merchants for onboarding.

Some of the most common situations are due to Risk requirements or to support different functionality (based on the type of merchant) on different back-end platforms.

To differentiate a merchant submission, a unique parent login must create the merchant. A parent Users/Login is defined as the owner or the creator of the merchant.

Depending on the type of merchant submission, you will need to adjust your flow. If required to differentiate merchant submissions for Payrix Pro Risk, then please provide the unique login ID you created to the Implementations Team or your Partner Experience Manager to set up your flow correctly.

Signup Form

1. Create two Users on your Partner with Full Access.

2. Submit an Implementation Services ticket with both User ID of both Users. A second Signup form will be created using the second User’s ID.

3. You will use Signup Form A to submit one type of merchant and Signup Form B to submit and differentiate the other merchant submissions.

If applicable, the Partner Onboarding Team or Compliance Team will notify you which signup form to use based on your Risk requirements.

API

1. Create two Users on your Partner with Full Access.

2. Generate API keys for both Users/Logins.

3. Submit an Implementation Services ticket with both Users’ login resource id parameter values. The Implementations Team will set up a workflow on the back end to automate the submission flow.

4. You will use the API key associated with Partner A to create a merchant for one type of setup and the API key associated with Partner B to submit and differentiate the other merchant submissions.

If applicable, the Partner Onboarding Team or Compliance Team will notify you which Partner login and API key to use, depending on the Risk requirements.