BillPay provides many standard features and settings as well as enhanced ones that can be enabled by B2B Payments and then configured by the Merchant. Review the standard and enhanced features below to determine which ones best meet your business needs.

Topic Contents:

Basic features and settings

Enhanced features and settings


Basic features and settings

Merchant-defined URL

Merchant-defined alias is used in the BillPay Portal URL.
e.g. https://billpay.paymetric.com/merchantname

Branding with merchant logo

Merchant-provided logo displays in the BillPay Portal.

Online help

The BillPay Portal contains an online help site with content that is specific to Merchant users and Buyer users. It defines the BillPay Portal functionality and detailed information on how to use it.

Merchant support link

The Merchant configures their own Support URL within the BillPay Portal for use by their end-users.

Buyer management

Enabling the use of Buyers in BillPay allows invoices to be associated to a given Customer (a.k.a. Buyer) within the BillPay Portal.

If implementing Buyers, the Merchant can also configure whether to allow Buyer users to log in to BillPay and make payments as well as whether or not the Buyer can manage their own users.

Buyers must have at least one Buyer Division. The Buyer Division provides logical grouping of the Buyer's invoices/payments based on the Merchant's business needs. This could be by location or perhaps some sort of business division.

User permissions are at the Buyer level. You cannot give a user access to specific Buyer Divisions. Currently a Buyer user can only have access to a single Buyer; however, multiple Buyer access is coming soon.

Invoice payments are processed at the Buyer/Buyer Division level. You cannot select invoices for payment across multiple Buyer Divisions.

Pay multiple invoices at a time

Users can select multiple invoices and make a single payment. The Merchant can configure whether to obtain separate authorizations (resulting in multiple transactions) for each invoice or just a single authorization for all selected invoices. The default is to obtain a single authorization resulting in a single transaction for the payment.

Users can also select credit invoices to offset the balance of the selected debit invoices if available. If credit invoices are used and even if separate authorizations are configured, any remaining balance from the selected debit invoices will process as a single authorization. Credit invoice(s) must have the same Merchant Division and Currency of the debit invoice(s) being offset.

View receipts

Standard receipts are viewable online in BillPay Portal that include the following default information:

Merchant Name

Transaction Details

Invoice Grid

Invoice Details

Line Items

Define supported payment methods

Define the supported Card Types and Currencies and whether to support eCheck as part of standard configuration.

Available Card Types - MasterCard, Visa, Amex and Discover

Available Currencies - USD and CAD

Auto settle BillPay payments

You can configure BillPay to use a Sale Operation rather than a standard Authorization which will automatically submit transactions for settlement that are generated from a BillPay payment.

Choose whether to display due date

You can configure whether a due date displays or not for your invoices.

Prepopulate payment info

You can configure BillPay to prepopulate the Phone, Email, Name and/or Address from the invoice when making a payment in BillPay Portal. The data is uploaded to BillPay with the invoice.

Display security code field

You can configure whether or not the Security Code field displays and if it is required when making payments in the BillPay Portal.

Standard permission roles

There are two standard roles with assigned permissions for both Merchant users and Buyer users (if implementing). Following is a list of the permissions assigned to each role.

Standard Merchant Admin role:

Standard Merchant Reporting role:

User Management - Ability to edit buyer users

View Reports - Ability to view all reports

Export - Ability to export data

Submit Invoice Payment - Ability to submit payments on an invoice

Issue Credit - Ability to edit or delete

Submit Prepayment - Ability to submit prepayments **

Edit Scheduled Payments - Ability to edit or delete scheduled payments **

Edit Stored Payment Methods - Ability to add, edit, and delete stored payment methods

Edit Buyer Configuration - Ability to edit buyer information and configuration

Edit Settings - Ability to edit merchant settings

View Reports - Ability to view all reports

Export - Ability to export data

** Permission included by default if this optional feature is enabled.


 

Buyer Admin role:

Buyer Reporting role:

User Management - Ability to edit buyer users

View Reports - Ability to view all reports

Export - Ability to export data

Submit Invoice Payment - Ability to submit payments on an invoice

Submit Prepayment - Ability to submit prepayments **

Edit Scheduled Payments - Ability to edit or delete scheduled payments **

Edit Stored Payment Methods - Ability to add, edit, and delete stored payment methods

View Reports - Ability to view all reports

Export - Ability to export data

** Permission included by default if this optional feature is enabled.


Enhanced features and settings

Ability to export

Provides the Merchant (and Buyer if implementing) with ability to export various BillPay reports and data.

Multi-language support

Allows you to configure the language in which the BillPay Portal contents display. Supported languages include: English and French Canadian.

Near real-time RESTful API

Allows real-time calls to the BillPay platform in addition to Batch processing.

Transaction credits

Allows the Merchant to configure the ability for their users to issue a credit against a Transaction.

FSA

Allows a flexible spending account payments.

Voids

Allows the Merchant to configure the ability for their users to void an authorized transaction (i.e. cancel a payment that has not been settled).

Residual and/or partial payments

Allows a payment against an invoice that is less than the total balance.

A Merchant can set either Residual or Partial payments for invoices, but not both. For Partial payments, the existing invoice remains open with the remaining balance. For Residual payments, the existing invoice goes to a "Residual Closed" status and balance is set to $0. The Merchant uploads a new invoice for remaining balance.

Merchants can set additional parameters related to residual and/or partial payments during configuration.

Scheduled payments

Allows future payments to be scheduled against an invoice. Merchants can set additional parameters related to scheduled payments during configuration.

Prepayments

Allows payments to be made that are not tied to an invoice.

Custom invoice fields

Allows the use of Merchant-defined custom fields related to invoices in BillPay. There is a limit of 5 custom invoice fields.

Custom roles

Allows the Merchant to create custom roles for Merchant and/or Buyer users using any combination of the individual permissions defined in the Standard Features and Settings table above.

Note that Prepayments and Scheduled payment permissions are only applicable if you have those optional features enabled.

Customized receipts

Allows the Merchant include additional fields on receipts. Following is the full list of available fields:

Logo

Tagline

Header Text

Buyer Name

Buyer Division

Buyer Address

Merchant Name (standard)

Merchant Address

Transaction Details (standard)

Invoice Grid (standard)

Invoice Details (standard)

Line Items (standard)

Footer Text

Ability to email receipts

Allows the Merchant to configure if receipts are emailed to the Buyer user making a payment.

Support subsidiaries

Allows the Merchant to define subsidiaries as an additional method of grouping invoices and transactions. Merchant user permissions are set at the subsidiary level. Subsidiaries are configured as "custom fields". There is currently no limit to the number of subsidiaries a Merchant can configure. You cannot implement both subsidiaries and single sign-on functionality.

Note that once B2B Payments enables any of the custom options, this provides the ability to configure them; it does not automatically make selections on the various configuration tabs. See BillPay Configuration, BillPay Merchant Division, and BillPay Custom Roles for more information.