Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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.

...

Payflow Payments Pro
(aka PayPal)

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. 

Warning

As of February 2021, this gateway is disallowed by policy because it does not support a PCI-compliant payment option. This gateway will be fully removed from the software in an upcoming release.

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.

Info

Required Configuration: The client’s gateway account must be configured to use the “Silent Post” feature to prevent orphaned payment records in LearningBuilder. In the Payflow Pro Manager site, configure the account like so:

  • Use Silent Post: enabled

  • Void Transactions That Fail Silent Post: enabled

  • Silent Post URL: blank

See PayflowPro Silent Post for more details.

Warning

As of February 2021, using this gateway in “Secure Post” mode is disallowed by policy because it does not support a PCI-compliant payment option. Use “Hosted Pages” mode instead. The “Secure Post” mode will be removed from the software in an upcoming release.

Note

Please use LearningBuilder version 11.0.1 and greater in the 11.0.x LTS Release Branch series. Previous versions of LearningBuilder are at risk of allowing duplicate payments or improper error handling.

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.

Warning

As of February 2021, using this gateway in “Secure Post” mode is disallowed by policy because it does not support a PCI-compliant payment option. Use “3 Step Handshake” mode instead. The “Secure Post” mode will be removed from the software in an upcoming release.

Note

Please use LearningBuilder version 11.0.3 and greater in the 11.0.x LTS Release Branch series. Previous versions of LearningBuilder are at risk of allowing duplicate payments or improper error handling.

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.

Note

Please use LearningBuilder version 11.0.3 and greater in the 11.0.x LTS Release Branch series. Previous versions of LearningBuilder are at risk of allowing duplicate payments or improper error handling.

USAePay

USAePay provides a number of payment solutions. Currently, LearningBuilder supports the "2-Step Client-Side" mode only for this gateway.

Note

Please use LearningBuilder version 11.0.3 and greater in the 11.0.x LTS Release Branch series. Previous versions of LearningBuilder are at risk of allowing duplicate payments or improper error handling.

Alabama Interactive

Alabama Interactive is a payment gateway used by licensing agencies in Alabama. It offers both a “Hosted Pages” and “Hosted Pages iFrame” option, but LearningBuilder only supports the “Hosted Pages” mode at this time.

Info

Required Configuration: The client’s gateway account must be configured to use the “Postback Service” feature to prevent unrecorded payments in LearningBuilder. For more information, see the configuration page.

Note

Unlike Payflow Pro, Alabama Interactive does not have a way to guarantee against unrecorded payments. If an error occurs while notifying LearningBuilder of a successful transaction, they will retry a set number of times and then send an email.

We recommend using one of the other gateways instead that offer more robust protections against unrecorded payments in LearningBuilder.

Note

Please use LearningBuilder version 11.0.1 and greater in the 11.0.x LTS Release Branch series. Previous versions of LearningBuilder are at risk of allowing duplicate payments or improper error handling.

...

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. 

...

  • In an isolated circumstance, a user is able to create duplicate transactions in AuthNet, USAePay, and Moolah. This issue has been resolved in 11.0.3. See

    Jira Legacy
    serverSystem JIRA
    serverId80a5de98-58ff-3b59-a4bd-e013083b8a1d
    keyLB-2716

  • AuthNet logging needs to be enhanced to make issue triaging easier. This has been implemented in 11.0.3. See

    Jira Legacy
    serverSystem JIRA
    serverId80a5de98-58ff-3b59-a4bd-e013083b8a1d
    keyLB-2696

  • If In AuthNet, if a Behavior related to Post Payment processing failed, the User was NOT correctly redirected to the correct confirmation page. This has been resolved in 11.0.3. See

    Jira Legacy
    serverSystem JIRA
    serverId80a5de98-58ff-3b59-a4bd-e013083b8a1d
    keyLB-2696

  • If a Payment Attribute is added to a role grant workflow with a success action that grants the role, successfully completing the payment does not redirect the Practitioner to an auto-started Learning Plan Instance (LPI). This is counter to the expected case, where normally granting oneself a role will redirect the Practitioner to the LPI associated with that role if the Learning Plan Definition is set to “automatically begin when eligible.” See

    Jira Legacy
    serverSystem JIRA
    serverId80a5de98-58ff-3b59-a4bd-e013083b8a1d
    keyLB-2653

  • There is a small window of time within the ThreeStep Checkout Mode where a duplicate payment is possible. Refer to Duplicate Payments within Moolah and Duplicate Payments within Authorize.net for more information.

...