1. As you are already contracted to RCMS Core + Claim and the user interface version is fully live and available, have you fully operationalised this in your PSP?*
 
Yes.
No – but we expect to before the end of 2024.
No – but we expect to before the end of Q1 2025.
No – but we expect to before the end of Q2 2025.
We are awaiting guidance from Pay.UK or PSR on a deadline for us to operationalise this.
No, we signed the RCMS Core + Claims contract in anticipation of integrating via API, so are moving towards this.
 
 
 
2. What is holding you back from operationalising RCMS Core + Claims UI?
(Please select all that apply).*
 
Lack of familiarisation / testing environment to train teams in.
We cannot get a budget to operationalise unless PSR mandate the system.
We have planned to do it, but it is not scheduled until later as other projects take priority.
We can’t find any training materials to help us train our staff.
We have found the training materials on DataSite, but they are not sufficient to train our operators.
Anything else not included above (Use free text field)
 
What else is holding you back from operationalising RCMS Core + Claims UI?
 
 
 
 
2.1. You mentioned that you need to access an RCMS Core + Claims UI familiarisation environment to train your operators.
To what degree is this required by your organisation? Please pick a number on the scale, where 1 is not required at all and 10 is a core, immovable dependency.*
 

 
 
 
2.1. Have you processed any claims via RCMS Core + Claims with the counterparty also being on RCMS Core + Claims?*
 
Yes
No
I am not sure
 
 
 
3. For the industry transition to RCMS Core + Claims do you intend to (choose one)*
 
Remain on RCMS Core + Claims UI – accessed via the web-hosted user interface.
Not operationalise RCMS Core + Claims UI, but instead operationalise by implementing RCMS Core + Claims API – and operationalise it via API integration into your own operational screens.
Remain on RCMS Core + Claims initially, and operationalise it inside your PSP, with a view to moving to RCMS Core + Claims API integration after the whole industry has transitioned.
 
 
 
2. Do you have an approved Change project and team in place to support the transition to RCMS Core + Claims API?*
 
Yes
No
 
 
 
2.1. Have your Development and Testing teams received and reviewed the API Specifications?*
 
Yes
No
 
 
 
2.2. Do these final documents now cover all you require to build and run your API solution?*
 
Yes
No
 
 
 
2.3. Please explain to us what is missing or not clear in the API Specifications in the field below.*
 
 
 
 
3. Pay.UK have heard from some customers that they wish to access an RCMS Core + Claims UI familiarisation environment prior to starting their API build, as this provides important context.
To what degree is this required by your organisation?
Please pick a number on the scale, where 1 is not required at all and 10 is a core, immovable dependency.*
 

 
 
 
4. Has any estimation been completed on APPR Design, Development and Testing Build?*
 
Yes
No
 
 
 
5. Please outline your API estimation for Development and Testing timelines.*
 
1-3 months
4-6 months
6-9 months
9-12 months
12+ months
 
 
 
6. When do you expect to begin your API Build?*
 
Already started
Imminently (next four weeks)
Between October - December 2024
Between January - March 2025
From March 2025 onwards
 
 
 
7. When do you expect to complete your API Build and be ready to enter testing? (Please choose one)*
 
By the end of 2024
January 2025
February 2025
March 2025
April 2025
May 2025
June 2025
July 2025
September 2025
Q4 2025
2026
 
 
 
2. When do you think you will start your API project?*
 
Q1 2025
Q2 2025
Q3 2025
Q4 2025
2026
 
 
 
Email*