Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

PayCloud - Release Notes

Table of Contents
maxLevel3
exclude10.03.16 - Releases

Enhancements

Club Admin Features

Reports - Scheduled Payments

      • As a club Admin, I would like to see all the scheduled payments within a date range.

        Use Cases: Previously, Scheduled Payments were available to view by the individual user. Now, the new Scheduled Payments reports page shows all upcoming scheduled payments for the club that have not been processed. The scheduled payments report shows member name, number, account name, payment date, amount, and if it is a One Time or Recurring payment. All columns, with the exception of Amount, are filterable and the Date Picker can be used as a search option.

Image Removed

Image Removed

    • Schedule future or recurring payment user is forced to select a current account or enroll a new account before Payment information fades into view.

    Use Cases: Previously, Payment Method, Payment Amount, and Schedule were shown on the Schedule a Payment page, allowing for an error that cleared out previously entered information. Now, Users must choose between making a payment from a current account or enrolling a new account before the highlighted section will be viewable.

  • Image Removed

Payments - Statement Balance

    • When the balance due is calculated it should account for payments after the statement date.

Use Cases: Previously, the full statement balance option from the Schedule a Payment and Make a Payment page did not account for payments already made within the month. Now, the full statement balance adjusts the full statement amount if any payments are made in the same month; preventing overpayment.

Image Removed

Image Removed

Member Facing Features

Email Notifications

    • Email notifications sent from PayCloud have a subject line that begins with “Club Name - Payment Portal”.

Use Cases: Previously, Email Notifications for Scheduled Payments were labeled in the Subject line as Payment Portal - Club Name. Now, the subject line reads, Club Name then Payment Portal, allowing for easier recognition in the end user's inbox. Example below includes the Club name “trunk1”.

Image Removed

Bug Fixes

...

Fixed issue with statement sync error fails when multiple members with the same member number are found.

...

Fixed Issue where Member lookup and save does not trim the member number value.

...

Fixed issue when statements are synced login records are created.

...

Fixed issue with One Time Payment History, Scheduled Payments tab, and Upcoming Payments type by removing “-”.

...

ACH Widget - ETSv3

      • Account number control would only allow nine or more account characters. Account number field does not error with 5+ digit account numbers.

        Use Case: Previously, in the ETS ACH Widget, account number control needed to be nine digits or more to be successfully entered and submitted. Padded zeros were used to compensate. Now, settings have been updated to allow for accounts with five or more digits. This enhancement also includes moving the routing number text box before the account number.

      • Routing number is now placed before account number in ACH Widget.

        Use Case: Previously, the routing number was placed after the account number in the ACH Widget. Now, routing number is placed before the account number, echoing the end users bank information layout.

        Image Added

Bug Fixes

 

    • Removed ‘Manage Payment Methods’ for payment processors that don’t support saving payment accounts.
    • Fixed visibility of Elmah error logs – restricted for only authenticated users.
    • Fixed Sync transaction with processor button from transaction details.
    • Fixed ‘Save’/’Save and Close’ buttons on the Club Admin site that didn’t work.
    • Fixed Cancel buttons on the Club Admin site that didn’t go to the right page.
    • Fixed how duplicate ‘charged by members’ are treated when syncing statements, previously an error occurred and the statement was discarded, now we just associate the detail by member name(no tie to the dependent by ID) but save the statement (this was hotfixed to live on 22 Oct).

 

Downloadable Guide