What's new

In this release, we have compiled various smaller and scattered tasks related to bugs or optimization opportunities across our system landscape. From a long list of items, we will highlight the following.

UPDATED : 2024-06-13

Following this, we have unfortunately discovered that we released a breaking change that affects the accounting of payments via ePay. This change was not intended to be released without further clarification and notification to organizations and integrators. We deeply regret this and are working on a proper handling of the situation. We will review our procedures for such releases to prevent this from happening again.

UPDATED : 2024-07-16

We have decided to roll back the above mentioned change as of August 1, 2024. This means that from August 1, you will find ePay's Order ID as before. The ePay payments that have been processed in the meantime will remain unchanged to avoid further unintended consequences.

To assist you as best as possible, we will provide full export files of your payment data, and you can always contact us at support@onlinefundraising.dk for questions or clarifications.

We apologize once again for the inconvenience, and we are in the process of revising our procedures to avoid similar situations in the future.

What's changed

• Email Service: We have improved our ability to validate domains for sending email addresses from the organization's domain.

• Communications: We have added standard fields for the organization's postal code and city.

• Export: We have updated the interface for the export module to align with our standards for future development.

• Form: We have added support for the URL parameter: "utm_id".

• Web Resources: We have adjusted the caching duration of web resources in OnlineFundraising's portal to prevent users from using a locally cached and outdated version.

• Internationalization: We have been working on further internationalization and translation of Danish terms for the benefit of our Icelandic customers.

Bugfixes

• MobilePay: Until now, we have not updated the agreement's amount in MobilePay's app, which is particularly relevant following upgrades via telemarketing.
• MobilePay: We have updated our handling of Refund callbacks according to the new API following MobilePay's migration with Vipps.
• QuickPay: Customers experienced that QuickPay no longer forwarded the provided phone number to MobilePay, which we have reviewed and fixed initially, however it seems several gateways are experiencing a similar issue in relation to MobilePay.
• QuickPay: In the event of failed charge attempts via QuickPay, we did not register the error code and message from QuickPay. This has now been corrected.
• QuickPay: We have improved our logging and handling of payment sessions where Strong Customer Authentication (SCA) was required, failed from the user's side, and then successfully retried.
• ePay: We have registered ePay's Order ID as the transaction number in OnlineFundraising, which we have now corrected.
• NETS Easy: We have fixed our handling of callbacks if the gateway is temporarily down.
• Teya: We have fixed various minor errors in our handling of callbacks from Teya.
• SMS Keyword: We have added a date restriction for SMS campaigns run by organizations that are not members of ISOBRO, as required by 4T under rammeaftalen.dk.
• DataSet: The information "isTransactional" was not correctly derived in all cases.
• Internationalization: We have fixed our validation of the Icelandic Kennitala (National ID).