Convert to use Mollie Payments API

[mattbrailsford]

The current Mollie payment provider makes use of the Mollie Orders API in order to give a full order breakdown within Mollie. Looks at their docs however, it looks like they are deprecating the Orders API in favour of the simpler Payments API. With the Payments API we would no longer provide a full order breakdown, instead we would just send an order amount to capture (much like many other payment providers).

I think it would make sense given the Orders API is being deprecated that we should look to migrate the provider to use the Payments API instead.

[melslenstra-dc]

@mattbrailsford Mollie actively discourages use of the Orders API: https://docs.mollie.com/docs/orders-overview

The current implementation sends quite some customer and order information to Mollie, effectively making those fields required in the order on the Umbraco Commerce side. For instance, it seems impossible to NOT ask for a full billing address if the order is to be paid using this payment provider. This has functional implications (having to ask for an address when selling a purely digital product) as well as being less-than-ideal GDPR-wise.

Is switching to the recommended Payments API on the roadmap somewhere?

[DynamicDave]

Hi Matt,

Personally, I think it's a shame that Mollie no longer recommends using the Orders API, because I prefer to send a "whole order" to Mollie so that I can also review the order in Mollie instead of just the total amount.

I would rather prefer to see an option to place an Order for a digital product, so without address details. Or the choice in the Commerce Payment Provider between Order and Payment.

But anyway; changes at Mollie is not something you can do anything about.

Dave

[melslenstra-dc]

I get that preference, it can be very nice to have an overview in your Mollie dashboards. Ideally, which of Mollie's APIs to use should be configurable (or just have two separate PaymentProvider packages to choose from).

AFAIK it's Mollie that requires those fields in case of using the Order API, so I don't think an "option to place an Order (...) without address details" is going to be possible from UC's point of view - but I might be wrong.

[DynamicDave]

You're absolutely right! It should be an option whitin Mollie.
A complete order; an (digital) order without addres info etc and a simple payment.
If Mollie would be able to provide that options, the choice which type of payment you want to make wouldn't be that hard I think.

[rudgr]

any updates on this? tx

PS: might also not to validate this mollie api identifier change https://help.mollie.com/hc/en-us/articles/26598989040146-Update-to-API-identifiers

[mattbrailsford]

No update yet. It is on our backlog so we will get to it at some point but it hasn't yet been scheduled. We also need to review where the payments API is at as at the time of creating this feature request not all payment methods that the Order API were supported so we need to see if those have been added yet.

[umbracotrd]

Hey guys, Mollie Payment Provider 16.1.0 is out with a new payment provider available in the backoffice, which uses Mollie's Payment API. The old payment provider which uses Mollie Order API is now deprecated in the backoffice (just in the UI, there's no changes functionality-wise) and will be removed in v17.

The details changes can be found in the repository's Releases section.