Search
Close this search box.

RCMS contracting and functionality

FAQs

Red Flag Alert provides the ID verification service. Only publicly available data is checked, and no footprint is left on the individuals record. Biometric information is required as part of the process

Once you have passed ID&V, the contract will be sent via DocuSign to the person listed as your contract signatory in the registration form. This should happen within a maximum of 3 working days of completing ID&V.

Please provide one contract signatory when you complete registration. The contract is sent via DocuSign to that named contract signatory and includes “offline” instructions for those PSPs who need to have two signatories.

Pricing for both RCMS Core, and RCMS Core + Claims can be accessed here: APPR – pricing update to customers (wearepay.uk).  In short, there is no charge for RCMS in 2024.  In 2025 and 2026 we will be recovering costs only via the Faster Payments Systems with billing to direct FPS participants. As use and behaviour data of RMCS builds up, we will move to direct billing, based on use and behaviour, for all RCMS customers.  We expect that the move to direct billing will happen, at latest, in 2027.  Please note, all charges are based on cost-recovery as we are a not for profit organisation.

We have released a Best Practice Guide.  This has been developed in collaboration with the PSR and with industry.  It contains guidance on how to deal with a range of claims scenarios and provides examples of “what good looks like” in dealing with consumers. It will be made available to all PSPs who have registered and passed ID&V. It will be sent out via DataSite.

The PSR’s direction on APP Reimbursement under SD20 is focused on consumers, micro-enterprises and charities. For more information please refer to SD20 on PSR website: https://www.psr.org.uk/publications/legal-directions-and-decisions/app-scams-reimbursement-sd20-on-psps/

We are developing the RCMS system to ensure that PSPs can comply with their obligations under SD20 and we are confident that the system will be available for 7 October launch date. In addition, we are supporting PSPs in being able to register and contract for RCMS in time. However, it is the obligation of all in scope PSPs to ensure that they comply with the deadlines.

There is no cost related to registration

The RCMS does not manage disputes. PSPs can register for RCMS Core or RCMS Core plus Claims. The Core system allows PSPs to submit their monthly claims data from 7 October as required under SD20. It includes the directory of all registered PSPs so that sending PSPs can identify the details of the receiving PSPs they need to contact to manage claims. The Core plus Claims option allows the sending and receiving PSPs to manage the full end to end claims management process within RCMS, provided both parties have signed the Core plus Claims contract.

We will be providing the PSR with regular updates on PSP registrations. If an in-scope PSP has not registered for APPR, or does not respond to a sending bank’s requests, they will be non-compliant to SD20. Sending PSPs should let the RCMS helpdesk know if a Receiving bank is not registered on the RCMS.

The PSR has indicated its support for RCMS to be the single industry solution for APP claims management, but has not yet set a deadline by which in-scope PSPs will have to join the Core+Claims solution. The PSR intends to gather industry feedback later in 2024. Pay.UK is supporting PSPs to move to RCMS Core + Claims as quickly as they wish to and it will be available via web-hosted UI by October 7, and via API integration in January 2025

CHAPS has yet to publish their rules. You will be able to see who is a CHAPS member in the Directory

Until more PSPs have registered and indicated whether they will join RCMS Core or Core plus Claims initially, it is difficult to estimate how many will be on the Claims system for day 1. However, we believe that it will be beneficial for PSPs to join RCMS Core+Claims on day one to allow them to take advantage of the functionality of the full system.

An APP fraud reimbursement claim involving a sending or receiving PSP that is not on RCMS Core plus Claims will require a manual process. It is for that reason that we believe it would be advantageous for the whole industry to be on RCMS Core+Claims as soon as practicable to eliminate the manual element of claims handling.

The expectation is that RCMS Core+Claims will become the single target solution for APP reimbursement claims management. However, we appreciate that SD20 currently only mandates PSPs to join RCMS Core for reporting purposes. Our working assumption is that in-scope PSPs will be mandated to join Core+Claims in 2025, subject to the PSR’s planned consultation in Q4 2024. However, Pay.UK will have everything in place to ensure that all PSPs can move to RCMS Core + Claims ahead of any mandate.

This will be available in the future training information released for firms that have registered and contracted. We caution that this is a simple template to create some standardisation of manual processes; however it is not a fully fledged process document. Only by all customers joining RCMS Core + Claims will operational effectiveness and simplification be achieved for industry.

SD20 only mandates PSPs to use the RCMS Core element for monthly data reporting. Until the mandate is extended to cover Core plus Claims, PSPs can join RCMS Core only and manage their claim processes outside the system. However, we believe it would be advantageous for the whole industry to be on RCMS Core plus Claims as soon as practicable to eliminate the manual element of claims handling.

We are encouraging Sponsor Banks to work with their Indirect PSP clients to ensure they register and claim their sort code and account number combinations. This will avoid the risk of non-compliance, as well as the possibility that the Sponsor receives claims routed to them that should have gone to their Indirect clients. We will be reporting to the PSR on registration against their list of in-scope PSPs. If you have not yet recieved an IAP support pack with information for you to share with your FPS indirect participant clients, please request one by emailing CBDO@wearepay.uk . Materials can be adjusted to match a PSPs corporate branding and tone of voice.

Registration is open and PSPs have until 20 August to register with us to remain compliant to SD20. We expect there will be many PSPs that will register in the final few days. We cannot comment on any possible changes to the regulations, as this is a matter for the Regulator.

It is up to PSPs to determine based on the wording of SD20 whether they are in scope or not. If they are, they have to register with us. If you believe you are out of scope of SD20, please send an email to CBDO@wearepay.uk with the subject line “out of scope” and we will provide you with next steps to formally inform us of that.

The directory search results will indicate whether a PSP is a full RCMS claims+ user or just using the RCMS Core functionality

Unless both sending and receiving banks are on RCMS Core plus Claims, the claim will have to be managed outside the RCMS system. Operational efficiency will be achieved by all PSPs join RCMS Core plus Claims as soon as practicable. Pay.UK is supporting PSPs to move to RCMS Core + Claims as quickly as they wish too and it will be available via web-hosted UI by October 7, and via API integration in January 2025

The RCMS is specifically for APP scam fraud on FPS,. It has been developed to faciliatate compliance with the FPS Reimbursement Rules, and therefore support the APP scams reimbursement policy to deliver the policy outcomes for industry and for victims of fraud. (with CHAPS as a potential later addition once that scheme has developed their rules and approach)

Please register as in scope, pass ID&V and then receive the contract. The contract is a suite of artefacts including security schedule, service outline, Ts and Cs and more. Within the Ts and Cs are the Data Terms which include clauses that create an “intra-participant data sharing agreement”. We proposed this to industry through our legal working group to design the contract. While not technically required, industry agreed that including this was efficient and avoids the need for potentially millions of individual data sharing agreements between the potential more than a thousand PSPs in scope. A Data Assessment for Controllers is also included in the contractual suite to enable PSPs to undertake their own DPIAs. Our BPC summary is being released by the end of August.

“Pay.UK is a Recognised Payment System Operator for the UK. The systems that we operate are used by such a large number of entities that we cannot complete lengthy questionnaires on an individual basis. This even applies when PSPs join our core payment systems. However, the contract artefacts includes a security schedule, service schedule, data terms and other relevant information, specific to the RCMS for PSPs to conduct their due diligence. PSPs must register as in scope of SD20 and pass ID&V to receive the contract for review, governance and signing.
Public information about Pay.UK applicable to any due diligence appraisal is also available. In particular, we are the owner and operator of the UK’s digital inter-bank retail payment infrastructure and are heavily regulated by multiple regulatory bodies, including the Bank of England, the Payment Services Regulator and His Majesty’s Treasury. A useful description of the Bank of England’s regulatory oversight of us is Financial market infrastructure supervision | Bank of England
We are required to provide attestations to ensure that our processes are at the required standards here – Self-Assessment-Against-The-Principles-For-Financial-Market-Infrastructures-–-2023.pdf (wearepay.uk)
You can also find our Annual Reports, detailing our Risk and Compliance posture, our Governance structure and our Financial statements, at this link: https://www.wearepay.uk/who-we-are/corporate-information/ – and our not-for-profit status.”

The final decision remains with the sending PSP, but the receiving PSP will have the opportunity to discuss and provide their input to the sending PSP as part of the claim decision making process. Please refer to the FPS reimbursement rules for details.

Please register as in scope, pass ID&V and then activate the DataSite registration that we will send to you. DataSite holds a large amount of useful and detailed information to help PSPs prepare for October 7 2024, including detailed information on the functional specifications of RCMS. Please note near-final API specifications are also now available to allow PSPs to design and scope the build of their API integration ahead of the APIs going live in January 2025.

We are making it as easy as possible for PSPs to register and comply with SD20. Before being given access to the live system, they will have to have passed ID and Verification (ID&V) checks that ensures they are bona fide in-scope PSPs.

Calculations surrounding excess have been built into the RCMS. Once registered and contracted for RCMS, PSPs will have access via DataSite to training material and helpful guides on using the system.

Calculations surrounding excess have been built into the RCMS. Once registered and contracted for RCMS, PSPs will have access via DataSite to training material and helpful guides on using the system.

The account number requested on the registration form is added to the directory, so that Receiving PSPs are able to search for the Sending PSP’s account details where the Reimbursable Contribution needs to be sent to. Even if you believe that your organisation is only ever going to be a receiving PSP, please complete this information anyway. The APP scam reimbursement policy is a world-first and we want to prepare for every eventuality to reduce potential future friction.

Once registered and contracted for RCMS, PSPs will have access via DataSite to training material and helpful guides on using the system.

Please see the FAQs on RCMS registration and Directory Set up available on our website. More detailed information is also available via DataSite to PSPs who have registered and passed ID&V.

Once registered and contracted for RCMS, PSPs will have access via DataSite to training material and helpful guides on using the system.

There is a 2-way comments facility for any notes etc. There is currently no ability within the RCMS to attach files.

Until all PSPs are using RCMS Core plus Claims to manage their claims processes, all PSPs have to use RCMS Core to report their claims data on a monthly basis (Reporting Standard A). Once all PSPs are on the full system, the reporting will be automated via the RCMS Core plus Claims.

Yes. System Administrators can grant users the relevant role access in the system.

This is included in the Best Practice Guide, which is available on DataSite once you have registered and passed ID&V

Yes, this is possible.

Information on this will be available via the training materials and a demo to show how multiple payments are added will be scheduled in due course. Each payment will need to be added one by one. Please register to receive the first release of training materials.

Information on this will be available via Datasite once you have registered and passed ID&V.

Information is only visible between the parties involved in the claim.

Please consult the APP Reimbursement Rules available on the Pay.UK website and the RCMS training guide. The repartriation journey in the RCMS can be triggered mid-workflow or after the claim has been closed.

Once registered and contracted for RCMS, PSPs will have access via DataSite to training material and helpful guides on using the system.

The directory search results will indicate whether a PSP is a full RCMS claims+ user or just using the core functionality in which case the claim will need to be manually worked through. Contact details of the Receiving PSP (if registered) will be available on the directory.

If the Indirect PSP has not registered and claimed the sort codes and account numbers for which it is responsible, claims for these accounts will be routed by default to the Sponsor. For this reason, we are encouraging Sponsors to work with their PSP clients to ensure they have registered and claimed the accounts that are theirs.

Once registered and contracted for RCMS, PSPs will have access via DataSite to training material and helpful guides on using the system.

Changes can be made after registration within the RCMS platform. Only major changes may require assistance from Pay.UK help desk otherwise the process is simple.

It is only possible to supply one reimbursement account. If you use multiple accounts, due to multiple brands, we suggest you register separate brands as separate entities and have a separate instance of the RCMS for each of these.

This is included in the data model published 30 July, along with V1 of the solution architecture

When users search the PSP directory, the directory will identify ‘no results’ have been found if the sort code is not found in the directory. The user will then need to raise a ticket through our help desk. If the sort code/account is found but has specifically been marked as out of scope by a PSP, then the ‘In scope?’ field will state ‘N’.

Yes, the process to be used by PSPs where one of the PSPs is not using Core+Claims is detailed under the ‘Operational Readiness’ chapter within the Best Practice Guide. For clarity, if either PSP is not using RCMS Core+Claims, the claim will need to be managed offline and there is no functionality in the RCMS to be able to store responses for claims being managed offline. PSPs will need to do this on their internal systems. We will be providing templates to PSPs so that the offline communication between PSPs can be streamlined.

Information on this will be available via the training materials and a demo to show how multiple payments are added will be scheduled in due course. Each payment will need to be added one by one. Please register to receive the first release of training materials.

If you do not send or receive via FPS at all, then please wait for the CHAPS rules to be published. However, all PSPs that send or receive payments via FPS should assess whether they are in scope of SD20. The RCMS does not yet cover CHAPs workflows, but these are intended to be implemented soon.

Yes, that is correct.  There is no attachment facility due to security reasons.  There are other free text fields as we progress the claim where further text can be sent between Sending and Receiving PSPs

Advanced reimbursement is a decision made by the sending PSP to refund their consumer before the Opportunity to Respond window closes for the receiving PSP. This means the Sending bank is reimbursing at risk and does not have to take into consideration excess or max cap.

The RCMS offers notifications via the UI. Email notifications will be included in Release 2. Further detail on this will be available via the training materials. Please register to receive the first release of training materials.

Please see the API folder in the SharePoint folder marked “RCMS API specifications”. If you do not have access to SharePoint, but intend to implement via API, please email CBDO@wearepay.uk to tell us this so we can help you.

Dashboards are being developed in Release 2 so users can have an aggregated view of the status of claims.

Status notifications are under consideration for Release 2.

Yes, the RCMS uses £100 excess by default. If the PSP user wishes to change this, they will be able to do so at claim level.

The RCMS Payment ID will be 18 characters in Release 2 so that this can be added to the Faster Payment as a reference. More detail on this will be included in the training guide.

Each case created has a unique claim ID so PSPs can use this by default, but the directory provides an option for all PSPs to add a format for references if they want PSPs to use a specific reference format.

Sending PSPs can use this field to notify Receiving PSPs of the ‘format’ they wish Receiving PSPs to use when sending the reimbursable contribution.

Correct, you will need the compliance user role. Please register by 20 August and once the RCMS contract has been signed, you will receive an email detailing the activation steps where the Service Administrator role can be set up. The Service Administrator can then set up the compliance user role, along with the other role types offered within the RCMS.

All registered PSPs whether direct or indirect will be listed on the Directory. There is a reliance on all in scope PSPs registering, contracting, and activating themselves on the RCMS platform to populate the directory and validating the data effectively.

“We will be hosting multiple demonstrations to showcase the capabilities of the RCMS Core+Claims including stop the clock, please register your interest using this link: www.wearepay.uk/rcms/.
Alternatively, screenshots of the RCMS will be included in the training materials. Please register to access the training materials.”

The Stop the clock function can still be used by the Sending PSP and managed offline. The FPS Reimbursement Rules are system agnostic, so they apply irrespective of a solution being used.

Yes, time stamps against stop the clock will be shown in ‘case history’ within the RCMS.

Please refer to the FPS Reimbursement Rules (on the Pay.UK website) for details on timings. Further details and examples are included in the Best Practice Guide which can be accessed once a PSP has registered.

The EISCD contains within it secondary reference data which will be populated in the directory for registered PSPs. It is vital that all registered PSPs review and validate this data to ensure the PSP directory is kept updated and the data within it is valid.

Frequently asked questions (FAQs)
Skip to content