Category: Updates


  • From VippsMobilePay to Vipps

    Announcing breaking change:

    • The existing Payment Method Types:
      "MobilePaySubscriptions" and “VippsMobilePayRecurring” will be replaced by: "VippsRecurring"
    • The existing Payment Gateway Providers:
      "MobilePay" and “VippsMobilePay” will be replaced by: "Vipps"

    Integrators are encouraged to account for both existing and replacing Payment Method Types and Payment Gateway Providers.


    Update to planned migration

    We are currently about two-thirds through our planned migration of existing MobilePay Subscriptions to our dedicated microservice (as outlined in our previous update).

    In the midst of this rollout, Vipps MobilePay officially announced a brand consolidation, uniting under the single brand name Vipps and phasing out the MobilePay brand name across markets (see Vipps Merchant & Partner Guide).

    Rather than locking our API into an interim brand name (VippsMobilePayRecurring) that would quickly become obsolete, we have decided to follow along and use the term VippsRecurring (with provider Vipps) as this avoids confusion in the years ahead and keeps our data model clean.

    We are therefore holding the migration process to coordinate this update.

    Mid-flight renames can often introduce operational friction, and we are only able to realistically consider and execute this shift thanks to the outstanding, productive cooperation with the integrators representing the subscriptions already migrated.

    We will reach out to each integrator and plan the update together.

    Payment and Payment Method

    Once migrated Payments and Payment Methods will include:

    {
        "paymentMethodType": "VippsRecurring",
        "paymentGatewayProvider": "Vipps"
    }

    Subscription

    Once migrated Subscriptions will include:

    {
        "paymentMethodType": "VippsRecurring"
    }

    Future transitions

    Please note that this release and migration only involve Subscriptions and their Recurring Payments. Single and External Payments are not included at this stage, but these will be transitioned as the integration progresses.

    Support ofExisting Payment Method TypeOriginally announcedReplaced by
    Single Payments
    (currently via PSP)
    MobilePayOnlineVippsMobilePaySingleVippsSingle
    (later)
    Recurring APIMobilePaySubscriptionsVippsMobilePayRecurringVippsRecurring
    Report API,
    Donations API
    MobilePayExternalVippsMobilePayExternalVippsExternal
    (later)


  • New response options for webhooks

    Introducing:

    • New response options for webhooks to postpone our exponential backoff algorithm:
      • HTTP 429 Too Many Requests
      • HTTP 503 Service Unavailable

    For more, please read about webhook delivery attempts: https://support.onlinefundraising.dk/hc/en-001/articles/5356624805916-Webhook-Delivery-Attempts


    During 2026 we are improving our infrastructure and one element is our separation of webhook handling from the payment engine as previously announced: https://www.onlinefundraising.dk/developer/new-webhook-service/

    The migration of webhook event types is still ongoing, but we expect it to be completed in September 2026.

    The new webhook infrastructure allows batching of a configurable larger number of webhook payloads per webhook request, and an overall faster execution.

    We understand some integrations are built to handle lower volumes at a slower pace and therefore introduce an option to respond with HTTP 429 or HTTP 503 with a Retry-After as described in our documentation.


  • Replacement of DAWA with Adressevælger

    Introducing in June 2026:

    • addressValidator and addressId in DataSet

    Deprecating in September 2026:

    • dawa_id in DataSet

    Fundraisers can choose to use various services to validate user inputs, including Business Code, National ID, Phone Number and Address.

    In Denmark, we currently validate Danish addresses using Danmarks Adressers Web API (DAWA). However, DAWA is being deprecated on 17th of August 2026 and will be replaced by a new service called Adressevælger. For more, please see:

    The two services operate somewhat differently, but share the same underlying address UUID. You can verify this by looking up our office address using the UUID 0a3f507b-4642-32b8-e044-0003ba298018:

    As part of this transition, we are replacing the “dawa_id” field in DataSet with a new field “addressId“, which is neither service nor country specific.

    If your integration relies on DAWA, please update it to use the new field “addressId” along with the Adressevælger service.


  • Payment API: orderLines and receipt

    Deprecating:

    • The entity: “Order Line” and thereby the API-endpoint:
      GET /payment/{guid}/orderLines
    • The entity: “Receipt” and thereby API-endpoint:
      GET /payment/{guid}/receipt

    During 2026 we will implement a series of backward-compatible optimisations in the Payment API. These improvements aim to simplify maintenance of the source code, ensure stability, and make it easier for new integrators to work with the Payment API.

    See the previous release.

    Background

    When Payment API was introduced back in 2019, OnlineFundraising’s focus was less narrowly defined than it is today. Over time, it has become clear that our sole focus is on charitable organisations and their fundraising for good causes. At the time, however, there were also commercial interests to consider, both then and in the years that followed.

    For that reason, OrderLines were added to support a potential need to present an invoice consisting of order lines, corresponding to a settlement for a given period. In practice, this capability has turned out to be unnecessary for organisations. We are therefore deprecating and removing this functionality to simplify our codebase and make ongoing maintenance easier.

    We recognise that this is not backwards compatible, which we normally strive to maintain. However, since we see virtually no API requests using this functionality, we are taking the liberty of phasing it out. Please do not hesitate to contact us if you have any questions about this change.


  • New Communication Event Types

    Introducing Communication Event Types:

    • PaymentMethodSignupFailed
    • PaymentRecurringFailed

    These will allow organisations to configure additional automatic retention emails sent to donors based on specific scenarios which predominately are incorrect bank details for Betalingsservice and erroneous payment method applied in VippsMobilePay respectively.