Documentation about `statsdata.object` confusing about sdk

[escruickshank]

Hi! Thank you for being a partner of Pay.
Those are quite a few questions! It might be easier to answer these via an eMeeting. Please can you book some time with me via this link https://www.pay.nl/meetings/ellen-cruickshank I will be happy to talk you through our system.

[remcotolsma]

That is not necessary, we understand from your colleague Fréderique or another colleague that you are proud of your documentation. Perhaps you can improve the documentation based on these questions? I assume that's why Fréderique and/or colleague asked us to share our feedback?

[escruickshank]

Hi! We have processed the feedback where relevant. Thank you for your input.

[remcotolsma]

Can you elaborate a bit on how the feedback was processed? We can't see improvements / changes in the documentation yet? There's no rush, but it would be nice if our questions were answered in the documentation. We regularly consult the documentation when writing code and solving problems.

[escruickshank]

Hi! We have adjusted the statsdata to statsData on https://docs.pay.nl/developers#mandatory-data-technical-partners and we have clarified the correct character limit (64) on https://developer.pay.nl/docs/glossary-1#stats-parameters.

[remcotolsma]

Thanks for that. This still leaves a number of questions unanswered. Do the open questions still have your attention? For example, the story behind the 2 APIs: https://rest.pay.nl/v1/ and https://rest-api.pay.nl/v16/. What is the idea behind it and what are your plans for it?

[escruickshank]

Hi! No problem at all. I will respond to the other questions via mail, as this is not the appropriate platform to discuss strategic decisions. Thank you again for your input, I will close this issue now.

[remcotolsma]

I don't want to discuss your strategic decisions, but some explanation and background information about the choices made is useful for all users of your API. I don't see why you can't share that here or in the documentation, I think all API users would benefit from that. But by e-mail is also fine, I can be reached via [email protected].