Changelog
Knowledge baseContact
Start typing to search…
Back to All
added

The March update (Week of 13 March)

over 2 years ago by Tom Bossink

We have released quite a big update. Read more below 👏

AuthorisationGroups

We have introduced a new endpoint to retrieve the AuthorisationGroups (https://developer.pay.nl/reference/get_authorisationgroups). If you call this API then you will retrieve PAY.'s public groups. If your account has rights to create own groups, you will also retrieve these groups.

Merchant:Create

We have introduced several enhancements to this endpoint:

  • You can submit one or more clearing accounts
  • You can supply compliance data (e.g. pep indication, ubo status etc) for each person linked to the merchant
  • You can directly create authentication tokens. You can indicate which authorisation groups needs to be linked to this token.
  • The account will be linked to the merchant if there is already an account available for the e-mail address that is supplied. Note; the account needs to accept in the PAY. admin that he/she is related to that company.
  • You can directly indicate which authorisation groups needs to be linked to the account that you have created
  • We return the secrets (ie the token , the service secret and the license secret), these can be used in other API calls.

The full API definition, including some samples can be found here; https://developer.pay.nl/reference/post_merchants

Other improvements

  • The Languages API also returns a link to an image URL
  • The Categories API now returns the initialMCC and initialRiskCategory that is linked to each category
  • The Countries API also returns nationality data, including translations;
  • The Merchant:GetConfig endpoint is removed, instead the Service:GetConfig endpoint is changed. You can authenticate with an AT-code/token or with an SL-code/secret. If AT-code/token is used the serviceID needs to be included in the body parameters. See; https://developer.pay.nl/reference/get_services-config
  • The Service:GetConfig API is enlarged with encryptionKeys
  • If there are no translations available (mainly in the Core API's) we now return translations: null instead of translations:[], since the translations are returned in objects instead of arrays.