The settings of Tip request in the APP only work if you perform a Direct Payment, if an external Application starts the payment, Tip can be enabled now by request by sending some parameters via the integration object.

Read more: https://developer.pay.nl/docs/softpos#ask-the-customer-for-a-tip-through-inject

We have introduced a new endpoints for terminal management (to support in-person payments).

• Terminals:Create; use this endpoint to create a terminal for a service location. You need to have an activation code (will be presented on the payment terminal). If you are a partner and have access to your sub-merchants you can also create a terminal for a service location from one of your sub-merchants. Note you need to have additional rights to use this endpoint.
• Terminals:Delete; if you want to remove a terminal from a service location you can use this endpoint. Also here; if you are a partner you need to have access to that merchant to be able to remove a terminal for a sub-merchant. Note you can undelete your delete action within a 15 min time windows with the Terminals:Undelete endpoint.

With the introduction of V3 of our API’s we have introduced our new transaction processing platform; called the Transaction Gateway Unit platform. Together with this TGU platform we have released V1 of our Order API.

The main benefits of this Order API;

• Brand new API's for the processing of transactions on our Transaction Gateway Unit platform
• Support to handle multiple payments to pay for an order. E.g. an order can be paid with a voucher and with an iDEAL transaction.
• Fully compatible with iDEAL 2.0 and all of iDEAL's new features (like fast checkout). See this page for more information: https://developer.pay.nl/docs/ideal
• All new features (and new payment methods) will be introduced on this TGU platform
• Easy switching between different TGU's when a TGU is unavailable due to disruptions or maintenance

We strongly advise to change your implementation to use these new Order API’s, please contact your contact person within Pay for more information.

We have released a few changes in the last months. Below a summary👇

Changes

• It was already possible to start a transaction with the Transaction:Create API with an SL-code and secret as authentication. It is now also possible to request the status of the transaction with the Transaction:Statuswith an SL-code and secret on rest.pay.nl.
• We have added pagination to the Terminals:Browse endpoint
• We fixed a typo in the Transaction:Refundendpoint. The description is has a maxLength of 32 instead of 64
• We have added a new endpoint Payout:Clearing, with this endpoint you can create an instant clearing on the revenue group linked to the provided service. If you want to use this endpoint, please contact your accountmanager. Specific rights are needed if you want to use this endpoint.
• We have added a boardingStatus and a payoutStatus field to the Merchants:Get, Merchants:Browse and Merchants:Info. A full description of these statusses can be found here: https://developer.pay.nl/docs/object-status

We have released a few small updates in the past weeks, see it as a Christmas gift 🎄🧑‍🎄. Read more below 👇

Improvements

• When updating a license to an UBO or to an authorized to sign person or when creating a license which is an UBO or authorized to sign person we will automatically request for an identification (document). In the response of the update or create call an identification document is now requested.
• The available balance per turnovergroup is added to the Balance:Dashboard (https://developer.pay.nl/reference/get_balance)
• In the Merchant:Update (https://developer.pay.nl/reference/patch_merchants-merchantcode) we have added the country of residence. You are now able to update this country of residence (for a merchant). Note this will trigger a review of the merchant file.
• We have implemented a few improvements in the Transaction:Create API
  • The BTW number is now successfully stored when creating a transaction;
  • The validation on regionCode (in the delivery address and invoice address) is removed and this field is added to the documentation.
• In the Merchants:Info (https://developer.pay.nl/reference/get_merchants-merchantcode-info) API we have added the Pay. account manager and for each sales/service location the website and the websiteURLs that are configured in the output.
• In the Terminals:Browse (https://developer.pay.nl/reference/get_terminals) and Terminals:Get (https://developer.pay.nl/reference/get_terminals-terminalcode) we have added the supplier of the terminal and for each brand the Acquirer and AcquirerMID to the output.
• We fixed an issue in the Transaction:Refund (https://developer.pay.nl/reference/patch_transactions-transactionid-refund), the correct RefundID is now returned.

We have released quite a few new endpoints in the last months. Read more below 👇

New endpoints

We have released quite a few new endpoints. Note for all these endpoints you need to have the proper rights.

• Licenses: Get, Browse, Create, Update, Delete and Undelete. See for more info: https://developer.pay.nl/reference/get_licenses-licensecode. These endpoints can be used e.g. to add a new license (account) to a (sub-)merchant. You can also add the compliance data (e.g. UBO status etc).
• ContactMethods:Get, Browse, Create, Update, Delete and Undelete. See for more info: https://developer.pay.nl/reference/get_contactmethods-contactmethodcode. These endpoints can be used e.g. to add a new contact method to a (sub-)merchant.
• AuthenticationTokens:Get, Browse, Create, Delete and Undelete. See for more info: https://developer.pay.nl/reference/get_authenticationtokens-authenticationtokencode. These endpoints can be used e.g. to add an authentication token to a (sub-)merchant.
• Turnovergroups:Get, Browse, Create, Delete and Undelete. See for more info: https://developer.pay.nl/reference/get_turnovergroups-turnovergroupcode. These endpoints can be used e.g. to add an turnovergroup to a (sub-)merchant.
• ClearingAccounts:Get, Browse, Create, Delete and Undelete. See for more info: https://developer.pay.nl/reference/get_clearingaccounts-clearingaccountcode. These endpoints can be used e.g. to add a clearingaccount to a (sub-)merchant.
• Merchant:Update. See for more info: https://developer.pay.nl/reference/patch_merchants-merchantcode. This endpoint can be used to update merchant data.
• Merchant:UpdatePackage. See for more info: https://developer.pay.nl/reference/patch_merchants-merchantcode-package. This endpoint can be used to update the package. To get a list of available packages you can use the Packages:Get (https://developer.pay.nl/reference/get_packages) endpoint. When updating the corresponding settings which belong to that package will be applied.
• Merchant:ToReview. See for more info: https://developer.pay.nl/reference/patch_boarding-merchantcode-ready. This endpoint can be used to notify our boarding department that the merchant is ready to be reviewed.

Other improvements

• In the Transaction:Create response we have added a few new data elements when an instore payment has been done.
  • A hash; a unique key of the transaction which can be used to get the status of the payment or the request a receipt
  • A cancelURL; an URL which can be used to cancel the instore payment
  • An orderStatusURL; an URL which can be used to retrieve the status of the instore payment

We call this update the early summer ☀️ update. We have released a few updates and a new endpoint. Read more below 👇

Reporting

We have released a new endpoint that gives an overview of the active balance of a merchant, inlcuding information about the next and previous clearing. If you are a partner and supply a merchant code and you have access to that merchant we will provide the data from that merchant. If no merchant code is provided your own balance information is returned. Note you need to have the correct rights to use this endpoint.

Read more here: https://developer.pay.nl/reference/get_balance

Other improvements

• In the Authorisation:Capture, the Transaction:Status and the Transaction:Info response the merchant reference is now returned instead of the consumer reference.
• In the Terminals:Browse you can now supply a merchant code as query parameter to filter the list of terminals for a certain merchant. See for more information: https://developer.pay.nl/reference/get_terminals.
• Some query parameters in the Invoice:Lines and Clearing:Lines endpoints where not correctly described in the documentation, we fixed that.
• In the Merchant:Create endpoint you can now supply a visitAddress for each person/account.
• The Documents:Add endpoint now supports multiple files (of the same file-type), these files will be merged into one document.

Again we have released an update. The second one in May 👏. This release contains a few updates and new endpoints. Read more below 👇

Merchant management

We have released new endpoints to retrieve:

• Invoice lines; with this endpoint you can retrieve the invoice lines. If you are a partner and have access to your sub-merchants you can retrieve also the invoice lines for your sub-merchants, see for more information. https://developer.pay.nl/reference/get_invoicelines .
• Clearing lines; with this endpoin you can retrieve the clearing lines. If you are a partner and have access to your sub-merchants you can retrieve also the clearing lines for your sub-merchants, see for more information: https://developer.pay.nl/reference/get_clearinglines.
• An invoice/clearing line contains a unit type (e.g. per percentage or per quantity). We have a Core API available to retrieve all unit types Pay is using (https://developer.pay.nl/reference/get_billingunittypes).
• Furthermore an invoice/clearing line contains a billing or clearing type, e.g. to invoice iDeal transactions or to indicate we have cleared iDeal transactions. We have a two Core API availables to retrieve:
  • All billing types incl. how they are grouped on the invoice available (https://developer.pay.nl/reference/get_billinglinetypes)
  • all clearing types incl. how they are grouped on the clearing available (https://developer.pay.nl/reference/get_clearinglinetypes

Other small improvements

• The Service:GetConfig response now contains a list of available TGU's; see for more information (https://developer.pay.nl/reference/get_services-config). For more information regarding the Pay platform and TGU's please refer to; https://developer.pay.nl/docs/platform
• The Core API to retrieve the languages that Pay supports (https://developer.pay.nl/reference/get_languages) referred to an .png image. However in the image pack that we supply only .svg images are available. We now refer to the correct .svg image in the API.

We have released a small update with two new endpoints. Read more below 🙌

Merchant management

We have released new endpoints to:

• Suspend a merchant; see for more information; https://developer.pay.nl/reference/delete_merchants-merchantcode
• Unsuspend a merchant; see for more information; https://developer.pay.nl/reference/post_merchants-merchantcode-unsuspend

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