Module(s) affected: Cross Entity orders, Hosted Payment Formsįailed schedule job counts are now recorded to limit the number of times failed jobs run. Solution: Updated the Hosted Payment Form to send the payment form’s entity ID when the cart’s entity does not contain the payment method. Original System Design: Cross Entity order(s) should use the correct GL account when a payment is made in Staff View and Community Hub (CH). Hosted Payment Form update now use the correct GL account for Cross Entity orders.Īssociations encountered issues where a Cross Entity order was paid using a credit card, but the payment transaction debited the wrong entity’s GL account. Module(s) affected: Payment, Accounting, Community Hub If the card holder name exceeds 50 characters, the system will not record characters exceeding 50 but payments will continue to process, and this will be recorded in Nimble AMS. When entering credit card name details in CH and Staff View (SV), users will be limited to 50 characters. Solution: Enforced a maximum character restriction of 50 characters on Card Holder Name field. Original System Design: Payments recorded in processor should be voided if a CH user encounters an error, during a payment transaction.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |