Differences

This shows you the differences between two versions of the page.

--- admin_menu:payments:payment_gateways:start [2010/05/24 16:33]
jonyo fixed link
+++ admin_menu:payments:payment_gateways:start [2016/04/02 23:08] (current)
rdowen2016 [Payment Gateways]
@@ Line 3: / Line 3: @@
 Payment Gateways in the software can be configured **Site Wide** and **Per User Group**
-{{:admin_menu:payments:payment_gateways:payment_gateways.png|}}
+{{:admin_menu:payments:payment_gateways:payment_gateways.jpg|}}
 ===== Payment Gateway Columns =====
@@ Line 29: / Line 30: @@
 ===== Current Payment Gateways Supported =====
-The following credit card gateways are supported by the software.  Through these you can accept credit card payments once you have setup an account with them.  You must have an account that accepts payment over the Internet from ecommerce sites.  Many of them provide accounts where you must actually have the "card in-hand"...this is not that type of account.
+[[startup_tutorial_and_checklist:feature_configuration:payments:start|A list of available Payment Gateways is here]]
-  Authorize.net AIM - authorize.net (website)
-  Paytrace - paytrace.com
-  Linkpoint - linkpoint.com
-  Moneris - moneris.com (Canada)
-  Payflow Pro (purchased by Paypal) paypal.com
-  NoChex - nochex.com
-  Payment Express - paymentexpress.com
-  Paypal Standard - paypal.com
-Checkout - 2checkout.com
-  Worldpay - rbsworldpay.com
-  Paypal Pro (Website Payments Pro) - paypal.com
-  Payscape - payscapeadvisors.com
-  Netcash - netcash.com
-Some of the above gateways allow you to accept the credit card information on your site and communicate that information through "secure back channels" over the Internet while others force the client to their site where the credit card information is collected.  The client is then redirected back to your site after the payment is made.  You will need to decide what type of payment gateway you wish by researching them.
-As well as the above there are "local" payment gateways provided by the software like: Cash, Check, Money Order and Account Balance.
 ===== Configuring Payment Gateway Settings =====
@@ Line 76: / Line 58: @@
 ^ Authorize.net Account Type ^ Test Mode setting at Authorize.net ^ [[#Account Status]] setting in Geo Configuration ^
 | Normal Account | Normal | Live |
-| Normal Account | Test Mode | Live |
+| Normal Account | Test Mode((Recurring billing will **not function** using a normal authorize.net account that is in **test mode**.  See [[#Payment Gateway specific Recurring Billing Limitations]] section for more information on Authorize.net limitations.)) | Live |
 | Test Account((You can sign up for an Authorize.net test account from http://developer.authorize.net/testaccount/ if you wish.)) | Normal or Test | Testing Mode |
 </tip>
@@ Line 90: / Line 72: @@
 Some gateways require configuration changes on the //gateway side//((Not in the Geo admin panel, but rather at the payment processor's website, for instance the settings configured at paypal.com or authorize.net.)) to enable using recurring billing.  Refer to the documentation provided by the payment gateway processor regarding what is needed to handle recurring payments.
-**Notes On a Recurring Billing Orders**
+=== Notes On a Recurring Billing Orders ===
-  * Only 1 recurring billing item((Like a user subscription)) is able to be paid for at a time in the same recurring billing order.  This is because each item will have it's own recurring billing cycle and price that will have to be processed on its own.
+  * Only 1 recurring billing item((Like a user subscription)) is able to be paid for at a time in the same recurring billing order.  This is because each item will have its own recurring billing cycle and price that will have to be processed on its own.
   * If there is 1 or more payment gateway enabled that has recurring billing enabled, on the payment choices page only those gateways with recurring billing enabled will be displayed.
   * If there are no payment gateways that have recurring billing enabled, the order will be processed normally and no automatic renewals or recurring charges will be performed.  In the case of a user subscription, the user will only be charged one time, and after the duration is up the subscription will expire normally as if the user had canceled the subscription and let the time run out.
-  * Each payment gateway can have it's own "user agreement" used on the payment choices page, when processing a recurring billing order, be sure to set the user agreement text to comply with what is required by each payment gateway's terms of use and any applicable local or regional laws.  Not all payment gateways have this however, such as the Paypal payment gateway since the terms are defined when the user is taken to Paypal to check out.
+  * Each payment gateway can have its own "user agreement" used on the payment choices page, when processing a recurring billing order, be sure to set the user agreement text to comply with what is required by each payment gateway's terms of use and any applicable local or regional laws.  Not all payment gateways have this however, such as the Paypal payment gateway since the terms are defined when the user is taken to Paypal to check out.
-**Payment Gateway specific Recurring Billing Limitations**
+=== Payment Gateway specific Recurring Billing Limitations ===
 The limitations listed below are due to limitations in how each payment gateway works, these are not something specific to the Geodesic software.
@@ Line 110: / Line 92: @@
     * Recurring billing **disabled** at the code level, because there is no way to check on status of recurring billing, and Linkpoint does not send any signals when the status changes.  In other words, if user stops paying, the software would never know.
     * The recurring billing can only last for 99 cycles.  So if you have defined one cycle to last a month, after 99 months the recurring billing will essentially be automatically canceled.
-===== My Payment Gateway Does Not Appear in the List =====
-If the payment gateway does not appear in the list that does not mean that it can never be within the system.  Each payment gateway has their own way of communication.  Though some payment gateways may seem very close to another there are always differences that require something specific in their coding.  Any payment gateway can be added to the system as long at that payment gateway has a "portal" that the software can "communicate with" to pass information and get a proper response from to "approve" a transaction.  If the payment gateway you need has this ability it can most likely be added to the system as a viable payment option.
-The problem is that owing to each gateway's unique nature each gateway must be programmed into the system at the php code level.  We have done most of the work in creating a  new gateway when we recoded the 4.0 version.  Within the 4.0 version we moved most of the common php code used by all gateways out of the individual payment gateway integration files.  This leaves only the few unique pieces that each individual gateway needs to communicate with it's own gateway system.  If you wish to try to code this gateway yourself into the system and feel you have the required php skills look at the following file in your system:
-/classes/payment_gateways/_cc_template.php
-By looking at that file you should then be able to insert the necessary code to communicate with your payment gateway and receive the proper response our system needs.

Geodesic Solutions Community Wiki

User Tools

Site Tools

Differences

Page Tools