...
|
|---|
Enhancements
Office - Batch Posting Integration
...
CE Payments
Settlements
- Adding payment processing fees to the settlement sync to CE Office.
Use Case: Prior to
Pending status being introduced, payments made in PayCloud were marked as Approved, and were captured in daily Office postings. With the pending status introduced in the prior release, payment batch postings no longer included the new Pending status payment types. This feature essentially causes the batch posting process to occur as it did prior to the release of the Pending status.- Adding payment processing fees to the settlement sync to CE Office.
Payments - Status
Updated Status for Declined transactions to be correctly recorded as declined instead of canceled.
Use Case: Previously, declined transactions were listed with a canceled status. Now, declined transaction are properly labeled with an appropriate declined status.
Payments - Statements
Added functionality in PayCloud to now reject statements sent from CE Office outside of the Keep Payments range for the Club.
Use Case: Previously, PayCloud would sync statements from CE Office beyond the Keep Payments range set by the Club. Now, the PayCloud system recognizes the Keep Payments range set for the Club and will not sync payments that fall outside of that range.
Bug Fixes
Fixed an issue with Club & Club Admin sites when certain values could not be read from the settings cache, causing unintended scheduled task failures.
Fixed an issue causing an exception for Members who did not have a statement for the current period but were enrolled in AutoDraft.
Fixed an issue with hiding the Save button when deleting the last member from the AutoDraft table.- processing fees being visible in the bank reconciliation, Clubs would not see individual fee values. Now, Clubs can account for each processing fee in their Bank Reconciliation.
For Example: $1,000 payment was made by a Member, $4 of this payment accounted for fees, and $996 went to the club. When the Club views their Bank Reconciliation, they can see that $4 of the payment went to their Fees account and $996 went to Member Dues, instead of the non-descript $1,000 payment from the Member.
Duplicate Payments
Added an ‘idempotencyID’ to payment related API calls to prevent the same request from being processed twice.
Use Case: Previously, there was no process in place to avoid duplicate payments, Member Accounts, Account enrollments, etc. Now, an ID has been assigned to each of these actions and the system recognizes not to process or complete duplicate ID numbers.
Credit Card Payments
Added new ‘Hosted Fields’ credit card tokenization form for CE Payments.
Use Case: Now that Credit Card Tokenization has been instituted, the Account Enrollment form for credit cards has been updated to reflect Major Credit Card Recognition and color coded validity.
For Example: Green color coded information is valid, red shows an invalid entry. Also, the Credit Card Account Enrollment Form recognizes the Credit Card carrier.
Payments - Scheduled Payments
Changed the way full Statement Balances are calculated for one time or recurring payments scheduled on the last day of the month.
Use Case: Previously, A Payment scheduled for May 31st will look for May’s statement balance, which would mean the payment wouldn’t fire until Office ‘Month End’ processing for May has happened. Now, PayCloud always uses the statement that was posted in the previous month. The example Payment scheduled for May 31st will look for 30 April’s statement balance.
Bug Fixes
Fixed an issue where the ‘Keep Statements For’ setting to ‘Keep All Statements’ was incorrectly maxing out at Keep 12 months instead.
Fixed many issues surrounding duplicate member numbers at Clubs, and made changes to prevent the most common causes of duplication
- Fixed an issue with Firefox’s display of stacked date and time picker controls.