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.
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.
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.
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.
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
