Tag: Breaking Change

  • Payment API: orderLines and receipt

    Update:

    Tags: ,

    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.

  • From MobilePay to VippsMobilePay

    Update:

    Tags: , ,

    Announcing breaking change:

    • The existing Payment Method Type: "MobilePaySubscriptions" will be replaced by: "VippsMobilePayRecurring"

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

    Background

    When Norwegian Vipps and Danish MobilePay merged in March 2024 we chose to extend our existing “Payment Gateway Engine” (a micro service) as the fastest way to support the new VippsMobilePay API without any chances to our Payment API, allowing a smooth transition.

    As OnlineFundraising remained in Denmark we kept the Payment Method Type: "MobilePaySubscriptions" as it were.

    Today OnlineFundraising manages ~600.000 MobilePay Subscriptions, and as we become increasingly relevant for Norwegian organisations we have identified a need to both enhance our ability to scale and incorporate the Norwegian brand: “Vipps”.

    We have therefore been working on a new micro service with a fresh implementation of the VippsMobilePay Recurring API which among other things allows synchronisation of Agreement details, such as plan, description, amount and frequency in the app.

    Migration

    Implementation of the new micro service will involve a migration of existing Subscriptions and Payments from one micro service to another which includes replacing the Payment Method Type per entity in the Payment API.

    We expect the migration to start in April and last until July September 2026, one merchant at a time, in a prioritised timetable, and as coordinated with each CRM integrator as possible.

    During the migration updated webhook events will be sent for:

    • Recurring MobilePay Payments in 2026
    • All MobilePay Subscriptions
    • All MobilePay Payment Methods

    Integration

    If your integration is creating new Subscriptions with the Payment Session Handler API you may continue to use the Payment Method Type: “MobilePaySubscriptions” until the end of 2026, as we will convert it to “VippsMobilePayRecurring“.

    If your integration relies on Payment Method Type for reporting or similar, please be prepared to receive new Subscriptions and new Recurring Payments with “VippsMobilePayRecurring” sometime in the above mentioned timeline.

    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 TypeReplaced by
    Single Payments
    (currently via PSP)    		MobilePayOnlineVippsMobilePaySingle
    (later)
    Recurring APIMobilePaySubscriptionsVippsMobilePayRecurring
    (upcoming)
    Report API,
    Donations API    		MobilePayExternalVippsMobilePayExternal
    (later)