Bill Payments using RPPS
Overview
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.
Participants
Participant | Detail |
---|---|
Originator/Originator Bank | The Originator originates payment transactions to RPPS using TabaPay as the service
provider to originate payments files to RPPS. The Originator’s Bank is a financial institution used by any Originator. It is the institution from which the MasterCard Settlement Bank obtains funds via a Fedwire to credit Receivers for payment files sent through the RPPS network. If an Originator is unable to fund payments sent through the RPPS network, the Originator’s Bank would be responsible for guaranteeing the funds for the Originator. |
Biller | The Biller is a company to which a MasterCard RPPS payment transaction is sent |
Biller’s Bank | A Biller’s Bank is a financial institution that receives payments on behalf of a Biller from an Originator via the RPPS network. |
TabaPay | TabaPay is the Originator’s Service Provider connecting to MasterCard RPPS for bill payments originated to the Biller via RPPS. |
MasterCard RPPS | MasterCard RPPS maintains all connections between Originators and Receivers to transmit data and funds. It allows all parties involved to have one connection to reach multiple Originators and Billers, and maintains all connections, performs extensive edit checks on all files and payment transactions, batches and sends all files, and initiates all settlement transactions. |
MasterCard RPPS Settlement Bank | The MasterCard Settlement Bank is the financial institution used by RPPS to initiate Fed wires to all Originators’ Settlement Banks and to credit all Receivers for payment files sent through the RPPS network. The MasterCard Settlement Bank sends Fed wires for the value of payments transferred through the MasterCard RPPS network to the appropriate Receivers. The MasterCard Settlement Bank is an agent of MasterCard RPPS and has an agreement with MasterCard RPPS to provide settlement services on its behalf |
How it Works


1 Consumer at the Originator attempts to initiate 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. |
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 California time 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. |
Considerations
Topic | Considerations |
---|---|
Returns | Billers can return any payment sent through TabaPay and the RPPS system. Any payment not posted within 24 hours by the Biller is electronically returned via the RPPS network. RPPS routes it back to the correct Originator. MasterCard RPPS also allows partial returns. These may be used for various reasons, such as discounts, commissions, rebates, or fees. The Biller can electronically return any payment to the Originator through TabaPay and RPPS network. Each returned payment includes a return code that provides the reason the payment is being returned. Payments may be returned if the Biller is unable to post the payment, as may occur if an invalid account number or closed account number is used. Errors and resulting payment disputes are minimized because MasterCard RPPS edits all transaction files prior to sending them to the Biller’s Bank. However, a Biller can return any payment to an Originator via the RPPS network/TabaPay. |
Guaranteed Funds | All funds to match payment files sent through MasterCard RPPS are transferred via Fedwire; hence, they are guaranteed funds. |
Soft Descriptor | Every Bill Payment will appear as “Bill Payment” in the consumer’s statement. Biller Search using RPPS Biller Directory |
Biller Search using RPPS Biller Directory


- 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.
- TabaPay searches RPPS Biller Directory for the Biller (using numerical values from the address) and returns Biller Name to the Originator.
- 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.
Contact your TabaPay representative to obtain samples for the flat files to search billers.
RPPS File Formats & Samples
Originator Payment File
Sample data
ISO |
MID |
ACH Type |
Entry Type |
Entry Description |
Amount |
IIN |
First name |
Last name |
Account type |
RTN |
Account |
Debit-Credit |
---|---|---|---|---|---|---|---|---|---|---|---|---|
6281 |
21 |
N |
RPPS |
205 |
rpps0000496 |
Samwise |
Gamgee |
RP |
123456789 |
4444444444 |
C |
|
6281 |
21 |
N |
RPPS |
443.89 |
rpps0000497 |
Samwise |
Gamgee |
RP |
123456789 |
4444444445 |
C |
|
6281 |
21 |
N |
RPPS |
5.03 |
rpps0000498 |
Samwise |
Gamgee |
RP |
233456789 |
3333333335 |
C |
|
6281 |
21 |
N |
RPPS |
6.81 |
rpps0000499 |
Samwise |
Gamgee |
RP |
123456789 |
4444444445 |
C |
|
6281 |
21 |
N |
RPPS |
155.4 |
rpps0000500 |
Samwise |
Gamgee |
RP |
*0002380203 |
*56789 |
C |
|
6281 |
21 |
N |
RPPS |
68.93 |
rpps0000501 |
Samwise |
Gamgee |
RP |
*0002380203 |
*56780 |
C |
File header record
Field # |
Field position |
Field Size |
Content/Format |
Example |
Remarks |
---|---|---|---|---|---|
|
1 |
1 |
Numeric |
Record Type Code |
1 |
|
2-3 |
2 |
Numeric |
Priority Code |
01 |
|
4-13 |
10 |
Alphanumeric |
Immediate Destination |
“ “ + 999900004 |
|
14-23 |
10 |
Alphanumeric |
Immediate Origin |
Bank properties RPPS-ID |
|
24-29 |
6 |
YYMMDD |
Transmission date |
YYMMDD |
|
30-33 |
4 |
HHMM |
Transmission Time |
HHMM |
|
34 |
1 |
Alphanumeric |
File modifier |
User input |
|
35-37 |
3 |
Numeric |
Record size |
094 |
|
38-39 |
2 |
Numeric |
Blocking factor |
10 |
|
40 |
1 |
Numeric |
Format code |
1 |
|
41-63 |
23 |
Alphabet |
Destination |
MC REMIT PROC CENT SITE |
|
64-86 |
23 |
Alphabet |
Original Name |
TabaPay INC |
|
87-94 |
8 |
Alphanumeric |
Reference code |
YYMMDDD-File modifier |
Batch header
Field # |
Field position |
Field Size |
Content/Format |
Example |
Remarks |
---|---|---|---|---|---|
|
1 |
1 |
Numeric |
Record Type Code |
5 |
|
2-4 |
3 |
Numeric |
Service Class Code |
220 Credit, 225 Debit |
|
5-20 |
16 |
Alphanumeric |
Biller Name |
Left justified, with blank |
|
21-40 |
20 |
|
Reserved |
Blank |
|
41-50 |
10 |
AN |
Biller ID |
|
|
51-53 |
3 |
A |
Entry Class |
CIE |
|
64-63 |
10 |
A |
Entry Description |
RPS PAYMNT or REVERSAL |
|
64-69 |
6 |
O/AN |
Biller Descriptive Date |
YYMMDD |
|
70-75 |
6 |
N |
Transmission Date |
YYMMDD |
|
76-78 |
3 |
|
Reserved |
Blank |
|
79 |
1 |
N |
Originator Status code |
1 |
|
80-87 |
8 |
N |
MC RPPS ID |
|
|
88-94 |
7 |
N |
Batch number |
Unique per file |
Detail Record
Field # |
Field position |
Field Size |
Content/Format |
Example |
Remarks |
---|---|---|---|---|---|
|
1 |
1 |
Numeric |
Record Type Code |
6 |
|
2-3 |
2 |
N |
Transaction Code |
22 Credit. 27 Debit |
|
4-29 |
26 |
X |
Reserved |
Blank |
|
30-39 |
10 |
N |
Net amount |
2 decimal pl |
|
40-54 |
15 |
AN |
Consumer name |
CIE format |
|
55-76 |
22 |
AN |
Acct number |
|
|
77-78 |
2 |
X |
|
Blank |
|
79 |
1 |
N |
Addenda record |
0 |
|
80-94 |
15 |
N |
Trace Number |
|
Batch control
Field # |
Field position |
Field Size |
Content/Format |
Example |
Remarks |
---|---|---|---|---|---|
|
1 |
1 |
Numeric |
Record Type Code |
8 |
|
2-4 |
3 |
N |
Service code |
220-credit. 225-debit |
|
5-10 |
6 |
N |
Entry count |
# entries |
|
11-20 |
10 |
|
|
blanks |
|
21-32 |
12 |
N |
Sum debit amt |
2 decimals |
|
33-44 |
12 |
N |
Sum credit amt |
2 decimals |
|
45-54 |
10 |
AN |
Biller id |
|
|
55-79 |
25 |
|
|
|
|
80-87 |
8 |
N |
RPPS ID |
Bank properties |
|
88-94 |
7 |
N |
Batch number |
Match header |
File control
Field # |
Field position |
Field Size |
Content/Format |
Example |
Remarks |
---|---|---|---|---|---|
|
1 |
1 |
Numeric |
Record Type Code |
9 |
|
2-7 |
6 |
N |
Batch count |
# batches |
|
8-13 |
6 |
N |
Block count |
blank |
|
14-21 |
8 |
N |
Entry count |
#entries |
|
22-31 |
10 |
N |
Hash |
|
|
32-43 |
12 |
N |
Sum debit amt |
2 decimals |
|
44-55 |
12 |
N |
Sum credit amt |
2 decimals |
|
56-94 |
30 |
|
Reserved |
|
RPPS Error Codes
Description |
|
---|---|
R01 |
Insufficient Funds |
R02 |
Customer account closed |
R03 |
No account |
R04 |
Invalid account number |
R05 |
No pre-notification on file |
R06 |
Returned in accordance with originator request |
R07 |
Authorization previously permitted revoked by customer |
R08 |
Payment stopped or stop payment on item |
R09 |
Uncollected funds |
R10 |
Customer advises not authorized |
R12 |
Branch sold to another DFI |
R14 |
Representative payee deceased |
R15 |
Individual (beneficiary) deceased |
R16 |
Account frozen |
R17 |
File record edit criteria |
R18 |
Improper effective entry date |
R19 |
Amount field error |
R20 |
Non-transaction account |
R21 |
Invalid biller identification number |
R22 |
Invalid account number |
R23 |
Payment refused by biller |
R24 |
Duplicate entry |
R25 |
Invalid fair share amount |
R26 |
Erroneous data |
R29 |
Corporate customer advises not authorized |
R31 |
Permissible return entry (CCD only) |
R42 |
Routing number/check digit error |
R43 |
Invalid DFI account number |
R61 |
Misrouted return |
R62 |
Incorrect trace number |
R63 |
Incorrect dollar amount |
R64 |
Incorrect individual identification |
R65 |
Incorrect transaction code |
R66 |
Incorrect company identification |
R67 |
Duplicate return |
R68 |
Untimely return |
R69 |
Multiple errors |
R70 |
Permissible return entry not accepted |
R71 |
Misrouted dishonored return |
R72 |
Untimely dishonored return |
R73 |
Timely original return |
R74 |
Corrected return |
R80 |
Cross-border payment coding error |
R81 |
Non-participant in cross-border program |
R82 |
Invalid foreign receiving DFI identification |
R83 |
Foreign receiving DFI unable to settle |
R84 |
Entry not processed |
R95 |
Rebate of fair share from creditor |
C01 |
Incorrect DFI account number |
C02 |
Incorrect routing number |
C03 |
Incorrect routing number and DFI account number |
C04 |
Incorrect individual name/receiving company name |
C05 |
Incorrect transaction code |
C06 |
Incorrect DFI account number and incorrect transaction code |
C07 |
Incorrect routing number incorrect DFI account number and incorrect transaction cod |
C08 |
Incorrect foreign receiving DFI identification (CBR and PBR only) |
C09 |
Incorrect customer account number |
C10 |
Incorrect company name |
C11 |
Incorrect company identification number (biller identification number) |
C12 |
Incorrect company name and company identification |
C50 |
Automated‚ Account Conversion: Customer account number incorrect |
C51 |
Automated, Account Conversion: Biller ID incorrect |
C52 |
Automated, Account Conversion: Customer account number and Biller ID incorrect |
C68 |
DFI account number not from original entry detail record |
FAQs
FAQs | Transaction Costs
What is the cost of each bill pay transaction through Tabapay?
Standard RPPS costs + TabaPay Markup based on contract
Will I be charged if a transaction is returned or rejected?
You will pay for every transaction that MasterCard charges; No separate TabaPay or MasterCard charges on Returns.
FAQs | Payment File Confirmation
When payments are processed, rejected, or returned how long will it take for TabaPay to inform us?
TabaPay’s cutoff is 6 PM PT, and you should receive the processed file after the nightly batch at about 6:30 PM. You will receive other reports next morning via Dropbox.
How will those payment updates be shared?
SFTP via Dropbox
FAQs | File Format
Is Account the Bill Pay Account number linking Consumer and Biller?
Yes. Account number matches against biller masks in the Mastercard RPPS Biller/Creditor Directory.
Debit/Credit designator – is this telling us that the Biller accepts Debit or Credit cards?
Credit is a payment, Debit is a reversal.
If so, where would we send the credit card number in the payment file?
Not in the payment file, but TabaPay can help you with processing consumer credit card payments through TabaPay as well. Our card acceptance suite includes PCI-Compliant iFrames as well as APIs to place transactions with us.
Does TabaPay initiate the credit card transaction to pay the biller?
Payment to the biller is handled by the network.
Updated 4 months ago