PayWeb360 v.1.4.1225.0 is now available in production. The purpose of this release is to fix 1 issue (Payment History), enhance 1 feature (Max Payment Amount) and make 4 improvements (Contact Info Call-to-Action, Automatic Payment, Card Type Not Accepted, Login).
Payment History
Payment History is an existing feature of the Dashboard and History page that presents the payment history on an account.
Before
Prior to this release, Payment History could include payments from other customers in cases where the Account Reference Code is the same. While this may be appropriate on a joint account it would not be appropriate on a non-joint account.
After
Now, as part of this release, a PaymentVision implementation user can configure whether Payment History includes all payments associated with the Account Reference Code or only payments associated with the Account Reference Code that belong to the customer.
Max Payment Amount
Max Payment Amount is an existing feature that prevents an end user from exceeding a maximum payment amount.
Before
Prior to this release, the maximum payment amount was either the balance, in cases where it was provided by the merchant, or a maximum payment amount defined globally by PaymentVision.
After
Now, as part of this release, the maximum payment amount can be defined at the merchant level by payee, customer, payment method or any combination of customer account criteria.
Contact Info Call-to-Action
Contact Info Call-to-Action is a feature of the PayWeb360 landing page that directs attention to the customer’s contact information in cases where information that is required in order to make a payment is missing.
Before
Prior to this release, when required contact information was missing, the end user would be presented with the following call-to-action.
After
Now, as part of this release, when required contact information is missing, the end user is presented with this call-to-action.
Automatic Payment
Automatic Payment is an existing feature of the Make Payment and Dashboard page that presents an automatic payment if it has been set up on a customer account.
Before
Prior to this release, the Make Payment and Dashboard page would only include automatic payments set up via PayWeb360. They would not include automatic payments set up via other sources (e.g.; PayWeb 2, PayAPI).
After
Now, as part of this release, the Make Payment and Dashboard page will include automatic payments set up via all PaymentVision payment channels.
Card Type Not Accepted
Card Type Accepted is an existing error that is presented when a user attempts to add a card and the card type is not accepted by the merchant.
Before
Prior to this release the following message was presented when a user encountered a Card Type Not Accepted error.
After
Now, as part of this release, this message is presented when a user encounters a Card Type Not Accepted error.
Login
Login is a performance improvement that aims to provide a login experience that lasts no more than 3 seconds and, in cases where it does, present progressive progress indicators.
Indicator #1
Indicator #2
Indicator #3
