-
Extended support of Vipps Donations
Planned update:
- Extended support for Vipps’ Donations product, bringing in-app recurring donations into the subscription lifecycle
Vocabulary and concepts
At the API level Vipps operates with Agreements which represents the mandate and terms agreed with the debitor. Under an Agreement, an organisation may issue Charges.
In the product description Vipps presents agreements as Subscriptions, and charges as Automatic Payments and Recurring Payments. These are functionally synonymous with agreements and charges.
Charitable organisations have used Vipps (MobilePay) for donations and memberships for years, as OnlineFundraising introduced an integration to “MobilePay Subscriptions” in 2019 for specifically Danish organisations.
This well established product should not be confused with the newer Vipps Donations product, nor with standalone Numbers.
The Vipps Donations product
The essential features of the Donations product are:
- Donors can donate from the Vipps app without a website (and OF)
- Donors can change amount and frequency from the Vipps app
- Organisations are given access to personal details which historically only have been available through a website (with OF)
Product Origin / Channel Supports recurring? Debitor details Vipps Recurring Website with OF form Yes Full Vipps Numbers Vipps app No (single only) None Vipps Donations Vipps app Yes (single & recurring) Name & Phone Number Extended support in OnlineFundraising
Earlier this year we integrated to the Donations API and made both single and recurring donations available through our “Payment Receiver” which already supported the Report API containing Numbers. Our focus was strictly transactional data, as a way to help reporting and bookkeeping.
Later this year we will extend the integration which will present Agreements, as part of the Donations product, similar to other subscriptions in OnlineFundraising, such as Card, SMS, Betalingsservice or Vipps Recurring.
The key difference to the Payment API will be that the entities: Agreement, Subscription and Payment Method are locked together, as these are mirrored from Vipps, and that changes to i.e. amount and frequency cannot be made by the organisation, nor integrators to the Payment API, as this is the debitor’s exclusive prerogative in the Vipps app.
We are working hard to implement this Donations product without breaking changes, and our expectation is the integrators need only pay attention to the Payment Method Type: “
VippsExternal“.More updates will follow.
-
Updated Support of VippsMobilePay’s Donation API
Update:
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 Interfaces
Update:
As part of our ongoing and gradual improvement of the user interface, we have updated the appearance of the following menu items:
- Webhook
- Email History
- Payment Receiver
The update includes a new design and minor adjustments to enhance the user experience.