Electronic Payment Gateway
In NetForum, electronic payments for credit cards, ACH, Telecheck and PayPal Express Checkout are processed in real time by an electronic payment gateway. This page covers various topics related to gateways and payment processing.
Set up
In the Gateways section below, see specific setup instructions for each gateway.
Generally, for all gateways, here are the setup steps from a high level:
- Choose your gateway.
- Create a merchant account with your gateway and link it to your bank.
- Create a "user" account within your merchant account that will be used solely for electronic payment transactions that are performed in NetForum. This should not be the same account that a human uses--it is best to create a dedicated account for the NetForum application itself.
- Provide Abila the authentication credentials for the user you created in the step above, and Abila will input these into various configuration settings in web.config files for your NetForum application.
- Set the values of the PaymentAPI_iWeb and PaymentAPI_eWeb to be that of the gateway you've chosen.
- Ensure you have your Payment Methods configured properly for credit cards and other electronic payment types you will accept, for both iWeb and eWeb.
- If you plan to have multiple merchant accounts for the same gateway, for example one account for your main organization but a different merchant account for your PAC or Foundation, then you will need to configure Credit Card Gateways.
Gateways
BluePay and Vantiv are supported by NetForum. See Overview of the Payment Processor Enhancements for more information.
The following legacy gateways can be configured through the PaymentAPI_iWeb option.
Processor | System Option Value | Initial Build | ACH | TeleCheck | Tokenization | CreditCardAuthorizationAmount | Notes |
---|---|---|---|---|---|---|---|
Authorize.net | AuthorizeNetProcessor | 2010.01 | Yes | Yes | No | No | See Authorize.net |
Chase Paymentech - Tampa gateway | PaymentechProcessor | 2011.01.02 | No | No | No | No; be sure to clear this value. | |
Chase Paymentech - Salem gateway | PaymentechProcessorSalem | 2011.01.08 and 2013.01.02 | Yes | Yes | Yes | TBD | |
ETS | ETSProcessor | 2013.01 | No | No | No | No | |
Moneris | eSelectPLUSProcessor | 2010.01 | No | No | No | Yes | See Moneris |
PayPal | PayFlowProProcessor | Initial | Yes | Yes | 2013.01.03 | Yes | See Payflow Pro |
SecureNet | SecureNetProcessor / SecureNetVaultProcessor ( | 2011 | Yes | Yes | Yes | Yes | SecureNet (now Worldpay) is replaced by Authorize.net |
Additional Feature List
Multi-Currency
The following integrations work with the NetForum Multi-Currency feature:
- BluePay
- Vantiv
Other legacy gateways:
- PayPal (aka PayFlow Pro)
- Authorize.net
New Gateways
If you would like to use a gateway that is not on the list above, it is possible if you can work with a .NET developer to build the integration. NetForum uses an interface to connect from NetForum to a payment gateway. The developer will need to build out various methods to handle transactions. See Gateway requirements and Level of Effort to integration NetForum to a payment gateway for more; the linked pages explain how a software developer can create the integration, and also outlines various required features a gateway will need to have in order to be compatible with NetForum.
Before going through the work to create a new gateway, you might be able to use a supported gateway if that gateway works with the processor that you would like to use. Many gateways can work with multiple processors.
See also
- Electronic payment processing - detailed flow of how electronic payment processing is handled in NetForum.
- Payments Dictionary: 205 Words Worth Knowing from Vantiv, a payment gateway. A handy glossary.
- Tokenization - explanation of how gateway tokens are handled in NetForum.
- Avectra.netFORUM.Common.CreditCardProcessor - explains the software programming class behind electronic payment transactions. This can be useful to know if you would like to develop your own gateway integration.
- PCI Compliance
- PA-DSS compliance