# Remote Payment and Presentment Service (RPPS) Biller Maintenance Service
source: https://developer.mastercard.com/rpps-biller-maintenance-service/documentation/index.md

## Overview {#overview}

This documentation provides an overview of Mastercard Remote Payment and Presentment Service (RPPS) Biller Maintenance Service and details on how to use it. It is written for developers and technical managers who want to learn how to integrate with the Bill Pay platform and be able to manage billers via an API. It enables Concentrators to use their proprietary systems to easily onboard new billers.   

Mastercard Bill Pay is a solution that delivers an intuitive user experience for meeting the everyday bill payment needs of Concentrators and Originators. With innovation and expertise, Mastercard Bill Pay brings together the two sides of the bill pay ecosystem, billers and consumers, and sits between them to facilitate bill payments, bringing transparency, consistency, speed, and simplicity to the bill pay experience.   

See [the product page](https://developer.mastercard.com/product/bill-pay) for marketing and case study details.

## How It Works {#how-it-works}

The Remote Payment and Presentment Service (RPPS) Biller Maintenance Service allows concentrators to add billers to the RPPS system via API. Please note that the effective date (live date) cannot be sooner than 5 business days from the date submitted per business rules.

### Add Biller {#add-biller}

1. A concentrator submits work requests via the RPPS Biller Maintenance Service with an 'Add'.
2. Formatting and rudimentary business rule validations (formatting, length and valid values) are evaluated.
3. Assuming the request results in a successful response, the biller will be submitted and reside in a Work Request state.
4. A successful response is sent back to the Concentrator with the Work Request number.
5. Fine grain business rules will run in the background to determine if all values presented meet the additional requirements.

Concentrator should store this Work Request for use in further review of the secondary business rule validations that may lead to billers being rejected or requiring manual edits (if the biller matches another biller, it is deemed to be a duplicate and will be rejected). While the UI will display no record of the work request if it is rejected, concentrators may use the Work Request Status API to retrieve the billers by Work Request that have been rejected. (see below for the Work Request Status workflow). Alternatively, the Concentrator may manually login to the Mastercard RPPS system and validate that all work requests have been approved and/or some may be in a pending state that can be approved upon further review/edits or may be rejected based on manual matching. Billers may also be rejected because they match certain restricted words that would lead to the payments to illegal billers.
Diagram add

### Edit Biller / Get Biller Details {#edit-biller--get-biller-details}

1. An edit requires certain key fields to update child records such as Remittance Addresses, AKAs, Masks or Mask Descriptions, this is achieved with the GET call to /biller/{biller_id} to get the biller details.
2. The biller details are sent back to the biller to be used in the Edit request and passes biller details back to the concentrator.
3. A concentrator submits work requests via the RPPS Biller Maintenance Service with an 'Edit'.
4. Formatting and rudimentary business rule validations (formatting, length and valid values) are evaluated.
5. Assuming the request results in a successful response, the biller will be submitted and reside in a Work Request state.
6. A successful response is sent back to the Concentrator with the Work Request number.

Concentrator should store this Work Request for their records. Concentrators may use the Work Request Status API to retrieve the status of the Work Request. (see below for the Work Request Status workflow). Alternatively, the Concentrator may manually login to the Mastercard RPPS system.
Diagram edit

### Deactivate Biller {#deactivate-biller}

1. A concentrator submits work requests via the RPPS Biller Maintenance Service with a 'Deactivate'.
2. Formatting and rudimentary business rule validations (formatting, length and valid values) are evaluated.
3. Assuming the request results in a successful response, the biller will be submitted and reside in a Work Request state.
4. A successful response is sent back to the Concentrator with the Work Request number.

Concentrator should store this Work Request for their records. Concentrators may use the Work Request Status API to retrieve the status of the Work Request. (see below for the Work Request Status workflow). Alternatively, the Concentrator may manually login to the Mastercard RPPS system.
Diagram deactivate

### Get Work Request Details {#get-work-request-details}

1. A concentrator calls the GET work-request-statuses/{work_request_ids} path with the Work Request ID to get the state of the work request.
2. Formatting and rudimentary validations (formatting, length and valid values) are evaluated.
3. A successful response is sent back to the Concentrator with the Work Request number.

Diagram getworkrequest

All Approved Work Requests will be in an "Approved" state until the effective date submitted. Once live "Implemented", billers can be edited. If the Concentrator require the billers to be removed from Bill Pay, the ability to Deactivate the biller is available as well.

## Getting Started {#getting-started}

### Before You Start {#before-you-start}

* Your organization must have completed the necessary onboarding and key exchange activities outlined in the [API Basics](https://developer.mastercard.com/rpps-biller-maintenance-service/documentation/api-basics/index.md) section.
* You should have coded against and tested for the Use Cases to get MTF and then Production approval. See [Testing](https://developer.mastercard.com/rpps-biller-maintenance-service/documentation/testing/index.md) for more details.
* Concentrators will be notified at least 3 months in advance of all version updates to the Remote Payment and Presentment Service (RPPS) Biller Maintenance Service.
* Remote Payment and Presentment Service (RPPS) Biller Maintenance Service is currently only available in North America.

### Good to Know {#good-to-know}

In order to control access to the data, it is required that you have already completed and returned the Mastercard Bill Pay agreements and enrollment forms. You must have a Concentrator profile in the Mastercard Testing Facility (MTF) before you can begin testing in the MTF environment. Once MTF testing is completed, you can follow the procedures for moving to Production and then you can begin adding new billers in Production. The client id must be approved for those environments and associated with your Concentrator profile in the respective environment to ensure security protocols are in place.

The Remote Payment and Presentment Service (RPPS) Biller Maintenance Service is developed in an agile manner and is updated regularly with Bill Pay platform enhancements. Every effort is made to ensure backwards-compatibility as changes occur. Updates may dictate that a change will cause impacts. Notifications will be provided with a minimum of 3 months advance notice for non-breaking changes. These releases will allow you to incorporate the changes that are relevant to you if and when you choose to adopt those new capabilities.

## Next Steps {#next-steps}

If you have registered with Bill Pay, have an MCConnect account and profile and are ready to begin onboarding Billers then you will need to create a Mastercard Developers project. This will generate your credentials.

Please proceed to [API Basics](https://developer.mastercard.com/rpps-biller-maintenance-service/documentation/api-basics/index.md).