Difference between revisions of "Payment Processors"

From AWBS Wiki
Jump to: navigation, search
(Authorizenet)
Line 28: Line 28:
  
 
Authorizenet is an onsite processor, your customer's credit card information will be stored in your database. Make sure you have a SSL Webcert installed.''
 
Authorizenet is an onsite processor, your customer's credit card information will be stored in your database. Make sure you have a SSL Webcert installed.''
 +
 +
 +
== BluePay ==

Revision as of 13:51, May 26, 2008

Authorizenet

Settings at authorizenet.com:

Direct Response - Delimited Response = Yes Transaction Version = 3.1 Password Required mode = checked


In AWBS;

In the Module Setup page, select Authorize.net in the Main Payment Module section.

Select all Credit Card types you will accept in the Accepted Credit Cards/Payment Methods section.


In Payment Setup, enter your authnet username. Enter your password OR Transaction Key. (older accounts may use the password, most new accounts will use the Transaction Key) Enter the correct url. (The correct url should be present by default.) The Transaction Type should be set to AUTH_CAPTURE to charge the credit cards. (AUTH_ONLY is not recommended.)

The test mode setting will trigger test mode at authorizenet. Use test credit card 4111111111111111 for testing.

Then in the System Options page of the AWBS Configuration, enter your chosen CC encryption key. This key is something you will make yourself, that cannot be changed or retrieved. It should be something that is not used anywhere else and documented in a secure location and not given out to anyone.


Notes: The authorizenet module uses a secure curl connection via port 443. Ensure your server is running compiled curl with ssl support.

Authorizenet is an onsite processor, your customer's credit card information will be stored in your database. Make sure you have a SSL Webcert installed.


BluePay