What's new in version 2.1.30204.0
Features
Close an unpaid Payment Request
You can now close an unpaid payment request when a customer asks to. It also allows you to close a record for which payment could not be processed and resulted in an error.
Resend a Payment Request with updated amount
You can now update the amount for a closed Payment Request and send to Merchant Portal with the same reference number.
Removed cash receipt journal restriction
In Aptean Pay Receipts Queue,you can now choose to Create Records in Journal for individual payment receipts even if there is no corresponding invoice present in the system. Earlier, if a record did not have a corresponding Invoice in Business Central, you were restricted from doing so. For more information, see Cash Receipt Journal Record without Invoice.
Table to control email and aptean pay mobile no. in staging environment
A new feature has been added in the staging environment where you can add a specific list of email IDs and mobile numbers. A record from Aptean Pay Request Queue can only be sent to the Merchant Portal if the email or mobile number field value is either blank or present in staging data table. This ensures that your customers won't be affected by any test scenario.
Miscellaneous Fixes
- In Aptean Payment Receipts Queue, the action Create Record in Journal has been modified to Create Records in Journal.
- The value in Message fieldhas a consistent formatting now - lowercase letters without full stop.
- In Aptean Payment Requests Queue, when a Payment Method fails, the Payment Method Status now reflects thestatus Error.
- If you change the Mobile Number on Sales Header, the Aptean Pay Requests Queue page will now reflect that changed number instead of the number entered initially on the Customer Card page.
- The Message field on Aptean Pay Requests Queue now displays the error message in every scenario. In the previous release, Message was not getting updated in some of the cases where Status was Error.