The April update (Week of 10 April)

We have released an update. Read more below 👏

Core data; BillingLineTypes and UnitTypes

We have introduced new endpoints to retrieve Core data for the new Billing API that will be launched soon.

• BillingLineTypes; a Pay. invoice contains multiple billing lines which are grouped. This API returns all groups that are available. See for more information; https://developer.pay.nl/reference/get_billinglinetypes
• UnitTypes; each invoice line can have his own unit (e.g. per quantity or per percentage). This API returns all unit types that are available. See for more information; https://developer.pay.nl/reference/get_billingunittypes

PaymentVerificationMethods

A payment can be secured by different methods. On a card present transaction (on a payment terminal) it is known ad the Card Verification Method (CVM). iDEAL transactions can be verified by e.g. a QR code or by an app2app payment. We combine all these options in the PaymentVerificationMethods

With the Core data API; PaymentVerificationMethods you can retrieve a list of all methods. See for more information; https://developer.pay.nl/reference/get_paymentverificationmethods

And with the Transaction:Status and Transaction:Info endpoints the used method is returned if it is available.

Support for different "base URLs"

For the Transaction:Create, Transaction:Status and Transaction:Info endpoints support for different base URLs is added. In this documentation environment you can select (in the API explorer) against which base URL you want to try you API request.

Merchant:Create

We have introduced a few changes in the Merchant:Create endpoint

• The Pay. welcome e-mail will only be sent if loginAccount=true.
• The phone number and e-mail adress of a person is now optional. It is not required anymore