NEWS & EVENTS
Version 0.4 of the draft technical documentation has been released in the Request to Pay Developer Portal. You can view the updated documents by signing in to the Developer Portal here.
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.4 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 3rd December 2018 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.
Payment Service Providers and billers are today (Thursday 6 September 2018) being invited to register to play their part in developing ‘Request to Pay’ – a new way to improve the control, flexibility and transparency of bill payments.
The Request to Pay portal - www.requesttopay.co.uk - has been launched by Pay.UK, the UK’s leading retail payment authority, which has responsibility to develop best in class payment infrastructure and standards for the benefit of everybody.
Pay.UK is responsible for setting the standards and rules in retail payments and the Request to Pay service is an innovation which will be ready for the market to competitively launch from next year. It is expected to be a secure messaging service for payments - almost akin to email - overlaid on top of existing infrastructure. For each ‘request’, customers will be able to pay in full, pay in part, ask for more time, communicate with the biller, or decline the payment – giving more control to the person being asked to pay. Payers can expect to have a choice of payment methods, or be able to automatically trigger a payment as part of their acceptance of a request.
Potential participants are being invited to review the draft specifications and provide feedback using an API sandbox for the ‘message repositories’ which will play a role in storing, sending and receiving messages, and the ‘end-user applications’ which will make it possible for consumers and businesses to communicate with repositories. Using API (‘application programming interface’) technology as a secure way of sharing data, the proposition is for the Request to Pay service to be underpinned by a single central directory, which will enable registration of participants and identification of the services they provide.
All potential participants’ initial feedback will be used to help inform the draft technical specifications, which are currently provided for illustrative purposes. Two further iterations of documentation are planned to be published on the portal during 2018, as the specifications are further refined. The final versions will be published in early 2019, to enable interested participants to prepare their own competitive launches from spring 2019 onwards.
Paul Horlock, CEO of Pay.UK, said:
“We expect Request to Pay to support individuals with their financial decision-making, create a better channel for direct dialogue between payers and billers, and help more people and businesses avoid the cliff edges that can be created by an irregular income, or an unexpected or unpaid bill.
“By setting the standards and rules needed to make Request to Pay work, Pay.UK will act as a market catalyst, encouraging developers to spot innovative new uses for Request to Pay which could benefit a wide range of sectors – from utilities to financial services, government, charities and beyond.”
The development of the Request to Pay service is one of the end user deliverables being overseen by Pay.UK as part of its role in creating a New Payments Architecture (NPA). Any stakeholders that are interested in finding out more about the NPA, and how Request to Pay fits with the wider project, should visit the Pay.UK website: wearepay.uk
Workshop focusing on the background of Request to Pay, this session was set up for organisations that had expressed interest in the service but had been unable to attend their specific session. The session covers the requirements to run or utilise the service and how third parties can get involved in the future, with example app demonstrations for consumers and large billers.
Workshop focusing on the background of Request to Pay specifically aimed at Fintechs of any size or maturity that could be interested in using the service.
The session covered the requirements to run or utilise the service and how third parties can get involved in the future, with example app demonstrations for consumers and large billers.
Workshop focusing on the background of Request to Pay specifically aimed at government departments and use cases. The session will also cover the requirements to run or utilise the service and how third parties can get involved in the future, with example app demonstrations for consumers and large billers.