Prepaid Card Identification and Filtering

For those merchants that use our extraordinary suite of Fraud Defense tools (99% of our merchants use them), a highly requested and needed feature set has been added to help you save even more money and help stop online fraud and chargebacks.

The NETbilling payment gateway can now identify when a transaction is using a prepaid card. Merchants have the ability to block these transactions automatically by using a Fraud Defensefilter that has also been introduced. When a transaction is processed using the Direct Mode 3 API, the "card_flags" response parameter will return with a value of "P" when a prepaid card has been identified. The Data Retrieval Interface also includes a "card_flags" parameter that will have a value of "P" when a prepaid card has been identified.

For merchants using Fraud Defense, Step #15 can be enabled to automatically block these transactions to Allow, Block, or Block on rebill signups but allow otherwise, such as for a one time sale, product sales etc...

Transactions declined by this filter will have the authorization message set to "F/DECLINED".

Why consider blocking prepaid cards?

Prepaid debit cards are harder to track and identify the cardholder, and could indicate fraud. Prepaid debit cards are also often used in affiliate fraud and they will hold enough funds to pay for the smaller initial set up fee or trial offer of a product, but not enough to pay for the membership or subscription, resulting in a decline on the first recurring billing charge.

New option when adding a transaction to the Negative Database

Also, for merchants using Fraud Defense, when adding customer information to the Negative Database using the "add to neg.db" link on a transaction record in the administration panel, merchants can now choose to add the bank BIN to the negative database for card transactions, or the bank routing number for ACH transactions. Previously, adding a bank BIN or routing number had to be done manually.

If you are not using Fraud Defense and wish to enable these tools, please do so under the Fraud Defense setup screen in your NETbilling admin area. Additional fees do apply.

Additional information on cascaded transactions

When a declined transaction has cascaded to a secondary merchant account using NETbilling's cascade feature, the "Misc Info" section of the transaction now contains the authorization message and reason code that was returned from the first processor in the cascade. This can be found when viewing a transaction record in the NETbilling administration panel, and is also included in the Data Retrieval Interface "misc_info" response parameter.

3D Secure now supported through Inatec

The Inatec processor integration now supports passing through 3D Secure parameters when using Direct Mode 3. This only pertains to merchants who have a merchant account that supports the backend processor called Inatec.

Hosted payment form updates:

Additional validation has been added to the NETbilling hosted payment form to help ensure customers are entering their information properly. This includes various checks on the name, address, and email fields, as well as cross-referencing of state, zip/postal code, and country values for US and CA customers. This validation is performed automatically when fields are set to Required in the Form Editor.

The AVS result message shown on declined transactions can now be targeted by merchants using custom stylesheets. The message is wrapped with the following HTML tag: <span id='avsmessage'>.

If you have any questions regarding these new features, please email or call (661) 252-2456.