Configuring PINless Debit Payment Processing

5 Configuring PINless Debit Payment Processing

Learn how Oracle Communications Billing and Revenue Management (BRM) uses Paymentech to process PINless debit payment transactions.

Topics in this document:

About PINless Debit Payments

You can configure BRM to support PINless debit payments from your customers. PINless debit payments are debit card payments made without the card's magnetic stripe or your customer's PIN. Supporting PINless debit payments can reduce your transaction processing costs, because transactions are handled by domestic debit networks that tend to have lower fees than Visa, MasterCard, and other brands.

In BRM, these payments are processed through Paymentech as PINless debit BillPay.

About PINless Debit Validation and Authorization

BRM validates all debit card payments using Paymentech's Account Verification functionality. For more information, see "About Paymentech Account Verification".

BRM authorizes both online and batch PINless debit payments by sending a Purchase Authorization (PA) request to Paymentech that includes the following:

Action code set to PA
Method of Payment (MOP) set to DP
(For online only) Format indicator set to 02, with the billing reference number set to the customer's account number
(For batch only) Product record set to PDE001

Paymentech checks if the customer's account has enough funds and, if it does, debits the customer's account.

The response from Paymentech includes the MOP set to the PINless debit network and a trace number, which BRM then stores in the /event/billing/payment/cc object. When pin_deposit is run, it includes both the MOP the PINless Debit transaction was processed as and the trace number in the deposit request it sends to Paymentech.

Limitations of PINless Debit Payments

Before configuring BRM to support PINless debit payments, consider the following limitations:

Tokenization is not supported for PINless debit payment transactions. As a result, if a card number has already been tokenized in BRM, it cannot be changed to a PINless debit payment method.
The Card Type Indicator (CTI) cannot be sent with PINless debit transactions.
Stored credentials are not supported with PINless debit transactions.
Refunds are not supported with PINless debit transactions.

Setting Up PINless Debit Processing

Note:

Before Paymentech can start processing PINless debit transactions, your debit network must approve your merchant account and add all of your payment channels.

To set up BRM to support PINless debit payment transactions, do the following:

Enable the PINlessDebitProcessing business parameter in BRM. See "Enabling PINless Debit Payments in BRM".
Contact your Merchant Services Representative at Paymentech to have them enable PINless BIN File Management for your account.
Customize the PCM_OP_CUST_POL_PREP_PAYINFO policy opcode to identify PINless debit payment types. See "Identifying PINless Debit Payment Types".

Enabling PINless Debit Payments in BRM

To enable BRM to collect payments through PINless direct debit, use the pin_bus_params utility to change the PINlessDebitProcessing business parameter. For information about the utility's syntax and parameters, see "pin_bus_params" in BRM Developer's Guide.

To enable the collection of PINless debit payments:

Go to BRM_home/sys/data/config.
Create an XML file from the /config/business_params object:
```
pin_bus_params -r BusParamsAR bus_params_AR.xml
```
In the file, set the <PINlessDebitProcessing> element to enabled:
```
<PINlessDebitProcessing>enabled</PINlessDebitProcessing>
```
Save the file as bus_params_AR.xml.
Load the XML file into the BRM database:
```
pin_bus_params bus_params_AR.xml
```
Stop and restart the CM.
(Multischema systems only) Run the pin_multidb script with the -R CONFIG parameter. For more information, see "pin_multidb" in BRM System Administrator's Guide.

Identifying PINless Debit Payment Types

BRM determines whether a payment card supports PINless debit transactions by reading the first character in the /payinfo/cc object's PIN_FLD_TYPE_STR field. By default, this field is not set by BRM. You must customize the PCM_OP_CUST_POL_PREP_PAYINFO policy opcode to identify whether a payment card supports PINless debit and then set the PIN_FLD_TYPE_STR in /payinfo/cc appropriately.

To identify and mark PINless debit payment types, customize the PCM_OP_CUST_POL_PREP_PAYINFO policy opcode to do the following:

Validate that the PIN_FLD_TYPE_STR field in the /payinfo/cc object is not already tokenized.

If the field contains a token, it cannot be changed to a PINless debit payment type. The customer's debit card must be re-registered to be used for PINless debit transactions.
Customize the fm_cust_pol_is_pinless_debit() function to use the Paymentech BIN files to determine whether a payment card supports PINless debit.
Customize the fm_cust_pol_is_pinless_debit() function to return true when the card is PINless debit and false when it is not.

Depending on the value returned by fm_cust_pol_is_pinless_debit(), the policy opcode sets the /payinfo/cc object's PIN_FLD_TYPE_STR field as follows:
- If True is returned, the first character of the PIN_FLD_TYPE_STR output flist field is set to Y.
- If False is returned, the first character of the PIN_FLD_TYPE_STR output flist field is set to N.

For more information about the PCM_OP_CUST_POL_PREP_PAYINFO policy opcode, see "Customizing Payment Method Data Preparation" in BRM Opcode Guide.