PayWeb360 1.17 is now available in production. The purpose of this release is to introduce 1 new feature (Fee Waiving), 4 enhancements (Payment History, Original Creditor, User Profile Navigation, Session Expiration), 2 new configuration options (Automatic Payments, Payment History) and 4 fixes (2-Factor Authentication, Payments-in-Full, User Events and Email Domain Extension).
Fee Waiving
Fee Waiving is a new feature that, when enabled, will allow users to waive a convenience fee when signing on as an agent.
Payment History
Payment History is an existing screen that presents both upcoming and previously processed payments.
Enhancement
Payment History will now include ACH returns as part of this release.
New Configuration Option
Prior to this release, the account associated with the payment would need to be present within client reference data (a.k.a. CIF) for it to be included. Now, as part of this release, PayWeb360 can be configured to include payments that are associated with an account ID that is not present within client reference data.
Original Creditor
Original Creditor is an existing field within the Account Detail screen. Now, as part of this release, the original account ID can be presented underneath it. In order to take advantage of this enhancement you will need to include the original account ID within client reference data (a.k.a. CIF).
User Profile Navigation
User Profile is an existing screen that enables users to view their personal details and electronic communication settings. As part of this release, we have improved the navigation to this screen from the Dashboard.
Before | |
After |
Session Expiration
Prior to this release, a session would automatically expire after a period of inactivity. Now, when a session is about to expire users will be warned and given the opportunity to extend it.
Automatic Payments
Automatic Payments is an existing feature that enables users to schedule a series of payments to pay off a balance over time.
Before | Prior to this release, users were able to view an itemized schedule when setting up and managing an automatic payment.
|
After | Now, as part of this release, the itemized schedule can be hidden in cases where it may change in response to a change in the balance. Users will still be able to view a summary including the recurring amount and frequency when the itemized schedule is hidden. |
Email 2-Factor Authentication
Email 2-Factor Authentication (2FA) is an existing feature that, when enabled, requires a user to log in with something they have (code) in addition to something they know (password). As part of this release, we fixed an issue that caused an old email address to pre-populate when opting into 2FA
Payments-in-Full
Payment-in-full (PIF) is an existing feature that enables clients to present pay-off plans that result in the balance being paid in full. As part of this release, we fixed an issue that impacted the date of the first payment within a pay-off plan.
User Events
User Events is an existing feature that records user activity within the site. Prior to this release, a bug caused some login failures to be recorded as successful, leading to inaccurate reporting. This issue has been fixed as part of this release.
Email Domain Extension
Prior to this release, PaymentVision enforced a 4 character maximum limit on the email domain extension (e.g.; .com, .org) when adding or updating an email address within the User Profile screen. Now, as part of this release, PaymentVision will allow up to 63 characters to better align our limit with newer domain extensions.