-
New Webhook Service
Update:
Introducing:
- Additional IP addresses sending Payment and DataSet webhooks:
63.182.150.2453.68.254.1303.126.194.2133.124.137.18
Integrators are encouraged to limit webhook requests from the IPs listed in this resource: https://info.onlinefundraising.dk/webhooks.json
Please check this at least once daily.
During 2026 Q2-Q3 we will gradually transition webhook event types to a new dedicated Webhook Service which will relieve the bottlenecks we have seen, which peaked in December 2025: https://status.onlinefundraising.dk/incidents/scxl4lwm38b6
For more, please see our documentation: https://support.onlinefundraising.dk/hc/en-001/articles/5356622578844-About-webhooks
- Additional IP addresses sending Payment and DataSet webhooks:
-
From MobilePay to VippsMobilePay
Update:
UPDATED 2026-10-06 : Read more
Announcing breaking change:
- The existing Payment Method Type:
"MobilePaySubscriptions"will be replaced by:"VippsMobilePayRecurring""VippsRecurring" - The existing Payment Gateway Provider:
"MobilePay"will be replaced by:"VippsMobilePay""Vipps"
Integrators are encouraged to account for both existing and replacing Payment Method Types and Payment Gateway Providers.
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,amountandfrequencyin 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 and Payment Gateway Provider per entity in the Payment API.
We expect the migration to start in April and last until
JulyOctober 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 Payment Methods
- All MobilePay Subscriptions
NB: Your integrator may request a migration without webhooks.
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 “VippsRecurring“.If your integration relies on Payment Method Type for reporting or similar, please be prepared to receive new Subscriptions and new Recurring Payments with “
VippsRecurring” sometime in the above mentioned timeline.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 of Existing Payment Method Type Replaced by Single Payments
(currently via PSP)MobilePayOnlineVippsSingle
(later)Recurring API MobilePaySubscriptionsVippsRecurringReport API,
Donations APIMobilePayExternalVipps External
(later)
- The existing Payment Method Type:
-
Payment API: paymentRequired and quantities
Update:
Deprecating:
- Agreement and Payment property:
"paymentRequired" - Agreement property:
"defaultQuanity" - Subscription and AddOn property:
"quantity"
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.
Payment Required
We found that the property “
paymentRequired” caused unnecessary confusion and chose to phase it out from various user interfaces during 2024, reducing its usage intentionally. With this update we also ignore the property, should it be provided by integrators.The original intention behind “
paymentRequired” was to address arrears on an unpaid subscription – for example, when a payment card expired, and the subscription required payment for its service.This made sense for commercial products, but not for donations, and thus created unnecessary confusion and complexity in the overall solution.
Quantity
Similarly, variations of “quantity” are suited for subscriptions of physical goods, but not for donations, which furthermore added unnecessary confusion.
With this update we ignore the above mentioned properties should they be provided by integrators.
- Agreement and Payment property:
-
SMS with Custom Fields Service
Update:
We have expanded the existing user interface with the Custom Fields Service.
Later, as with other subsystems, we will update the user interface in terms of design and user experience.
-
Payment API: Unpaid, expectedTs og First-scheduleTypes
Update:
Tags: Payment APIIntroducing:
- Payment state:
"Unpaid" - Payment timestamp:
"expectedTs"
Deprecating:
- The follow Agreement Schedule Types:
YearlyFirstHalfyearlyFirstQuarterlyFirstMonthlyFirstWeeklyFirst
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.
State: Unpaid
The Payment state: “
Unpaid” is assigned to Pending payments that have not been charged three months afterdueDateTs, without any error detected.Common examples are Direct Debit claims with Arion Banki or FI-kort (giro) via Betalingsservice, e.g. FI-kort has been sent by post, but it has not been paid and we have no options to check its status.
The Unpaid state reflects that no further action will be made for this particular payment, and allows for anonymisation which is prohibited Contacts with Pending Payments. However, should the Payment be paid at a later time, the Payment state will be updated to: “Charged”.
No webhook is sent when the state is set to “Unpaid”, as we consider this a non-action.
Timestamp: expectedTs
The new “
expectedTs” timestamp indicates when the payment is expected to be processed and is shared across all Payment Types. In practice, this timestamp corresponds to the following for each Payment Type:- Single: “
chargedTs“ - OneOff: “
chargedTs“ - Recurring: “
dueDateTs“
Our aim is to help analysis and pivot across all Payment Types.
Schedule Types with First
The following existing schedule types are being deprecated in favour of variants without the suffix “First”:
YearlyFirstHalfyearlyFirstQuarterlyFirstMonthlyFirstWeeklyFirst
Our aim is to narrows the scope of options for integrators.
The use of “*First” was generally very limited and Agreements with such scheduleTypes have been updated accordingly.
- Payment state: