Merchant Onboarding refers to the creation of the Merchant and/or the Client's Merchant Portal. See Services Onboarding for adding/enable Services for the Merchant.

Important:        For a Merchant's contacts to receive service notifications, you must assign the correct Service Notification Distribution Lists (a.k.a. Campaigns) to the account in Salesforce.

 

Scenario

Action required

Scenario A:

New Master Service Agreement (MSA)

Requires new Organization and new Merchant.

Add Merchant

Scenario B:

Addendum to MSA

Separate XiPay Web Service Account (WSA)

Can either share or have separate XiSecure Data Set Profiles (DSP)

Add Merchant using Existing Organization.

newMerchExistingOrg

XiPay Considerations:

-Note that if you create new Merchant, a separate XiPay Web Service Account (WSA) will be created.

-The WSA is used to authenticate to the XiPay platform. There is a one-to-one relationship between a Merchant and an XiPay WSA.

-The Client will have the ability to add XiPay WebGUI users to XIIDs across multiple Merchants if they have proper role permissions by using the add existing user option.

oNote that adding an existing user DOES count against the user quota unless it is an Integrator Consultant.

XiSecure Considerations:

-Are they using same DSP?

-If not, what token format will they use?

Scenario C:

Addendum to MSA

Same XiPay WSA

Can either share or have separate XiSecure DSP

Do NOT add a new Merchant.

If you need to add a new Approving Manager, select the Merchant and navigate to Settings | Users.

XiPay Considerations:

-Note that in this scenario, all XIIDs (a.k.a. XiPay Server IDs or Payment Configuration IDs) must use the same XiPay WSA.

-If they need a separate XiPay WSA then a new Merchant must be added and it would fall under Scenario B.

XiSecure Considerations:

-Are they using same DSP?

-If not, what token format will they use?

Scenario D:

Breakout Existing Merchant to new Master Service Agreement (MSA)

XiSecure: both entities using XiSecure service

Create a new Organization and Merchant.

XiPay Considerations:

-Client removes users from XIIDs.

-Client can work with B2B Payments Support Services to change XIIDs if needed.

XiSecure Considerations:

-Requires a new DSP and cutover to the new DSP

Scenario F:

Breakout Existing Merchant to new Master Service Agreement (MSA)

XiSecure: only 1 entity is using XiSecure service

Requires new Organization and new Merchant Portal.

XiPay Considerations:

-Client removes users from XIIDs.

-Client can work with B2B Payments Support Services to change XIIDs if needed.

XiSecure Considerations:

-If existing entity is keeping XiSecure then no change is required.

-If only the new entity is keeping XiSecure, then a new DSP and cutover is required

Scenario H:

Cancel Master Service Agreement (MSA) and Merchant merging to another MSA

XiSecure: only 1 entity is keeping XiSecure service

Requires new Organization and new Merchant Portal.

XiPay Considerations:

-Client removes users from XIIDs.

-Client can work with B2B Payments Support Services to change XIIDs if needed.

XiSecure Considerations:

-Requires new DSP.

Scenario I:

Cancel Master Service Agreement (MSA)

Disabling Former B2B Payments Clients