Tag: Vipps

  • From VippsMobilePay to Vipps

    Update:

    Tags: , ,

    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)

  • From MobilePay to VippsMobilePay

    Update:

    Tags: , ,

    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, 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 and Payment Gateway Provider per entity in the Payment API.

    We expect the migration to start in April and last until July October 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 ofExisting Payment Method TypeReplaced by
    Single Payments
    (currently via PSP)    		MobilePayOnlineVippsSingle
    (later)
    Recurring APIMobilePaySubscriptionsVippsRecurring
    Report API,
    Donations API    		MobilePayExternalVippsExternal
    (later)

  • Updated Support of VippsMobilePay’s Donation API

    Update:

    Tags: ,

    We have expanded Payment Receiver and its integration with VippsMobilePay’s Donations API, upgrading from v1 to v2, making authentication easier with the user interface.

    Their Donations API enables the forwarding of donors’ full name and phone number to the organisation (at a cost) in contrast to regular VippsMobilePay Number payments.

    Additionally, with this update we also note whether or not each payments is part of “Faste Donationer” which will later be used to mirror those subscriptions and their recurring payments.

    Contact

    Full name is provided without split into first name and last name as these are not available from the Donations API.

    {
    "contactType": "individual",
    "name": "Full name",
    "msisdn": "4512345678",
}

    Payment

    Meta data provides insight into Number (recipient), custom reference from VippsMobilePay’s portal, and agreement.

    {
    "paymentMethodType": "MobilePayExternal",
    "paymentGatewayProvider": "PaymentReceiver",
    "paymentGatewayTransactionId": "10000000000",
    "paymentMethodAccountingCode": "MobilePayExternal",
    "metaData": {
        "mpe": {
            "message": "My message",
            "ledgerId": "123456",
            "recipient": "DK:654321",
            "agreementId": "d1e2d365-1433-471c-be96-xxxxxxxxxxxx"
            "externalReference": "ORG-REF-1234"
        }
    }
}

    Payment Method

    {
    "paymentMethodType": "MobilePayExternal",
    "paymentGatewayProvider": "PaymentReceiver",
    "metaData": {
        "mpe": {
            "recipient": "DK:325858"
        }
    }
}

    DataSet

    A summary of registered details are available from the DataSet API.

    {
    "jsonElement": {
        "formResult": {
            "name": "Full name",
            "msisdn": "4512345678",
            "message": "My message",
            "recipient": "DK:123456",
            "externalReference": "ORG-REF-1234",
            "agreementId": "d1e2d365-1433-471c-be96-xxxxxxxxxxxx"
        }
    }
}