Recurring Payments Profile

Overview

The Recurring Payments Profile Report (RPP) is for use by any merchant or payment processing partner, who have integrated the Recurring Payments Product. The Recurring Payments Profile Report gives merchants and processing partners detailed information about outstanding subscribed monthly payments.

The Recurring Payments Profile Report is available through PayPal’s website and Secure FTP Server, which is defined and described in the Secure FTP Server Specification. Recurring Payments are created with PayPal Recurring Payments API, as documented in the NVP API Developer Guide and Reference.

Know before you begin

• The RPP is available via the Secure FTP Server (reports.paypal.com), which requires a separate user account for access to the RPP. A user account that is enabled for the RPP is also enabled to create user accounts for the Secure Drop-Box. To ensure data security, RPP users must generate their own user accounts for the Secure Drop-Box.
• The RPP is generated and delivered by PayPal on a regular (24 hour) basis. With the initial release of the RPP, the RPP is generated and distributed by 9AM daily in the leading timezone of the reporting window.
• You can receive the RPP in either comma separated value (csv) or tab delimited values format (tab). Contact your PayPal Account Manager to set the data format for this report.
• The RPP is available via the Secure FTP Server for 45 days after the date of its delivery.
• The reports character encoding is UTF-8 (8-bit UCS/Unicode Transformation Format).
• The reports are available in these formats:
  • Portable Document Format (PDF)
  • Comma-Separated Values (CSV)

Distribution and access

The following steps describe how to set up and access the RPP using the Secure FTP Server:

1. Create a Secure FTP Server user account. Login to PayPal (www.paypal.com) and create a Secure PayPal Reporting FTP Server username and password. Passwords for accessing the Secure FTP Server cannot be reset by PayPal. To obtain a new password, you must create a new Secure FTP Server user account.

2. Grant access to third-party users. You must explicitly grant access to third-parties by contacting their PayPal Account Manager to supply the following information: – Third-parties’ PayPal login username – Type of permission: reporting access (read) The third-party is then notified by email that access to the business partner’s Secure FTP Server has been granted.

3. Access the Secure FTP Server programmatically using an FTP client. The hostname of the Secure FTP Server is reports.paypal.com. A user account on the Secure FTP Server has the following directory structure: /ppreports/outgoing

New or revised versions

In the future, PayPal will support multiple versions of the RPP. PayPal will notify you regarding the creation of any new version as well as any deprecation of older versions of the report.

If you wish to take advantage of a new version, you can receive two versions of the same report concurrently in order to test and integrate the new version. You can also receive nonconsecutive versions of the same report concurrently in order to test and integrate the new version. Contact your PayPal Account Manager to enable different versions and request any changes in report distribution.

Notifications

PayPal operationally monitors the generation and delivery of the RPP on a 24/7 365 basis. PayPal maintains two different user contact points for report notifications:

• A business contact point for all notifications related to data integrity, data delivery, and new reporting features
• A technical contact for all notifications related to data integrity, data delivery, system outages, system updates, and new features.

PayPal will notify you of the following events related to reporting.

• Delays in report delivery
• Errors in report generation
• New version availability
• System outage
• System update / maintenance (pre-announcement)
• New reporting feature releases

Contact your PayPal Account Manager to provide PayPal with the appropriate notification email alias. PayPal strongly recommends that you create a distribution list or email alias that allows multiple parties to receive communication about the RPP.

Section 1: Report file name

The filename naming convention depends on whether or not you are using Multiple Account Management.

The filename of the RPP for a single account follows this naming convention:

RPP-yyyymmdd.SequenceNumber.Version.Format

When using Multiple Account Management, the filename of the report follows this naming convention:

RPP-yyyymmdd.ReportingWindow.SequenceNumber.TotalFiles.Version.Format

Section 2: File structure

The report can be delivered as either a comma-separated values or tab-delimited file. This section describes the structure of the data file.

A report file can contain a maximum of 1 million records. If the report contains more than 1 million records, the report is split across multiple files. The report is also organized by section, where each section represents a single PayPal account. If you are not using PayPal Multiple Account Management, the report contains only a single section.

Each row of the report consists of a two letter row type, followed by the details specific to that row type. The following table lists the valid row types, along with the sections that describe the data for that row type.

Row types

A report file with fewer than 1 million records (a single file) with only one section is organized as follows:

For report files that are split over multiple files, only the first file has a report header record and only the last file has a report footer and a report record count record. A report with two sections split over two files might be organized as follows:

Section 3: Report data

This section details the columns and related data that is delivered in the report header, report footer, and report record count records.

Report header data

Report header data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Report footer data

Report footer data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Report record count data

Report record count data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Section 4: File data

This section details the columns and related data that is delivered in the file header and file footer records.

File header data

File header data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

File footer data

File footer data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Section 5: Section data

This section details the columns and related data that is delivered in the section header, section footer, and section record count records.

Section header data

All section header data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Section body

Body data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Before any rows of body data in the report, a column header row lists the name of each of the fields in each body data row. The column header column starts with CH, followed by the Column Name for each body data field (except for the column type field). For example:

CH,"Profile ID","Description","Payer Name","Payer Email","Billing Cycles","Currency Code","Amount","Tax Amount","Ship Amount","Profile Status","Billing Period Type","Billing Cycles Remaining","Date Last Paid","Amount Last Paid","Outstanding Balance","Next Bill Date","Num Failed Payment","Date Last Modified"

Section footer data

Section footer data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Section record count data

Section record count data exists in one row with each element being separated by the file delimiter. All report fields are non-blank unless otherwise noted.

Sample CSV report

1"RH",2007/12/05 22:43:15 -0800,"A","QRQJ9CLWCBH3Q",001,<br />
2        FH,01<br />
3        SH,2007/12/03 00:00:00 -0800,2007/12/03 23:59:59 -0800,"QRQJ9CLWCBH3Q"<br />
4        CH,"Profile ID","Description","Payer Name","Payer Email","Billing Cycles","Currency Code","Amount","Tax Amount","Ship Amount","Profile Status","Billing Period Type","Billing Cycles Remaining","Date Last Paid","Amount Last Paid","Outstanding Balance","Next Bill Date","Num Failed Payment","Date Last Modified"<br />
5        SB,"I-6FE511321P0478119","Item6","PrabhaS","pshanmugam-us2-buyer@paypal.com","1Days","USD",500,100,100,"Suspended","Regular",0,"",,100,"",1,"2007/12/0302:00:35 -0800"<br />
6        SF,2<br />
7        SC,2<br />
8        RF,2<br />
9        RC,2<br />
10        FF,2<br />

Version history

See also

• PayPal-supported currencies
• T-codes