1. Configuring and Collecting Payments
  2. Setting Up Merchant Accounts

6 Setting Up Merchant Accounts

Learn how to set up merchant accounts for BRM-initiated payments in Oracle Communications Billing and Revenue Management (BRM). Payment processors, such as Paymentech, use merchant accounts to identify the companies who send them payments.

Topics in this document:

Setting Up Merchant Accounts

To manage BRM-initiated payments, a payment processor, such as Paymentech, creates a merchant account for your company. For example, your account might be assigned the merchant account number 050505. If you accept payments in multiple currencies, a payment processor creates an account number for each currency.

When you send payments to a payment processor, you need to send them the merchant account number so they can determine where to deposit your BRM-initiated payments. To do so, you configure the merchant account number in the configuration file for the Data Manager (DM) that sends the payment request to the payment processor:

-   dm_fusa   mid_ispname_840     050505

This entry maps the merchant ID (mid_ispname_840) with the merchant account number (050505). The merchant ID is a combination of the merchant name (ispname) with the currency ID (840). You need to load merchant names into the BRM database.

To load merchant names into the BRM database, you edit the pin_ach file and load it by using the load_pin_ach utility. An entry in the pin_ach file includes the merchant name: 

fusa     0.0.0.1 /payment -1     ispname     0

If you use multiple currencies, you are given multiple merchant account numbers. You configure multiple entries in the DM pin.conf file, for example: 

-   dm_fusa   mid_ispname_840     050505
-   dm_fusa   mid_ispname_250     050506
-   dm_fusa   mid_ispname_276     050507

You specify merchant names and the payment processors that process your BRM-initiated payment transactions for the entire system. You can specify any number of merchant ID and Merchant account number pairs.

To load merchant names into the BRM database:

  1. Edit the pin_ach file in BRM_home/sys/data/pricing/example. The pin_ach file includes examples and instructions.

    Note:

    The default merchant name used by each payment processor is the first merchant name listed for the payment processor.

    The file includes this entry for Paymentech:

    fusa     0.0.0.1 /payment -1     test     0

    where:

    • fusa is the name of the payment processor.

    • 0.0.1.1 /payment -1 is a routing POID used to identify the database where the payment processor DM runs. The object type and ID (/payment -1) are not significant.

    • test is the merchant name.

      Edit this field to specify your merchant name. This name must match the merchant name entry in the payment processing DM configuration file. For example, if the merchant name in the dm_fusa pin.conf file is mid_ispDealer, the merchant name in pin_ach must be ispDealer.

    • 0 is the payment channel ID.

      Edit this field to specify the payment channel ID for each payment processor. The channel_id value must match a payment channel ID configured in the /strings object. If a payment does not contain a payment channel ID, a value of 0 is saved with the payment by default, which configures it as Unspecified Payment Channel. For more information, see "Configuring Payment Channels".

  2. Save the pin_ach file.

  3. Run the load_pin_ach utility: 

    load_pin_ach  pin_ach

    For more information, see "load_pin_ach".

Specifying Merchant Accounts for the Payment DM

To enable the Paymentech DM to send merchant account data:

  1. Open the Paymentech DM configuration file (BRM_home/sys/dm_fusa/pin.conf).

  2. Change the merchant account entry. Use this syntax:

    - dm_fusa   mid_merchantName_currencyID    merchant_account_number

    For example:

    - dm_fusa   mid_ispname_840     050505

  3. Save and close the file.

  4. Stop and restart the Paymentech DM.

Using More Than One Merchant Name

You might use more than one merchant name if you separate deposits based on payment method (for example, if you deposit payments to a third-party service provider).

If you use multiple merchant names, each merchant name must be entered in the following files:

  • The payment processor configuration file (BRM_home/sys/data/pricing/example/pin_ach).

  • The payment processor Data Manager (DM) configuration file (for example, BRM_home/sys/dm_fusa/pin.conf).