Differences

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

--- admin_menu:payments:payment_gateways:start [2009/08/18 17:23]
jonyo added more limitations
+++ 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 27: / Line 28: @@
 Various buttons to configure, save, or cancel settings specific to each gateway.  If a gateway does not have a configure button, there are no settings specific for that gateway (this is usually the case for "manual" payment gateways such as cash or check).
+===== Current Payment Gateways Supported =====
+[[startup_tutorial_and_checklist:feature_configuration:payments:start|A list of available Payment Gateways is here]]
 ===== Configuring Payment Gateway Settings =====
@@ Line 50: / Line 54: @@
 <tip c n>**Note:** On some payment gateways, you need to use a special //test account//((In Paypal and Paypal Pro, this is referred to as a Sandbox account.)) when working in testing mode.  A few of the more popular payment gateways that requires separate accounts for testing, are **Paypal**, **Paypal Pro**, and **Authorize.net**.
+Note that for **Authorize.net** things can get a little confusing as there are test accounts, and there are normal accounts placed in Test Mode, and the two are not the same.  See the table below for what setting to use for [[#Account Status]] according to what you are using:
+^ Authorize.net Account Type ^ Test Mode setting at Authorize.net ^ [[#Account Status]] setting in Geo Configuration ^
+| Normal Account | Normal | 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 62: / 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.
-  * **Linkpoint**
-    * The recurring billing can only last for 99 cycles.  So if you have defined one period to last a month, using Linkpoint, after 99 months the recurring billing will essentially be automatically canceled.
   * **Authorize.net**
     * Not able to check status on recurring billing automatically, so the refresh status button is not able to contact authorize.net to get updated status.
     * The cycle duration is limited to be minimum of 1 week (7 days), maximum of 1 year (365 days).  Make sure all durations are between 7 days and 365 days.
+    * Recurring billing will **not function** using a normal authorize.net account that is in **test mode**((**From Authorize.net FAQ answer**:  The ARB API does not function in Test Mode.  You need to disable Test Mode in your Authorize.net account settings.  To disable Test Mode please login to your account, click on “Settings”.  Click on the link for Test Mode and disable it by clicking the button titled “Turn Test Off”.)).  Note that a normal account put in test mode is different than having a test account meant for developer testing.
   * **Paypal**:  (**not** Paypal Pro):
     * Cannot cancel payments from software, recurring billing must be canceled on paypal.com website.
     * There is no ability to specify the "start date" for the recurring billing cycle.  If a user purchases a renewal for a subscription before the user's current subscription runs out, they will still start being billed right away.
+  * **Linkpoint** [Not considered recurring billing capable, see notes below]
-===== My Payment Gateway Does Not Appear in the List =====
+    * 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.
-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