Slated to launch next year, Request to Pay 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. Payers will also get a choice of payment methods, or be able to automatically trigger a payment as part of their acceptance of a request.

The NPSO has opened up a portal for the new initiative, inviting Payment Service Providers and billers to register and review the draft specifications and provide feedback using an API sandbox for the ‘message repositories’ and the ‘end-user applications’.

Using API 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, says the NPSO.

Paul Horlock, CEO, NPSO, says: "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, the NPSO 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."