Category: Updates


  • Updated Support of VippsMobilePay’s Donation API

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

  • Updated User Interface: Export

    As part of our ongoing and gradual improvement of the user interface, we have updated the appearance of the following menu items:

    • Export

    The update includes a new design and several adjustments to enhance the user experience including:

    • Full history of past exports
    • Ability to isolate own exports from your colleagues
    • Ability to reuse previous exports as a filter for a new export
    • Support of Custom Fields Service

  • Swish Single

    Introducing:

    • paymentGatewayProvider: "Swish"
    • paymentMethodType: "SwishSingle"

    We recently introduced Swish as a new Payment Gateway, and are now expanding our implementation with Single Payments.

    The API documentation have been updated accordingly:


  • Updated User Interface: Settings

    As part of our ongoing and gradual improvement of the user interface, we have updated the appearance of the following menu items:

    • Settings

    The update includes a new design and minor adjustments to enhance the user experience.


  • Custom Fields Service

    We have introduced a new micro service: “Custom Fields Service”, which centralises Custom Fields used across Forms, Onboarding, SMS and custom integrations.

    As new Custom Fields are added – for example in Forms – they will be registered and later used to guide the addition of the same Custom Fields in other micro service, such as Export or Communications.

    The menu item for Custom Fields Service is located under “Data”.