What's new in version 2602.0.0.0

Aptean Pay  •  Release Note  •  7/22/2026  • 

Features

With the features added in this release of the Aptean Pay extension, you can now trace payment requests and payment authorizations back to their originating sales order and the customer's purchase order reference.

  • The Aptean Pay Requests Queue page now includes Order No. and Customer PO No. fields, populated from the Order No. and External Document No. fields on the posted sales invoice.

  • The Aptean Pay Pre-Auth Queue page now includes a Customer PO No. field, populated from the External Document No. field on the sales header.

  • The orderNumber and customerPONumber values are now included in the API payload sent to Aptean Pay for both payment requests and pre-authorized payments, ensuring Aptean Pay's records stay consistent with Business Central even when these values are blank.

Enhancements/Modifications

With this release of the Aptean Pay extension,

  • On the Sales Order/Invoice page, changing the External Document No. field is now blocked while an active payment authorization exists on the Aptean Pay Pre-Auth Queue (Payment Status New or Created). To make this change, you must first cancel the payment authorization using the Cancel Payment Method action.

  • If the related Aptean Pay Pre-Auth Queue record has a Payment Status of Expired, changing the External Document No. field is allowed, and the Customer PO No. field on the Aptean Pay Pre-Auth Queue record is automatically updated to match, so that a subsequent re-authorization uses the correct value.

UI/UX changes

The Order No. and Customer PO No. fields have been added to the Aptean Pay Requests Queue page. The Customer PO No. field has been added to the Aptean Pay Pre-Auth Queue page.