TabaPay offers bill payments via MasterCard Remote Payment and Presentment Service (RPPS).

The MasterCard Remote Payment and Presentment Service (RPPS), governed by MasterCard International, is a fully electronic solution for bill payment processing that provides electronic routing, posting, and same day settlement of financial transactions.

Use Cases

• Allow your consumers to make frequent payments towards their bills with approved vendors.
• Add a bill payment function to your consumer facing budgeting, or savings platform.

Participants

Bill Payments via RPPS Flow

1. Consumer at the Originator attempts to initiate payment to the Biller. The user experience of the consumer is provided by the Originator, and for the purposes of this workflow, displays interaction between Originator and Consumer.
2. The Originator reviews an online directory with TabaPay (Read RPPS Biller Directory) TabaPay accesses directory at MasterCard RPPS to determine if the Biller can receive payments electronically via the RPPS network.
3. Consumer confirms the payment to the biller. User experience of the consumer is provided by the Originator, and for the purposes of this document, details of the user experience, interaction between Originator and Consumer during biller search etc. is out of scope of this document.
4. The Originator prepares a payment file containing bill payment transactions and sends the file to TabaPay. Validation of records is performed by TabaPay prior to sending a payment file to RPPS.
5. TabaPay sends the file to MasterCard RPPS to process. This includes file and batch editing, account number validation and sorting/batching of payments.
6. The MasterCard RPPS Settlement Bank initiates a Fedwire against the Originator’s bank to retrieve funds in the amount of the payment file after all accounts number validations are complete and inaccurate account numbers have been rejected.
   Note: Settlement occurs once daily at 6 PM PT for the total processing that occurred that day.
7. The MasterCard RPPS Settlement Bank initiates Fedwires to credit the appropriate Biller’s Bank.
8. MasterCard RPPS sends payment files to the appropriate Biller. MasterCard RPPS sends confirmation files to TabaPay confirming transactions received, processed, any rejects from RPPS, returns from Billers, and reasons for the reject or return.
9. The Biller posts the credit to its account receivable.

RPPS Guidelines for Returns

Note: For RPPS Errors, refer to RPPS Exception Codes.

Biller Search using RPPS Biller Directory

1. Originator requests Biller Name and Biller Address from consumer and provides the values to TabaPay in a flat file. Format must be conformant with TabaPay requirements.
2. TabaPay sends the full file RPPS Biller Directory to the Originator.
3. Originator searches for the Biller (using numerical values from the address) using the Biller Name in the Biller Directory file.
4. Once Originator confirms the Biller Name from the Consumer, and requests account number for the Consumer at the Biller, Originator creates bill payment for the biller with TabaPay using the Consumer’s account number in the required format.

Refer RPPS Biller Directory File Format

Originator Payment File

📘

ACH vs RPPs Files

ACH and RPPS share similar file formats. You will see some columns that do not apply to RPPS.

Input File Format:

Sample Input File

Scroll over the table for more columns: ISO, MID, ACH Type, Entry Type, Entry Descriptions, Amount, IIN, First name, Last name, Account type, RTN, Account, Debit-Credit.

Input File Format

Processed File from TabaPay

RPPS Files

File Details

File sharing details will be provided to the client

• yyyymmdd=file date
• N=sequence number (1..n) if multiple files per cycle used
• A=file modifier (A..Z)
• For ISO: Do not use MID
• Comma separator for each field

Cut-off Time

Cut-off time is 2 PM PT.

• File cutoff missed will be moved to next window
• Confirmation of processing emailed to merchant

TabaPay pushes RPPS files via SFTP

SFTP Push - Security options can include:

• Merchant whitelists TabaPay IP
• SFTP ID and Password
• TabaPay public key for SFTP security (ID or ID+PW)

FAQs

FAQs | Transaction Costs

FAQs | Payment File Confirmation

FAQs | File Format

Biller Directory File Format

• Record 0 consists of biller information.
• Record 1 contains biller addresses.
• Record 2 contains biller masks.
• There may be multiple 1 and 2 records associated with a 0 record.
• Each 1 record may contain from 1 to 20 addresses.
• If no biller addresses are available for a biller, no 1 record will be created.
• Each 2 record may contain from 1 to 80 masks for the full and partial downloads, and from 1 to 60 masks for the advanced full download.
• There must be at least one mask for a biller.
• The address record may contain from 1 to 10 addresses, and the mask record may contain from 1 to 25 masks.
• Record 3 contains mask descriptors.
• Record 4 contains AKAs.
• Record 5 contains contacts.
• Record 6 contains phone and fax numbers.
  • There may be multiple 3 records associated with a 2 record, multiple 4 and 5 records associated with a 0 record and multiple 6 records associated with a 5 record.
  • Each 3 record may contain from 1 to 35 mask descriptors.
  • Each 4 record may contain from 1 to 15 AKAs.
  • Each 5 record may contain from 1 to 7 contacts.
  • Each 6 record may contain from 1 to 20 phone numbers.
  • If there is no data for record types 3 through 6, then they will not be created.
  • If a mask has mask descriptors, then that mask will be on a 2 record by itself, and the descriptors will be on one or more 3 records after it.
  • If a contact has phone/fax numbers the contact will be on a 5 record by itself, and the phone/fax numbers will be on one or more 6 records after it.
  • Mask record may contain from 1 to 50 masks and the contact record may contain from 1 to 3 contacts.
  • An 'X0' record will be generated to indicate no data for partial and advanced partial file downloads.
• Mask record may contain from 1 to 50 masks and the contact record may contain from 1 to 3 contacts.
• An 'X0' record will be generated to indicate no data for partial and advanced partial file downloads.

File Layout

Record lengths for the fixed-width format (in bytes):

• Biller - 1450 to 1451
• Biller Address - 232 to 4621 (2311 automated)
• Mask - 46 to 2701 (2251 automated)
• Mask Descriptor - 61 to 2101;
• AKA - 149 to 2221
• Contact - 658 to 4600 (1972 automated)
• Contact Phone - 101 to 2001

Biller Record (0)

Address Record (1)

Biller Mask Record (2)

Biller Mask Descriptor Record (3)

Biller AKA Record (4)

Biller Contact Record (5)

Biller Contact Phone Record (6)

File Layout for Advanced Partial File Type

Record lengths for the fixed-width format(in bytes):

• Biller - 22 to 2072
• Biller Address - 32 to 182
• Mask - 32 to 126
• Mask Descriptor - 42 to 192
• AKA - 32 to 338
• Contact - 32 to 338
• Phone - 42 to 192

No-Data Record