Tag: VippsMobilePay

  • From MobilePay to VippsMobilePay

    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 2026, one merchant at a time, in a prioritised timetable, and as coordinated with each CRM integrator as possible.

    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)

  • 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"
        }
    }
}