New Functionality

There was no new functionality added to this release.

Issue Resolutions

If a Third Party App was configured for integration, it allowed Payment Entries to be created with no Business Central "Customer No." if the user had used the "Import From Stripe" routine to import customers, but then hadn't mapped the Stripe customer to a Business Central Customer. With the Payment Entry existing, it then wasn't possible to assign a Business Central Customer No. to the mapping. The extension now allows the Customer No. to be assigned if the value previously hadn't been set, even though a Payment Entry exists. It also now looks to the "Stripe Customer Mapping" table and doesn't import the Payment Entry if the Business Central Customer No. hasn't yet been specified.

An additional check for an email address on the Customer Card was stopping the Paylink from being added to a Posted Sales Invoice where the Stripe Customer had already been created at Stripe. This additional check was removed as it was not needed.

Coming Soon

There are no major changes planned.

New Functionality

We took the opportunity to add an additional Payment Method Filter option to the "Create Payment Batch" wizard (in line with a change previously made to our Astral GoCardless extension).

Issue Resolutions

The extension now targets Business Central Version 22.

A small change was required to make the extension compatible with the next major release of Business Central (Version 23). Microsoft have deprecated the 'Assisted Setup' codeunit and moved the functionality to a 'Guided Experience' codeunit, and so references to the older codeunit had to be removed.

For next major compatibility, we also had to remove a reference to the 'Email Feature' functionality. This was added by Microsoft so that code could identify whether the system was using the older SMTP emailing functionality or the newer Email Accounts functionality, but is now no longer needed, as all systems now use the Email Accounts functionality.

Coming Soon

There are no major changes planned.

New Functionality

We added a Stripe Terminal action to the Customer Card and Posted Sales Invoice Page. Stripe Terminal functionality is still in 'Preview'. If you would like to trial this, please reach out to us at support@Astral365.com.

Issue Resolutions

There were no issues to be resolved in this release.

Coming Soon

There are no major changes planned.

New Functionality

We have now added functionality for Stripe Terminal. However, this is a pre-release version that is disabled by default. If you wish to trial this, please send an email to info@astral365.com explaining your use case, and we will add the functionality to your licence. Please note though that we have integrated using the "Server Driven" method (refer to the Stripe Url later in this paragraph), and Stripe have presently only made the US and Canada live, with other countries still being in beta. Please refer to https://stripe.com/docs/terminal/choosing-reader-and-integration#availability for more details. The Stripe Terminal functionality allows you to setup card readers and take in-person card payments.

We have added "Applies-to Entry Pay. Method" and "Applies-to Entry Payment Terms Code" to the Payment Entry Application page.

Issue Resolutions

The registration process now uses the CompanyProperty.DisplayName() rather than the CompanyName().

Coming Soon

This release still targets V20, but is fully compatible with V22. The next release will target V22.

We will be adding premium version functionality for the ability to brand the pages that are hosted by Astral 365.

We will be adding premium version functionality for the ability to add email signatures and allow a choice of logos that are added to the emails and to the printed invoices.

New Functionality

We have not added any new functionality in this release.

Issue Resolutions

Multiple Email Addresses: If a customer had two email addresses in the Customer's "E-Mail" field, on sending a PayLink a dialog is displayed asking which email address to use. This is fine when clicking the action to send a PayLink to the customer. However, it caused issues when batch printing (and adding the Astral Pay 'Payment Service') or with the new api that we added for integration purposes. In this release, if the email address field (on the Customer Card) contains multiple email addresses, it will simply select the first one when printing (and adding the Payment Service) or when using the api. This is part of the process to generate the payment Url, and the email address field is needed so that the customer can be created in the Stripe merchant account.

Auto Post: We noticed that Auto Post Transaction didn't post payouts. They were left unposted, but when manually posted there weren't any errors. This has now been resolved.

Withholding Tax: Systems that include Withholding Tax functionality (WHT - typically Australia or New Zealand) did not populate the Cash Receipt Journal correctly when using the "Create Journal Only" option. This is because where WHT is applicable, the line that posts to the "Bank Account" could not have a "Document Type" set as "Payment" as any entry that is marked as "Document Type" = "Payment" also needs a Vendor No. or a Customer No. This isn't available for a Bank to Bank journal. Now if the WHT fields exist in the database, it will force the journal to be created using the "Bal. Account Type" and "Bal. Account No." fields (the "Bal. Account No." field being set to the value that is in the "Astral Pay" "Posting Control Account" field), and each line will effectively be a single journal. The net effect posted to the "Posting Control Accout" will be zero.

Document Payment Method Filter: Setting the value to '<>DD' and then leaving the Payment Method Code on the Sales Invoice as empty should have meant that the 'Astral Pay' 'Payment Service' was added, but it was not. The logic for identifying whether the Payment Service should be added has been improved.

Coming Soon

The next release will target V21.

We will be adding premium version functionality for the ability to brand the pages that are hosted by Astral 365.

We will be adding premium version functionality for the ability to add email signatures and allow a choice of logos that are added to the emails and to the printed invoices.

New Functionality

We have added the ability to email out an "Authlink" to allow the customer to 3DS authenticate the card. Where a new card had been added by the merchant via the Stripe portal, it will not have been validated as 3D Secure. On attempting to collect a payment using the saved card, they payment may fail. If the payment does fail, a Page Action on the "Astral Pay Payment Entries" page can be used to "Email 3DS Authorisation Link".

The extension now targets V20. It is fully compatible with V21.

We have added an action (visible = false by default) to allow a user to mark a transaction as "Unposted".

We added an api to allow other extensions to get PayLinks created for Sales Quotes, Sales Orders, Sales Invoices and Posted Sales Invoice

Issue Resolutions

We have amended the logo that is displayed in the Extensions page.

When posting a transaction and using the option to "Create Journal Only", depending on the country version, the Source Code may not have been populated on the journal.

The Error Details page did not always show the Additional Information.

Coming Soon

The next release will target V21.

We will be adding premium version functionality for the ability to brand the pages that are hosted by Astral 365.

We will be adding premium version functionality for the ability to add email signatures and allow a choice of logos that are added to the emails and to the printed invoices.

New Functionality

There is no new functionality in this release.

Issue Resolutions

A further minor change to allow for the successful import of Payment Methods (cards) that were created via the Stripe portal. On processing the notification in relation to a payment method, the Customer Payment Method was being created, but not attached to a customer if the customer didn't exist in Business Central. The repercussion of this is that on importing the customer using the 'Find Missing Customers' action, it was importing the customer, but not importing the card as the card was already referenced in the underlying table. We have resolved this issue by delaying the insert until after the check that the customer exists.

When using the 'Find Missing Customers' action, it now checks for both the Stripe Payment Method ID and the Stripe Customer ID.

We have also added a new 'Import Customer Payment Methods' action to the Customer Payment Methods page.

Coming Soon

Whilst the extension is compatible with Business Central version 20, the next release will target Business Central version 20.

New Functionality

There is no new functionality in this release.

Issue Resolutions

It was reported that cards that were created from within Stripe's portal were not importing in to Astral Pay as available for future use. We identified that the Stripe portal appears to use a deprecated part of their api, and therefore first creates the card as a "source" before it becomes a "payment method". These cards can now be imported and the "Saved for Future Use" field is correctly enabled where applicable.

When sending out a 'Save Card' link by email, it used an existing link for a customer. This caused an issue if the link had already been used. Now, if a previous link is found, the user is asked a question whether they want to re-use the link or create a new one.

When creating a Payment Batch to collect payments from saved cards, there was no way of manually amending the card that is to be used before submitting to Stripe. The user can now either click the Stripe Customer link to select a payment method from any of the Stripe Customers that are linked to the Business Central Customer, or select the Payment Method link to select other payment methods linked to the Stripe Customer.

Coming Soon

Whilst the extension is compatible with Business Central version 20, the next release will target Business Central version 20.

New Functionality

There is no new functionality in this release.

Issue Resolutions

An issue was reported where the 'Document Payment Method Filter' field did not work correctly when multiple Payment Methods were specified.

Additional telemetry has been added to the extension.

Coming Soon

Whilst the extension is now compatible with Business Central version 20, the next release will target Business Central version 20.

New Functionality

The extension is now available in Malta.

Issue Resolutions

A table relation to the Language table was removed from the ISO 639-1 Language Code field in the Email Header/Lines records.

The extension is now fully compatible with the upcoming version 20 release of Business Central. Note that for the extension to be compatible, we had to remove all references to the older "SMTP Mail Setup" table and related objects. Please ensure that you have set up Email Accounts within Business Central if you want to email PayLinks to your customers.

Coming Soon

Whilst the extension is now compatible with Business Central version 20, the next release will target Business Central version 20.

New Functionality

There is no new functionality in this release.

Issue Resolutions

When making a MOTO payment from a Posted Sales Invoice, the amount was set as zero.

It is possible for a Customer to have multiple email addresses in the Email field. Where this occurred, an error was returned from the Stripe api while creating the Stripe Customer. In this scenario, the email addresses are now split into a list, and the user is required to select which Email address to use.

If the Customer Name field has an '&' symbol, an error was returned from the Stripe api.

Coming Soon

We are currently focusing on our other extensions. We are more than happy to receive feature requests, so if you have a suggestion, please do let us know.

New Functionality

There is no new functionality in this release.

Issue Resolutions

When using the "Email Stripe Save Card Link" action on the Customer Card/List pages, in some circumstances it selected the wrong link ID for the email.

Coming Soon

The extension currently targets Version 18, but is fully compatible with Version 19. The next release will target Version 19.

New Functionality

A new field called "BCC All Emails To" has been added to the Setup. When using SMTP Email configuration, the emails were sent straight out with just a success message, and so we felt that it would be useful to be able to BCC an internal email address to keep a copy of the messages that have been sent.

A "No. of Saved Cards" field has been added to the standard Customer Factbox page that is visible when creating sales orders/invoices etc. It is useful information when selecting payment method or payment terms. The mandate status can change automatically, and it is good to have a visible indication on the screen when creating sales documents.

Issue Resolutions

An error was raised when sending a payment to Stripe created against a saved card. The payment still went through but the transaction failed to post. The transaction posted via the webhooks later, but the initial error has now been resolved.

When using SMTP to send emails, the "PayLink Send From Email" field was being ignored if it was set.

Coming Soon

The extension currently targets Version 18, but is fully compatible with Version 19. The next release will target Version 19.

New Functionality

There is no new functionality in this release.

Issue Resolutions

An under the hood change in relation to the integration with our licensing service.

New Functionality

First release of Astral Pay.

Issue Resolutions

None.