Version 0.5 of Technical Documentation released

, 3 January, 219 - 9:0

Version 0.5 of the draft technical documentation has been released in the Request to Pay Developer Portal here. You can view the updated documents by signing in to the Developer Portal. The documents which have been transitioned to version 0.5 are as follows:

  • Request to Pay API Security oAuth
  • Message Definitions Part One
  • Message Definitions Part Two
  • Repository API definitions

We are also hoping at publishing new versions of the Request to Pay Technical Blueprint (which will be renamed to the Request to Pay Service Overview), and the OpenAPI Specification 2.0. We're working on hard on these releases and ensuring that we have incorporated your useful feedback where necessary. We are hoping to publish the new versions shortly.

Changes to the documentation were made following a four week consultation period, in which Developer Portal users were asked to feedback any ideas, suggestions or comments they may have. The feedback was then reviewed here at Pay.UK (the organisation responsible for delivering Request to Pay) and included in the new version where appropriate. There is a change log available in each new document that details exactly what has been changed and where it exists.

Now that version 0.5 of the documents have been published, we are once again asking you for feedback. You can provide this feedback using one of the forms available throughout the site. Your comments are important to us as it means that you can help improve the Request to Pay service, both functionally and technically, to ensure it meets the needs of consumers and businesses across the UK. You will have until the 6 February 2019 to review the current documentation, before we will gather the comments received and begin work on the next version of the documentation. A timeline of the consultation process is also available in the Developer Portal.

We'd like to thank you for all the valuable feedback which you have provided us with so far, and look forward to hearing your thoughts on the latest version of the documentation.