We have added some extra attributes in the PaymentMethods core data API

• targetCountries; indicates the targetCountries for each paymentMethod. E.g. the targetCountry for iDEAL is 'NL', the targetCountry for Bancontact is 'BE'.
• For each paymentProfile in a paymentMethod we now also return:
  • The riskCategory; e.g. iDEAL has a low risk category
  • The customerIdType; indicates how the payer is paying for the transaction. E.g. for iDEAL the payer is using his/her IBAN. For card payment the payer is using a creditcard.

We have released a few small improvements for the following endpoints:

• In the Service:GetConfig we now return the address that is configured on service location level
• In the Order:Create response and in the exchange call we now return the stats data and the transferData if supplied when creating an order.

We have released to new endpoints to get more information about your clearings & settlements. These endpoints are still in beta, so if you want to have access to these API's please contact your contactperson within Pay. to retrieve the necessary authorisations.

A short description of these endpoints:

• Clearings:Summary; A Pay. clearing contains multiple clearing lines. This API returns the clearing grouped by settlement (the actual transfer of the money to your bankaccount. You can filter on clearing id or settlement code (the code visible on your bank statement).
• Clearing:Records; Retrieve the transactions that are in a clearing. Provide a clearing ID or a settlement code (the code visible on your bank statement) to retrieve the transactions that are in that clearing.

We have released new functionality for some endpoints

• Terminals:Get and Terminals Browse we added the following fields to the output:
  • The hardwareCode (our TL-code) and physical serialNumber from the terminal;
  • The MCC code linked to your service / sales location in the service object;
  • The contact details (phone number and e-mail) that are linked to your service / sales location in the serviceobject;
  • The incorporationCountry field in the merchant object, this country represents the country in which the merchant is legally registered or incorporated.
• In the Merchant:Create, the License:Create and the License:Update we have added a rolesobject, so that you can indicate if the person that you want to add (to the company) is:
  • A primary contact person (for Pay); meaning that this person that will be contact by Pay when there a generic questions regarding which cannot be handled by operational/financial or technical employees. Usually a program manager or a project leader;
  • An internal administrator; will be shown to your users when there a errors or issues.
• The License:Get and License:Browse are retuning this roles object in the output.

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