| Info |
|---|
LearningBuilder can collect payments from end-users in many different ways. Adding integrations for gateways not listed here is generally possible with minor innovation. |
...
For more information on establishing a merchant gateway, see below.
Supported Gateways
Payflow Payments Pro | This service uses PayPal as the payment gateway and payment processor. PayPal performs all transaction processing prior to depositing into the client's merchant account. Customers using Payflow Payments Pro sign up for PayPal Pro service, which is around $30/month (as of July 2012). PayPal Payments Pro uses the concept of a "sandbox" for performing test transactions and a separate, live site. Payment processing is available through Secure Post mode but refund processing through LearningBuilder is not supported.
| ||||
Payflow Pro | This service uses PayPal as the Payment Gateway but uses a third party payment processor. This interface is the result of PayPal's purchase of Verisign, which first developed the Payflow Pro product. PayPal now uses it for advanced interfaces that use other payment processors. Payments and refunds are both functional, and are supported in both the Secure Post and Hosted Pages iFrame Checkout configurations.
| ||||
Authorize.Net | Authorize.Net is an alternative gateway to PayPal. If the organization has already established a relationship with Authorize.Net and wishes to use this gateway, LearningBuilder can be configured to support it. Payment processing is available but refund processing through LearningBuilder is not supported. This Payment Gateway is functional in Secure Post and 3-Step Handshake Checkout Modes.
| ||||
Moolah | Moolah is an alternative gateway which is focused on Non-Profit organizations. The support of this gateway was introduced in LearningBuilder 8.10 and is only functional in the 3-Step Handshake Checkout Mode. | ||||
USAePay | USAePay provides a number of payment solutions. Currently, LearningBuilder supports the "2-Step Client-Side" mode only for this gateway. | ||||
Alabama Interactive | Alabama Interactive is the a payment gateway used by BELS. licensing agencies in Alabama. It offers both a “Hosted Pages” and “Hosted Pages iFrame” option, but LearningBuilder only supports the “Hosted Pages” checkout mode for this payment gateway. at this time.
The following App Config values should be obtained from the client:
There is an AlabamaInteractiveMode setting that can be set to Test or Live. This setting determines which Credentials and URLs are used. These URLs are also set in App Config, although the Product Defaults should meet your requirements. |
Gateway / feature support matrix
| Info |
|---|
Payment gateways support different features. If a feature is not supported, it may be because the gateway does not support it |
Vendor |
| Checkout Modes | Supported Features | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Secure | Hosted | Hosted | 3 Step | 2 Step | Full | Partial | GL | Discount | Responsible Party ‘Pending’ Payments (aka Bulk Employer Payments) | Organization ‘Bulk’ Payments | ||||
Payflow Payments Pro | PayPal |
|
|
|
|
|
|
|
|
|
|
|
| |
Payflow Pro | PayflowPro |
|
|
|
|
|
|
|
|
(Added with 10.0 Release) |
( |
|
| |
Moolah | Moolah |
|
|
|
|
|
|
|
|
|
|
|
| |
Authorize.Net | AuthNet |
|
|
|
|
|
|
|
|
( |
|
|
| |
USAePay | USAePay |
|
|
|
|
|
|
|
|
|
|
|
| |
Alabama Interactive | AlabamaInteractive |
|
|
|
|
|
|
|
|
|
| TBD in 10.8.0 | TBD in 10.8.0
|
|
Checkout Modes
The CheckoutMode App Config setting controls the user’s experience during checkout.
...
Method | App Config value for
| Description / PCI Compliance | ||||
|---|---|---|---|---|---|---|
Secure Post |
| Payment forms are hosted by LearningBuilder. Payment card data is transmitted to LearningBuilder, which then submits the payment transaction to the gateway.
| ||||
Hosted Pages |
| When the user begins checkout, their browser is redirected to the payment gateway’s website. The credit card form is hosted by the gateway and the entire transaction occurs externally to LearningBuilder. The user is redirected back to LearningBuilder after the transaction is complete.
The main drawback to this approach is that the payment gateway’s checkout form often does not look exactly like LearningBuilder, resulting in a disjointed user experience. On the other hand, innovations made by the gateway to their checkout experience (such as adding support for new payment types) can be immediately available to end users without requiring changes to LearningBuilder. | ||||
Hosted Pages |
| This is similar to Hosted Pages, except that instead of redirecting the user to a 3rd-party checkout process, the 3rd-party checkout form is displayed in an iframe within LearningBuilder. This often results in a more seamless user experience because the user never leaves the context of the LearningBuilder site.
| ||||
2 Step Client-Side |
| In this mode, the checkout process is implemented within LearningBuilder except for the credit card processing. When the user submits the form containing credit card data, the form submits directly to the payment gateway which handles the transaction and then redirects the user back into LearningBuilder.
See the USAePay documentation for more information | ||||
3-Step Handshake |
| After the user enters their credit card information, LearningBuilder submits that data directly to the payment gateway as a background post. The user’s browser does not navigate away from LearningBuilder. The gateway securely stores the credit card data, without processing a transaction, and returns a token that can be used to reference those saved credentials at a later time. The user then finishes the checkout process in LearningBuilder, which includes a “checkout confirmation” page. Once the user confirms their intent, LearningBuilder makes a second background post to the gateway. This post includes the transaction details (amount, etc) plus the token that was received earlier. The payment gateway then uses the stored card data to complete a transaction.
|
PCI Compliance
As of 10.6, LearningBuilder does not support any payment gateways or checkout modes in which payment card data is transmitted to or processed by LearningBuilder. In order to maintain PCI compliance, LearningBuilder cannot have anything to do with credit card details.
...
Obtaining an Internet Merchant Account
To accept credit cards over the Internet, you need a special account called an Internet Merchant Account. If PayPal is your merchant bank, you do not need the Internet Merchant Account. Your account provider or merchant (acquiring) bank works with a PayPal-supported credit card processor. Examples are First Data, TSYS Acquiring Solutions (formerly Vital Processing Services), and Paymentech. To accept live credit cards, provide details about your account to PayPal during the "Go Live" part of enrollment.
An Internet Merchant Account is a different type of merchant account. It has additional risks associated with card-not-present (e-commerce) transactions. It is different from a merchant account used for face-to-face/card-present (in-person) retail transactions. Obtain an Internet Merchant Account even if you already accept credit cards at your location. To apply for an Internet Merchant Account, contact your merchant (acquiring) bank.
...