BillPay and B2B Gateway work together to securely facilitate and perform hosted online payments for Merchants and their Customers (a.k.a. Buyers). The BillPay interface and functionality are customizable to meet the Merchant's functional needs.

Topic contents:

Key terms

BillPay solution interfaces at-a-glance

End-to-end configuration and onboarding process

Configuration prerequisites

BillPay key terms

Review the following key terms to help with your understanding of the setup, configuration and administration of the solution.

hmtoggle_plus0Merchant Portal

The interface used to setup and configure the BillPay solution.

hmtoggle_plus1  BillPay Portal


Entity setup to process electronic payments and invoices. The Merchant exists in both Merchant Portal and BillPay. The same Merchant name is used in both interfaces.

A Merchant User will access both Merchant Portal and BillPay with the same login credentials. Permissions for both interfaces are managed in Merchant Portal.

hmtoggle_plus1  Buyer

hmtoggle_plus0Merchant division

The Merchant Division represents the ERP business unit (e.g. company code) and is used in determining the appropriate B2B Gateway Payment Configuration (a.k.a. XIID) to which the invoice payment transaction should be routed. You must have at least one Merchant Division.

When processing payments in BillPay, the XIID is determined by a unique combination of Merchant Division + Currency + Payment Type.

hmtoggle_plus1  BillPay roles


An object in BillPay tied to a billing document in the ERP system. Can have multiple payments against it in the form of transactions.

hmtoggle_plus1  Transactions


BillPay solution interfaces at-a-glance

There are certain tasks that are performed in Merchant Portal and some that are performed in BillPay. A Merchant's Buyer (i.e. Customer) Users would only access the BillPay Portal; he/she would never have access to the Merchant Portal. The following provides an at-a-glance view of which tasks are performed in which Portal site:


End-to-end BillPay configuration and onboarding process

BillPay onboarding consists of the following high-level process steps:

1.B2B Payments enables the appropriate functionality.

2.Determine the features and functionality being implemented including any enhanced features.

3.Complete the settings on the BillPay Configuration page.

4.Complete the settings on the Merchant Division page.

5.If using Custom Roles, complete the Roles pages. NOTE: Custom Roles are required if you are implementing the BillPay Activity Report. You setup BillPay Teams after you create Merchant Users.

6.Submit the Onboarding Request via the Onboarding page.

7.Receive notification once the request is processed and continue with ERP integration.

8.End Merchant Portal configuration process. Continue with ERP integration activities and setup within the BillPay Portal (see BillPay Portal online help for information on that interface).

Click to Expand

Click to Expand

BillPay configuration prerequisites

BillPay must be enabled in the Merchant's Profile before any configuration can be performed. The selections made in the profile will affect what pages and configuration settings display. INTERNAL ONLY: Refer to the Enable BillPay topic for more information.

Determine the features and functionality being implemented including any enhanced options.

Enter the appropriate IP Address, Range or Network for incoming BillPay traffic for both QA and Production environments on the Origination IPs page.