How to configure LearningBuilder for AuthNet (LB Version 10.5.1)

...

...

Payments - General

EnableCreditCardValidation - Determines if the credit card entered is validated before submitting transaction.

This should be set to true, preferably.

ManualPaymentDocumentationFileTypes - Types of files that can be uploaded as payment documentation. This should be a subset of images that can be converted to PDF.

The product default should suffice, unless the client only wants to review specific file types. This configuration only matters if RequireAttachmentsWhenRecordingPayments is set to true.

PaymentAllowedCcTypes - List of allowed credit card types. This controls both what is visible on the checkout page. You must enter the values from the StringConstant attribute on the CreditCardTypesEnum. Invalid values are currently ignored. Valid values are listed in the CreditCardTypesEnum.

AuthNet’s website says they accept AmericanExpress, Discover, JCB, MasterCard, Visa; but their developer documentation says they also accept DinersClub, so unless the client specifically only wants to accept certain credit cards, the default value should suffice.

PaymentCheckoutMode - Which checkout mode to use for charge transactions - Possible options are: "SecurePost", "HostedPages", "HostedPagesIFrame", "TwoStep" or "ThreeStep".

In order to stay PCI Compliant, SecurePost may no longer be used. Hence the only acceptable checkout mode supported by Authorize.Net is 3-Step Handshake. See Payments and E-Commerce.

PaymentDocumentationFileLibrary - This is the ID of the File Library in which newly uploaded payment documentation files are stored. If EMPTY, the ability to upload documentation when recording a payment will be suppressed. PER HEURISTICS POLICY, in PROD environments this must point to an encrypted File Library. WARNING: Once initialized to a non-empty value, changing this to point to a different library will cause the 'view documentation' link to vanish to any payments referencing the original library. This can be resolved by manually updating the pre-existing files to belong to the new library instead. Please consult with the technical support team before changing this setting from one library to another.

Um… This seems empty for most clients, so…

PaymentEnabled - Enable to support payments. Disable if payments are not required.

This must be set to true in order to use AuthNet in LB.

PaymentGateway - Active Payment Gateway - AuthNet or AuthNetFake - PayflowPro or PayflowProFake - PayPal or PayPalFake - Moolah or MoolahFake. In 'SecurePost' PaymentCheckoutMode, the fake gateways support three simulated responses: 1. FirstName = MissingId: This will result in an Approval but no Transaction ID 2. FirstName = Decline: This will result in a Declined status. 3. FirstName = Anything else: This will result in an approval. In 'HostedPages', 'HostedPagesIFrame', or 'ThreeStep' PaymentCheckoutMode, the authorization is successful and marked as paid.

This must be set to AuthNet.

PaymentHistoryItemDisplayLimit - The number of transaction line items displayed on the payment history page before they get rolled up into 1 line item.

There doesn’t seem to be an actual numerical limit. However, the recommended limit is the default of 5.

RequireAttachmentsWhenRecordingPayments - Requires a user to upload payment documentation when manually recording a payment.

If set to true, then when a user records a payment, they will also be prompted to upload payment documentation.

...

At least, that’s what I’d THINK should happen. Upon testing… I don’t see that option, so what gives?

ShoppingCartItemDisplayLimit - The number of shopping cart items displayed on the checkout page before they get rolled up into 1 line item.

There doesn’t seem to be an actual numerical limit. However, the recommended limit is the default of 25.

VoucherUsageLockDurationInMinutes - The number of minutes that a Voucher code is locked as in-use when first selected for payment, to prevent multiple users from using the same code at the same time.

There doesn’t seem to be an actual numerical limit. However, the recommended limit is the default of 30 minutes. This setting only matters if the discount voucher feature is being used.

Payment - Authorize.NET

AuthNetApiLoginId - Test Credit Card: Visa 4007000000027

This is the merchant Account ID.

AuthNetLiveUrl - The fully resolved URL for the Autorize.NET API service for LIVE Transactions

This should stay as the product default.

AuthNetMerchantEmail - The email address used with Authorize.NET

What does this mean in context? Honestly, I have no idea. Most clients who use AuthNet either have it as the default or empty.

AuthNetMode - Determines whether transactions should be processed as Test transactions. Acceptable values are 'Test', 'Live' or empty.

And what does this mean? Most using 3-step have it as Live, but some have it empty. Does it matter? Those using AuthNet but SecurePost have some defaulted to test, but I guess payments still work. What gives?

AuthNetPassword - The Password needed for logging into the Authorize.NET API

How is this different from the transaction key? Is the product default fine?

AuthNetPublicClientKey - This is the key that is used for the 'ThreeStep' payment checkout mode. Obtain key from Auth.Net Merchant Interface: Account > Settings > Security Settings > General Security Settings > Manage Public Client Key

AuthNetTestUrl - The fully resolved URL for the Autorize.NET API service for TEST Transactions

This should stay as the product default.

AuthNetTransactionKey - Unique key provided by Client for using Authorize.NET API

See AuthNetPassword question

AuthNetTransactionMethod - Determines the type of transaction. This value should always be CC

AuthNetTransactionType - Deternines what actions Authorize.NET should take with the information provided. This value should be set to AUTH_CAPTURE unless client has specifically requested another method. Acceptable values are AUTH_CAPTURE or AUTH_ONLY

AuthNetVersion - The version of the Authorize.NET API that should be used.

This should stay as the product default.

Configurations for 3-Step Handshake (LB Version 10.5.1)

PaymentCheckoutMode

This must be set to ThreeStep in order to use 3-Step Handshake.

AuthNetPublicClientKey

This must be entered before 3-Step Handshake can be enabled. The client will need to provide the public client key. They can find it through their Auth.Net Merchant Interface: Account > Settings > Security Settings > General Security Settings > Manage Public Client Key.

AuthNetMode

This must be set to Live in order to use 3-Step Handshake.

AuthNetApiLoginId

This is the Account ID that the client will need to provide in order to log in to the Authorize.NET API. This should already be configured if the client is using AuthNet.

AuthNetPassword & AuthNetTransactionKey

...

Features Supported

Subpages