prisma turtle
Hi, I was using the "Get payment method" endpoint for a while to get pricing of payment methods. https://docs.mollie.com/reference/get-method
In the documentation there is still the pricing response, but in query params the option of pricing is removed from the param include.
When calling the API there is no pricing response.
mollie_payment_info = Mollie::Method.get(method.id, include: "issuers,pricing")
strange onyx
I don't know the exact reasoning why it was removed from the /method/{id} endpoint (I think @thin portal might have more information about that), but the information you're looking for is still available on the /methods/all endpoint.
thin portal
yes we have removed the pricing from methods and methods/{id}. It can now only be included for methods/all. The reason for this is that we see different use cases for these endpoints: the methods/all we see mainly used by partners who want to offer payment method management in their own solution. The other ones are used more in checkouts to render the available payment methods. The latter one therefore will be used a lot more and has a lot more need for a low latency, so we have removed the pricing info (since this was quite "expensive").
We just need to update the docs to show that we have different responses depending on the endpoint you call. We will have a look at that.
prisma turtle
Ah check, I will be updating to use the /all endpoint then. Thanks!
gaunt canopy
yes we have removed the pricing from `methods` and `methods/{id}`. It can now on...
It "might" be good to communicate about this kind of changes. We store the transaction costs when starting a transaction, which results in objects not being found, payments not being created and in the end B2B customers that are getting their transaction costs for free now as we store "0" as transaction costs since this change. This is a breaking change.
This change is not in the changelog, there is no deprecation beforehand, developers were not informed and pricing had to be explicitly included in the request to include it in the response, so I doubt if there are a lot of use cases where developers enabled pricing but did not use it.
Please understand we are losing customers because of this, customers that will take a look at other parties as we are partnering with a PSP that is making breaking changes and reacting like it is business as usual.
quartz talon
It "might" be good to communicate about this kind of changes. We store the trans...
Yes, that!!
We have many, MANY, failed transactions because of this and it took us some time to figure out it was actually the API (ignorant as we are we thought we broke something) which changed on us! Getting a fix in production is not a 1-minute operation.
wet gyro