| Setting Up Your Store > Setting Up Your Payment Gateway |
Payment Gateways
|
Related Topics: Payment Methods | Transaction Modes | Void, Capture, Refund Orders | Gateway Settings |
Overview:
What is Payment Gateway?
A payment gateway is what acts on your behalf (as a store owner) to collect funds from a customer, authorize their credit card, and transfer funds into your bank account. In other words, an online credit card processing system. You must use a payment gateway to accept credit cards via an online store. If you do not have a payment gateway selected, the first place to call is your business bank, and ask them to get you setup to accept internet credit cards. They will advise you on costs, and which gateways they work with. These gateways will usually be on our list below.
To Access: Login to the Admin Site. Click Home. Under Common Links, click Gateway Settings.
The following
payment gateways are currently supported: (Click on each link for
further information):
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In general, AspDotNetStorefront needs to know the following:
Payment methods you want to accept (AppConfig:PaymentMethods).
Payment Gateway you will be using (AppConfig:PaymentGateway).
Transaction Mode for credit cards (AppConfig:TransactionMode).
Payment Gateway Configuration Parameters (e.g. AppConfig:AUTHORIZENET_X_LOGIN).
The default mode after install is in TEST mode. Consult your payment gateway information on their test mode instructions and test credit card numbers to use. Before going into production, you should set AppConfig:UseLiveTransactions=true and perform final testing. Also, PayPal does not have a "test" mode either.
How to install Payment Gateways:
- Go to Misc and then click AppConfig Parameters.
Use the Config Search box and type PaymentGateway. Then specify the gateway to be used by setting the AppConfig:PaymentGateway parameter (e.g. AUTHORIZENET). See above for the supported Gateways.
- You must also then set various AppConfig settings that are specific to that gateway (such as userid, password, etc).
- See the AppConfig parameters section for your chosen gateway (e.g. AppConfig:AUTHORIZENET_X_LOGIN, etc).
- By default, AspDotNetStorefront is set to use the MANUAL gateway on first installation.
You can add support for gateways not listed above if you want to, but it requires adding some additional code to the storefront. We can also add gateways if required for a nominal fee.
NOTE: VeriSign and LinkPoint require that the storefront be COMPILED against their COM interface. We do this by default. If you are not using those gateways, you can disable their code by commenting out the #define VERISIGN or #define LINKPOINT lines at the top of the verisign.cs and linkpoint.cs files (In the ASPDNSFGateways directory), and recompiling the storefront.
To use Verisign and Linkpoint also, you MUST install their SDK's on the server. Please consult their documentation on how to do this. We do NOT offer technical support on the installation of their SDKs. Your hosting company can also assist you as needed to install their SDKs on hosted servers.
After your site is installed, you should request a SSL certification from your hosting provider. We STRONGLY recommend that you get a dedicated SSL certificate tied to www.yourdomainname.com. We can work with a shared SSL certification, but it has complications!
Typical costs for SSL certs are from $50 to $99 per YEAR. These are available from a number of sources, but you should usually request this via your hosting company.
NOTE: DO NOT TELL THE STORE SITE TO USE SSL UNTIL YOU ARE ABSOLUTELY SURE YOUR SSL CERTIFICATE IS INSTALLED. You can test if it is installed by invoking your store home page via https, e.g. https://www.yourdomainname.com. If that works, your SSL cert is installed.
Once your SSL cert is installed, you can tell the store site to use it by setting:
AppConfig:LiveServer=yourdomainname.com
AppConfig:UseSSL=true
AppConfig:RedirectLiveToWWW=true (to match your SSL cert on www.yourdomainnamename.com)
When you set UseSSL to true, the store, and admin site will start to use it. The store goes secure on the cart page, address pages, signin pages, etc. It STAYS secure from there on out. Why? Because customers who see the lock icon appear get nervous if it later disappears! But doesn't this cause the site to run slower...yes, a very tiny bit, but you will never notice the difference, and it's more important to keep your customers feeling safe!
If you have turned on SSL, and you can no longer access your admin site, you must manually edit the database AppConfig table and set UseSSL=false. You cannot turn off SSL from any web page on the site!
See also Enabling SSL.
To turn your Payment Gateway to Live Mode:
After enabling your SSL and setting the necessary AppConfigs to run your store on Live mode, then you must also turn ON your payment gateway. By doing so, you can process the credit cards on live mode. Below are the quick and simple steps to turn ON your payment gateway:
Login to the admin site. Go to Misc and then click AppConfig Parameters.
Set the AppConfig:UseLiveTransaction to TRUE and AppConfig:UseSSL to TRUE and then save.
Click on HOME. Then under COMMON LINKS, click Run Config Wizard. This will allow you to setup your payment method and payment gateway.
Click on "Use Live Transactions" to YES. Make sure you had set the AppConfig:UseLiveTransaction to TRUE.
Then click "Use SSL" to YES. Make sure you had set the AppConfig:UseSSL to TRUE (Click here to understand why you have to turn ON your SSL)
Submit the settings.
Click Reset Cache.
Important Reminder: Always perform Reset Cache when you make changes in your AppConfig Parameters.
System Requirements | Security Best Practices | Support & Upgrade Contracts | Downloads | Contact Us
Copyright © 1995-2006 All rights reserved.