Accounts Receivable - Appendix B - Customer Web Portal for Credit Card Payments

 

Overview

 

External to AddonSoftware

AR staff can accept credit card payments from customers (card not present) via the Credit Card Payment additional option on the Customer form (AR > Inquiry and Maintenance > Customers). When configuring for AR staff payments, can choose to use either the J2Pay multi-gateway Java library that ships with Addon, or a hosted page from either Authorize.net or PayFlow Pro (PayPal). J2Pay supports:

  • Authorize.net

  • BillPro

  • EasyPay

  • NMI (Network Merchants, Inc.)

  • Payeezy

  • PayFlowPro

Customers can also pay their own invoices online. Invoices and statements contain a URL at the bottom for the login page, and customers who receive invoices/statements via email will see the URL as a convenient link to take them directly to the Payment Portal.

  • First time users need to register, supplying a username, first/last name, email address, and the customer number for which they're paying.

  • Upon registering, an email is sent to the address specified in the Customer Master form's Online Pay Auth Email field. The email includes a link for the authorizing party to click in order to confirm the registration.

  • Once confirmed, the user is emailed a randomly-generated password and a link back to the login page.

  • On first login, users are prompted to change their passwords. When successfully logged in, users are presented with a payment form for the corresponding customer. Invoices can be marked via the checkboxes, and the payment amount can be overridden if not paying the entire invoice. Click the green arrow or the Submit button to confirm payment (Note that this form will close if left up for > 60 seconds.). Users are then taken to either the Authorize.net or PayFlow Pro hosted payment page where they can provide credit card information via the hosted page secure servers.

  • No matter how credit card payments are being accepted, you will need merchant account(s) that will interface w/ at least one of the supported gateways. If setting up Online Customer Payments, must use Authorize.net or PayFlo Pro (PayPal) hosted pages. If setting up AR staff payments (AR staff taking customer's credit card info over the phone), can use any of the supported gateways, and have the option of using the J2Pay API, or a hosted page.

Customer Online Credit Card Payment

 

  • No matter how credit card payments are being accepted, you will need merchant account(s) that will interface w/ at least one of the supported gateways. If setting up Online Customer Payments, must use Authorize.net or PayFlo Pro (PayPal) hosted pages. If setting up AR staff payments (AR staff taking customer's credit card info over the phone), can use any of the supported gateways, and have the option of using the J2Pay API, or a hosted page.

  • You will also need to set up an account with selected gateway(s) (i.e., on their web site) to get credentials (login/password). It is STRONGLY recommended (and may be required by the payment gateway) that you begin with a test account, then create the live account after successfully testing transactions.

  • If using Authorize.net or PayPal hosted pages, you need to go to their website(s) to configure the Authorize webhook and PayPal responses. PayPal also allows you to configure which fields must be filled in on the hosted page, as well as some options for how the payment pages look. Refer to Authorize.net or PayPal documentation for specifics on their hosted pages, and to the Payment Gateway Parameters documentation for information on constructing the URL's needed for the responses. In general, follow these examples:

    • Authorize.net login > Account > Webhooks

      • Name: descriptive name such as "Addon Payment"

      • Endpoint URL: example (https://<server>/<context_path>/<servlet_URL_Mapping>): https://test.server.com/aon_install/AuthorizeWebhook

      • Status: Active (set inactive if not testing or live)

      • Payment event: net.authorize.payment.authcapture.created

    • PayFlow Pro > PayPal Manager Login > Hosted Checkout Pages > Setup

      • Error URL: https://test.server.com/aon_install/PayPalError

      • Silent Post URL: https://test.server.com/aon_install/PayPalSilentPost

      • Silent Post Failure URL: https://test.server.com/aon_install/PayPalSilentPostFailure

  • If using hosted pages (Authorize.net or PayFlow Pro from PayPal)

    • Server must be accessible via the internet, have a public DNS name, and a valid SSL certificate for that public DNS name.

    • Use SSL Configuration in Enterprise Manager to enter the certificate path and password for ports 8443 and 443.

In AddonSoftware

 

  • Create a Context to be used by the online CreditCardLogin and related pages, as well as the servlets processing the gateway responses. This context is created automatically when Addon is first launched, as part of the Create SPROC Definitions process, and is named to match the database name, but in lower case. NOTE that once the context is created, you must start it manually through EM > Web > Context Configuration.

  • Set up an Email Account (Barista Administration > Document Management > Email Accounts) for use when emailing users and authorizing parties during the registration process.

  • Call up the ARS_CC_CUSTPMT Report Control Document (AddonSoftware Administration > Report Control > Report Control Documents) and edit it to contain the Email Account.

  • Enter gateway config (login/password, server name, i.e., the public DNS name) for any gateways being used via Accounts Receivable > Inquiry and Maintenance > Parameters > Payment Gateway Parameters. Attributes containing <*token> must be replaced with values supplied from the gateway.

  • Double check that BATCH_NO, DEPOSIT_ID, and CREDIT_TRANS_NO sequence number records exist (Barista Administration > Maintenance > Sequence Numbers).

  • For AR Staff form (making payments from Customer Master > Credit Card Payments option)

    • Set up one or more Cash Receipts codes for credit card processing (Accounts Receivable > Inquiry and Maintenance > Cash Receipt Codes).

      • POS Cash Type = Credit Card (P)

      • Set other fields as described in Cash Receipts Code documentation (link to it).

    • Set up corresponding AR Credit Card Parameters (launch from AR > Inquiry and Maintenance > Parameters > AR Credit Card Parameters, or as additional option from Cash Receipts Code form)

  • For Online Customer Payments

    • Set up one Cash Receipts code for online payments

      • POS Cash Type = Credit Card (P)

      • Set other fields as described in Cash Receipts Code documentation (link to it)

    • Set up corresponding Online Customer Credit Card Parameters (launch from AR > Inquiry and Maintenance > Parameters > AR Online Customer Credit Card Parameters, or as additional option from Cash Receipts Code form). Remember to use the Configure Web App additional option to create the Web Applications and automatically supply the Payment, Registration, and Password Recovery URLs.

    • Create an "application" username of your choice via Barista Administration > Security > Users. This user and password will correspond to the [APP1]/[APP2] Configuration Records described below.

      • Set the role for the "application" user to CCONLINE

      • After creating the user, select Change Password from the additional options to enter/confirm the desired password.

Barista Users

 

  • Add the "application" user/password to the Barista Configuration (Barista Administration > Maintenance > Configuration Records) as APP1 and APP2. The username entered for APP1 must be uppercased, while the password is entered for APP2 "as is." This user/password is referenced in the Web App configuration parameters and is responsible for launching the Online Payment Form.

Barista Configuration Records

 

    • Add any user who should be notified about exceptions encountered during online payment processing to the CCONLINE role (and make sure their email address is in the Barista users table). Members of the CCONLINE role will receive an email if the online payment process encounters errors, such as missing configuration or an unanticipated error from a gateway.

  • On an ongoing basis, call up any customer for which you want to enable Online Credit Card Payments, check the "Allow Online Payments?" box and fill in the email address of the customer contact who will be authorizing online payment.

    • After marking a customer for online payment, confirm that the Report Control Recipients record  for that customer (Report Alias =  ARS_CC_CUSTPMT) has been created (AddonSoftware Administration > Report Control > Report Control Recipients).



______________________________________________________________________________________

Copyright BASIS International Ltd. AddonSoftware® and Barista® Application Framework are registered trademarks.