| 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. See also: Payment and E-Commerce Features |
...
Payflow Pro | PayPal offers multiple payment products, but the only one that is both PCI compliant and fully supported by LearningBuilder is Payflow Pro. For more information on the other PayPal offerings, see PayPal Payment Gateways 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. LearningBuilder supports the PCI-compliant Three-Step Handshake checkout mode.
| ||||||
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 Three-Step Handshake Checkout Mode.
| ||||||
USAePay | USAePay provides a number of payment solutions. Currently, LearningBuilder supports the "Two-Step Client-Side" mode only for this gateway.
| ||||||
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 |
|---|
This document outlines known issues, outstanding items, or extra notes as they relate to most or ALL payment gateways. For gateway-specific documentation, refer to Payment Gatewaythe gateway-specific documentation. |
In LearningBuilder versions 11.0.1, 11.0.2, and 11.1.0, 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 server System JIRA serverId 80a5de98-58ff-3b59-a4bd-e013083b8a1d key LB-2716 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 server System JIRA serverId 80a5de98-58ff-3b59-a4bd-e013083b8a1d key LB-2653 There is a small window of time within the ThreeStep Checkout Mode where a duplicate payment is possible. Refer to https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/3099492370/Moolah+-+Known+Issues+Observations#Duplicate-Payment-Race-Condition and https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/3099656228/Authorize.Net+-+Known+Issues+Observations#Duplicate-Payment-Race-Condition for more information. This window also exists in the PayflowPro/SecurePost configuration. Refer to https://heuristicsolutions.atlassian.net/wiki/spaces/DOCS/pages/3101524085/Payflow+Pro+-+Known+Issues+Observations#Duplicate-Payment-Race-Condition for more information.
If a site app pool is recycled before payment is fully confirmed, the payment will redirect to a post-processing error page and a web error email (“The same key was already used for another template!”) will send. This occurs within the ThreeStep Checkout Mode and with the PayflowPro/SecurePost configuration.
...