PayWeb360 1.19 is now available in production. The primary purpose of this release is to resolve technical debt. It includes fixes to 21 issues (Apple Pay, Linked Accounts, 2FA, Email Registration, Recurring Payments, Settlement Offers, Make Payment, Onboarding), enhancements to 2 features (Digital Wallets, Linked Accounts) and the promotion of 1 pilot service (Digital Wallets).
Digital Wallets
Digital Wallets is an existing feature that enables users to pay with a card stored within their iPhone (Apple Pay), Android or Google account (Google Pay) without having to re-enter their card information.
Settlement Offers
In addition to other one-time payments, users can now use Apple Pay or Google Pay when paying a lump sum settlement.
Discover
Users can now use any card brand with Apple Pay and Google Pay, including Discover.
ZIP Code Validation
Prior to this release, Apple Pay payments would fail in cases where the billing ZIP code on file was 9 digits as opposed to 5. 9-digit ZIP codes are now supported as part of this release.
Caching
Prior to this release, a caching issue was causing ApplePay or GooglePay to be pre-selected even after being disabled within the tenant configuration. This has been fixed, as part of this release.
Pilot Program
Over the last several months, PaymentVision has run a small pilot program in order to gain operational experience with both Apple Pay and Google Pay. As part of this release, PaymentVision is ending its pilot program and will make the two payment methods available to all clients.
Linked Accounts
Landing Page
Prior to this release users landed on the Make Payment page after logging in. Now, as part of this release, PayWeb360 can be configured to land on the Dashboard in cases where the customer has more than one account.
Master Account ID
Prior to this release, accounts were linked when the Master Account ID was empty as opposed to NULL. Now, as part of this release, customer accounts will only be linked when the Master Account ID is populated with an actual value.
Payment History
Show More Button
Prior to this release, the show more button would disappear on the Payment History page after canceling a payment plan if the record count exceeded 10. This has been fixed, as part of this release.
Sorting Button
Prior to this release, series payments would disappear after sorting if the record count exceeded 10. This has been fixed, as part of this release.
Record Limit
Prior to this release, Payment History was limited to 10 payments in some configuration scenarios. That limit has been removed, as part of this release.
Series Records
Prior to this release, the first processed payment within a series would be presented as opposed to the next scheduled payment. This has been fixed, as part of this release.
Canceled Payment Plans
After canceling a payment plan it would still show up in payment history as an empty plan. This has been fixed, as part of this release.
Auto-generated Account Reference Codes
Prior to this release, recurring payments were not appearing within Payment History in cases where the account reference code was auto-generated and the customer had 4 or more linked accounts. This has been fixed, as part of this release.
2FA
Prior to this release, a bug was causing the 2FA setting to appear toggled on in cases where a customer initiated the registration process but failed to enter a valid code. This issue has been resolved as part of this release.
Email Registration
Error Handling
Prior to this release, users would be logged out after entering an invalid code more than two times while registering for email notifications. Now, as part of this release, the user will remain logged in.
Re-opting in
Prior to this release, users were unable to re-opt into email notifications using an email address they previously opted out. Now they can, as part of this release.
Recurring Payments
Timeouts
Prior to this release, customers would receive a failure message in cases where a payment plan was successfully created but timed out before assembling a response. Now, as part of this release, customers will receive a success response in the event of future timeouts.
Recurring Payment Amount
Prior to this release, the recurring payment amount and convenience fee would not update after changing the payment amount and navigating back to the Verify Payment screen. This has been fixed, as part of this release.
Payment Type
Prior to this release, a recurring payment would display as a one-time payment when the number of payments exceeded 500 and the browser encountered latency. This has been fixed, as part of this release.
Settlement Offers
Expired Offers
Prior to this release, the settlement offer call-to-action was being presented in cases where a lump sum offer expired. This has been fixed, as part of this release.
Multiple Future-dated Payments
Prior to this release, settlement plans were allowed even when a future-dated payment already existed and PayWeb360 was configured to not allow more than one future-dated payment. This has been fixed, as part of this release.
Call-to-action
Prior to this release, a settlement offer would not be presented in cases where a customer was enrolled in a payment plan, as expected. However, it would also not be presented after cancelling the plan. Now, as part of this release, a settlement offer will be presented after canceling a payment plan.
Make Payment
Payment Amount Alert
Prior to this release, the min max payment amount error was presented upon landing on the Make Payment screen in a certain configuration scenario when a payment method was not already on file. This has been fixed, as part of this release.
Card Icon
Prior to this release, the payment card icon would disappear from the Make Payment screen after viewing the payment methods on file and preserving the selected method.
Onboarding
Prior to this release, an extra tab click was required to navigate through the last step of the onboarding process. This has been fixed, as part of this release.
