Payment Gateways and Processors
BluSynergy supports the following Payment Gateways / Payment Processors with the high-level features supported.
The payment processor is configured using the [System >> Payment Processor Configuration] menu and the essential configuration fields are noted below. Note that depending on the selected processor, the field names may adapt (change) to reflect the nomenclature used by that processor.
The basic configuration:
Fig 1. Basic payment processor settings
Using the "Payment Processor" list box, select the processor that you have signed up with.
The Login and Password fields is assigned by your processor (the field names may change to reflect the nomenclature used by that processor - in the example above it is called "API Login Id" and "Transaction Key" by authorize.net)
Clicking on the "Show Advanced Options" shows more fields:
Fig 2. Advanced options for the payment processor configuration.
The generic setting are outlined below. Y = Required, N = No, P = Processor dependent
Click on the links below to review additional configuration settings for these payment processors.
Testing Your Payment Processor Configuration
When configuring a payment processor for the 1st time, we recommend the following test use cases. For the first pass, we recommend you test against the processor's staging/test environment and for the second round, we recommend testing against your processors' live/production environment using small amounts (eg. $1.00). This is a critical step since you will often find that transactions working fine in the test environment (such as tokenization, account updater, ACH etc.) are being declined in the production environment since separate enrollment is required.
The following test credit card numbers usually will work on your processor's staging environment. The expiration date must be set to a future date:
American Express Test Card 370000000000002
Visa Test Card 4111111111111111Second Visa Test Card 4012888818888
Some processors/gateways use specific test cards for each card types and you may wish to test against all these card types
For testing ACH transactions, any valid Bank Routing Numbers will work, the Account Number may be made up. These are some test routing numbers used by some processors/gateways:
A full list of valid routing numbers may be found here: http://www.fedwiredirectory.frb.org/reserve.cfm
Test a payment using each of the major credit card types that you support (Mastercard, Visa, Discover, Amex). Note that test card numbers that will NOT work in the production environment.
If applicable, test using ACH. A valid bank routing number (ABA number) is required, the account number may be synthesized
Find a successful payment and attempt a refund. Do this for both Credit Cards and ACH (if applicable).
If AVS is enabled on your merchant account, then test and verify expected results when you provide the billing address and when you do not provide the billing address.
If CVV (Card Validation Value) is enabled on your merchant account, then test and verify expected results when you provide the CVV and when you do not provide the CVV.
In the BluBilling system, save the card (or ACH) to the Customers profile and then attempt to make a payment using this saved card.
If using tokenization, then verify that the above step created an entry in your merchant account for the new card.
At the end of the day, compare reports in BluSynergy (Payment detail report) against the reports available on your processors' system.
Verify funding by monitoring your bank account and understand the funding cycle (usually 1 to 2 business days) and the settlement mode used by your acquirer (gross settlement vs. net settlement).
The "Test Processor" is a dummy payment processor that may be used to simulate various results by sending various amounts and/or keywords in the payment description as noted below: