Transaction Detail report

The Transaction Detail report provides merchants and payment processing partners with detailed information about every transaction that occurs in an account, regardless of whether it affects the balance. The report also summarizes debits and credits for each currency that the account holds and provides details about individual payments that are made for any single day in the preceding 45 days.

The following specifications apply to this report:

This report uses UTF-8 character encoding (8-bit UCS/Unicode Transformation Format).
PayPal generates this report on a daily (24-hour) basis, and it is available by 12:00 PM daily in the leading time zone of the reporting window. SFTP reports are in the /ppreports/outgoing directory.
This report is available in the Secure Dropbox for 45 days after delivery.
The report is available in CSV (comma-separated values) or TAB (tab-delimited) format. To set your data format, contact your PayPal account manager or customer support.
This report includes alternative payment methods (APMs). For more information about APMs, see the list of supported APMs.
All fields of type varchar are surrounded with double quotation marks, regardless of the field delimiter. Double quotation marks inside a field are represented as two double quotation marks in succession.
Fields that can contain spaces are indicated in the field descriptions in the following tables. All other fields must not contain spaces. For example, the transaction_id field cannot contain spaces, while the transaction_note field can contain spaces.

Prerequisites

Before you use the Transaction Detail report, ensure that you meet the following requirements:

You must be an approved merchant to use this report. To request access, contact your PayPal account manager or customer support.
You must have an SFTP account to access the report on the SFTP server. For more information about accessing SFTP reports, see Access SFTP reports.

New or revised versions

When PayPal supports multiple versions of this report, PayPal will notify you of the creation of any new version and of the deprecation of older versions. When multiple versions exist, you can receive 2 versions of the same report concurrently to test and integrate a new version. You can also receive non-consecutive versions of the same report concurrently. To enable different versions or request changes in report distribution, contact your PayPal account manager or customer support.

Notifications

PayPal monitors the generation and delivery of this report at all times and maintains 2 contact points for notifications:

A business contact for all notifications that relate to data integrity, data delivery, and new reporting features
A technical contact for all notifications that relate to data integrity, data delivery, system outages, system updates, and new features

PayPal notifies you of the following types of events:

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

PayPal strongly recommends that you create a distribution list or email alias that allows multiple parties to receive communication about reports. To provide the appropriate notification email alias, contact your PayPal account manager or customer support.

Report file name

The file naming convention depends on whether you are using Multiple Account Management (MAM).

Single account report

For a single account, the file name follows this convention:

TRR-yyyymmdd.sequenceNumber.version.format

Field, Description
Field	Description
`TRR`	Abbreviation for "Transaction Detail report"
`yyyymmdd`	The date of the data in the report. This date stamp represents the latest, or ending, date of the data.
`sequenceNumber`	The sequence number of the file. 2 characters, right-justified, and zero-filled. Begins with `01` and increments until all parts are recorded. Always present, even if there is only 1 file.
`version`	The version of the report. 3 characters, right-justified, and zero-filled.
`format`	The report format: `CSV` (comma-separated values) or `TAB` (tab-delimited)

Multiple account report

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

TRR-yyyymmdd.reportingWindow.sequenceNumber.totalFiles.version.format

Field, Description
Field	Description
`TRR`	Abbreviation for "Transaction Detail Report"
`yyyymmdd`	The date of the data in the report. This date stamp represents the latest, or ending, date of the report data.
`reportingWindow`	The window of time when the report was generated: `A` (America/New York to America/Los Angeles), `H` (America/Los Angeles to Asia/Hong Kong), `R` (Asia/Hong Kong to Europe/London), or `X` (Europe/London to America/New York)
`sequenceNumber`	The sequence number of the file. 2 characters, right-justified, and zero-filled. Begins with `01` and increments until all parts are recorded. Always present, even if there is only 1 file.
`totalFiles`	The total number of files for this date. Always 2 digits and zero-padded. For example, `02` for 2 total files.
`version`	The version of the report. 3 characters, right-justified, and zero-filled.
`format`	The report format: `CSV` (comma-separated values) or `TAB` (tab-delimited)

Report file structure

A Transaction Detail report file can contain a maximum of 1 million records. If the report contains more records, it 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 Multiple Account Management, the report contains only a single section.

Each row consists of a two-letter row type code that is followed by the details for that row type.

The FH, SC, RC, and RF rows are not available in Transaction Detail report version 001.

Row types

The following table lists the valid row type codes for this report. Each code identifies the type of data in that row.

Code, Description, Section
Code	Description	Section
`RH`	Report header	Report header data
`FH`	File header	File header data
`SH`	Section header	Section header data
`CH`	Column header	Section body data
`SB`	Row data	Section body data
`SF`	Section footer	Section footer data
`SC`	Section record count	Section record count data
`RF`	Report footer	Report footer data
`RC`	Report record count	Report record count data
`FF`	File footer	File footer data

Single file report structure

When the report contains fewer than 1 million records, it is a single file with 1 section, organized as follows.

RH  Report header
FH  File header
SH  Section header
CH  Column header
SB  Row data
... (additional row data)
SF  Section footer
SC  Section record count
RF  Report footer
RC  Report record count
FF  File footer

Multi-file report structure

For reports that split across multiple files, only the first file contains the report header, and only the last file contains the report footer and report record count. The following example shows the structure for a 2-section report that is split across 2 files.

File 1, File 2
File 1	File 2
`RH` Report header	`FH` File header
`FH` File header	`SB` Row data
`SH` Section header	...
`CH` Column header	`SB` Row data
`SB` Row data	`SF` Section footer
...	`SC` Section record count
`SB` Row data	`RF` Report footer
`SF` Section footer	`RC` Report record count
`SC` Section record count	`FF` File footer
`SH` Section header
`CH` Column header
`SB` Row data
...
`FF` File footer

Report data

This section describes the data that is in the report header, report footer, and report record count rows. If the report splits across multiple files, only the last file contains the report footer and report record count rows.

Money amount fields in this report are unsigned, and they include no currency symbol, decimal separator, or other punctuation. For example, the report represents both 100 Yen and $100.00 as 10000. Use the associated credit or debit field to interpret the direction of an amount. For shipping, tax, and insurance amounts, the direction always matches the gross transaction amount.

Report header data

The report header identifies the report and the account that received it. It appears once at the beginning of the first file. All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (report header, `RH`)
2	`report_generation_date`	Date/time	The date and time the report file was generated, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
3	`reporting_window`	Varchar	The window of time when the report was generated: `A` (America/New York to America/Los Angeles), `H` (America/Los Angeles to Asia/Hong Kong), `R` (Asia/Hong Kong to Europe/London), or `X` (Europe/London to America/New York)
4	`account_id`	Varchar	The account number that receives the report (Payer ID is the encrypted hash of the PayPal account.)
5	`report_version`	Varchar	The version of the report

The report footer contains a total row count for the report. You can use it to verify that you received all records.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (report footer, `RF`)
2	`row_count`	Number	The number of body data rows in the report. You can use this for reconciliation. The report may span multiple files.

Report record count data

The report record count provides a second total row count for the entire report, also used for reconciliation. All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (report record count, `RC`)
2	`row_count`	Number	The number of body data rows in the report. You can use this for reconciliation. The report may span multiple files.

File data

This section describes the data in the file header and file footer rows. Each file in the report has a file header and file footer, even if the report contains only 1 file.

File header data

The file header identifies the sequence number of each file in the report. It appears at the beginning of every file. All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (file header, `FH`)
2	`file_count`	Number	The sequence number of the file in the report. You can use this for reconciliation.

File footer data

The file footer contains a row count for the individual file. You can use this to verify that you received all records in that file.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (file footer, `FF`)
2	`row_count`	Number	The number of body data rows in the file. You can use this for reconciliation.

Section data

This section describes the data in the section header, section footer, and section record count rows. If you are not using Multiple Account Management, the report contains only 1 section.

Section header data

The section header identifies the reporting period and account for the section. It appears once for each section.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (section header, `SH`)
2	`reporting_period_start_date`	Date/time	The beginning of the reporting period, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
3	`reporting_period_end_date`	Date/time	The end of the reporting period, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
4	`account_id`	Varchar	Account number that PayPal generated
5	`partner_account_id`	Varchar; blanks allowed; max 127 characters	The partner's account ID for the merchant. This is the value that the partner passes in the `<PartnerMerchantExternalID>` tag of the Multiple Account Management batch input file.

Section body data

The section body contains one row for each transaction, covering all transactions in the account during the reporting period, regardless of whether they affect the balance. Before the body data rows, a column header row (CH) lists the name of each field.

For transactions with associated disputes, claimant information appears only in the dispute report, not in the settlement report or transaction detail report.

Position, Field name, Data characteristics, Description
Position	Field name	Data characteristics	Description
1	`column_type`	Literal	The column type (section body, `SB`)
2	`transaction_id`	Varchar; blanks allowed; max 24 characters	Transaction ID of the money movement event. PayPal generates this ID, and a merchant cannot alter it.
3	`invoice_id`	Text; blanks allowed; max 127 characters	Invoice ID that the merchant sets for the transaction. If the merchant sent an invoice ID with the capture request, that value is reported here. Otherwise, the value of the invoice ID (if any) from the authorizing transaction is reported here.
4	`paypal_reference_id`	Varchar; blanks allowed; max 24 characters	A PayPal reference ID that identifies a related, existing transaction or event from which this event originated. For more information about reference events, see Reference IDs.
5	`paypal_reference_id_type`	Text; blanks allowed; max 3 characters	The type of the PayPal reference ID: `ODR` (order ID), `TXN` (transaction ID), `SUB` (subscription ID), or `PAP` (preapproved payment ID)
6	`transaction_event_code`	Alphanumeric; max 5 characters	Transaction event type (T-code). For a complete list of transaction event codes, see T-codes.
7	`transaction_initiation_date`	Date/time; blanks allowed; max 25 characters	Date and time when the transaction was initiated, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
8	`transaction_completion_date`	Date/time; blanks allowed; max 25 characters	Date and time the transaction was completed, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
9	`transaction_debit_or_credit`	Literal; max 2 characters	Direction of money movement for the gross amount: `CR` (credit) or `DR` (debit)
10	`gross_transaction_amount`	Money; max 26 characters	The payment amount before fees. This field contains the gross transaction value for all transactions. Handling fees and other non-transactional fees are reported as gross amounts with no corresponding fee column entry. For more information, see T-codes.
11	`gross_transaction_currency`	3-character currency code; max 3 characters	Currency of the transaction
12	`fee_debit_or_credit`	Char; max 2 characters	Direction of money movement for the fee: `CR` (credit) or `DR` (debit)
13	`fee_amount`	Number; blanks allowed; max 26 characters	The fees that are associated with the settlement. This amount includes all transactional fees. Fees are never amortized across multiple transactions. Handling fees and other non-transactional fees are reported as gross amounts with no corresponding entry in this field. For more information, see T-codes.
14	`fee_currency`	Char; blanks allowed; max 3 characters	Currency of the fees
15	`transactional_status`	Alphanumeric; max 1 character	A 1-character code that indicates the transaction status: `S` (successfully completed), `D` (denied), `P` (pending), `V` (reversed), or `F` (partially refunded). A status of `V` (reversed) is returned if the transaction is completely refunded.
16	`insurance_amount`	Money; blanks allowed; max 25 characters	The insurance amount that PayPal or the merchant reported for the transaction
17	`sales_tax_amount`	Money; blanks allowed; max 25 characters	The sales tax amount that PayPal or the merchant reported for the transaction
18	`shipping_amount`	Money; blanks allowed; max 25 characters	The shipping amount that PayPal or the merchant reported for the transaction
19	`transaction_subject`	Alphanumeric; blanks allowed; max 256 characters	Subject of payment as passed through by the payer to the payee. This is a pass-through of data that the payer controls. PayPal does not recommend using this field for special purposes.
20	`transaction_note`	Varchar; blanks allowed; max 4000 characters	Special note of payment as passed through by the payer to the payee (the memo or note variable). This is a pass-through of data that the payer controls, and it may contain special customer requests, such as shipping instructions.
21	`payers_account_id`	Alphanumeric; blanks allowed; max 127 characters	The email address of the payer. If there is no payer, this field is blank.
22	`payer_address_status`	Char; blanks allowed; max 1 character	Whether the counterparty's shipping address is confirmed: `Y` or `N`
23	`item_name`	Alphanumeric; blanks allowed; max 127 characters	The item name that the buyer specified in the auction or item title field, or the seller specified in button creation fields (`item_name` or `item_name_x`) for PayPal Shopping Cart, Buy Now, Donations, or Subscriptions
24	`item_id`	Alphanumeric; blanks allowed; max 127 characters	The item ID that the buyer specified in the auction or item title field, or the seller specified in button creation fields (`item_number` or `item_number_x`) for PayPal Shopping Cart, Buy Now, Donations, or Subscriptions
25	`option_1_name`	Alphanumeric; blanks allowed; max 64 characters	The name of Option 1 as the seller specified in button creation fields (`on0` or `on0_x`) for PayPal Shopping Cart, Buy Now, or Subscription Option 1 Name
26	`option_1_value`	Alphanumeric; blanks allowed; max 200 characters	The value of Option 1 as entered by the buyer or specified by the seller for PayPal Shopping Cart, Buy Now, or Subscription Option 1 Value
27	`option_2_name`	Alphanumeric; blanks allowed; max 64 characters	The name of Option 2 as the seller specified in button creation fields for PayPal Shopping Cart, Buy Now, or Subscription Option 2 Name
28	`option_2_value`	Alphanumeric; blanks allowed; max 200 characters	The value of Option 2 as entered by the buyer or specified by the seller for PayPal Shopping Cart, Buy Now, or Subscription Option 2 Value
29	`auction_site`	Varchar; blanks allowed; max 255 characters	Name of the auction site: `eBay`, `Yahoo! Auctions`, `uBid.com`, `Amazon.com Auctions`, `MSN Auctions`, `BidVille`, or `Other`
30	`auction_buyer_id`	Varchar; blanks allowed; max 255 characters	The ID of the buyer who is making the purchase in the auction. This ID can differ from the payer ID that is provided for the payment.
31	`auction_closing_date`	Alphanumeric; blanks allowed; max 100 characters	(For eBay auction items only.) Closing date of the eBay auction item.
32	`shipping_address_line_1`	Varchar; blanks allowed; max 300 characters	Line 1 of the street address for the shipping address that the payer specified. This is a pass-through of what the payer provided. International addresses may contain non-street information in this field.
33	`shipping_address_line_2`	Varchar; blanks allowed; max 300 characters	Line 2 of the street address for the shipping address that the payer specified. This is a pass-through of what the payer provided. International addresses may contain non-street information in this field.
34	`shipping_address_city`	Alphanumeric; blanks allowed; max 120 characters	City of the shipping address that the payer specified. This is a pass-through of what the payer provided. International addresses may contain non-city information in this field.
35	`shipping_address_state`	Alphanumeric; blanks allowed; max 120 characters	State, province, or territory for the shipping address that the payer specified. International addresses may contain non-state information in this field, such as a prefecture name, or this field can be blank if no state equivalent exists.
36	`shipping_address_zip`	Varchar; blanks allowed; max 60 characters	Postal code for the shipping address that the payer specified
37	`shipping_address_country`	Varchar; blanks allowed; max 64 characters	Country for the shipping address that the payer specified
38	`shipping_method`	Varchar; blanks allowed; max 10 characters	Shipping method that is associated with this order
39	`custom_field`	Varchar; blanks allowed; max 256 characters	(Reserved for merchant use.) Custom text that the merchant sets for the transaction. Unlike the invoice ID, the custom field has no uniqueness restrictions and is not searchable with PayPal search tools. In the Transaction Detail report, this field can include the unique ID of payments that are made with Mass Payment.
40	`billing_address_line_1`	Varchar; blanks allowed; max 300 characters	Line 1 of the street address for the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
41	`billing_address_line_2`	Varchar; blanks allowed; max 300 characters	Line 2 of the street address for the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
42	`billing_address_city`	Alphanumeric; blanks allowed; max 120 characters	City of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
43	`billing_address_state`	Alphanumeric; blanks allowed; max 120 characters	State, province, or territory of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
44	`billing_address_zip`	Varchar; blanks allowed; max 60 characters	Postal code of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
45	`billing_address_country`	Varchar; blanks allowed; max 64 characters	Country of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
46	`consumer_id`	Varchar; max 127 characters	The consumer's PayPal account number, as an encrypted hash
47	`first_name`	Varchar; blanks allowed; max 127 characters	Consumer's first name as recorded in their PayPal account
48	`last_name`	Varchar; blanks allowed; max 127 characters	Consumer's last name as recorded in their PayPal account
49	`consumer_business_name`	Varchar; blanks allowed; max 127 characters	Consumer's business name as recorded in their PayPal account. Included in the report as applicable.
50	`card_type`	Varchar; blanks allowed; max 30 characters	Card used in the transaction: `VISA`, `MASTERCARD`, `AMEX`, `BANKCARD`, `DISCOVER`, `DINERS`, `SWITCH`, `SOLO`, `GE`, `CARTES_BANCIARES`, `JCB`, or `UNKNOWN`
51	`payment_source`	Varchar; blanks allowed; max 50 characters	The payer's payment source: `PayPal`, `Direct Credit Card`, `Express Checkout`, `Virtual Terminal`, `eCheck`, `Credit Card`, `Electronic Funds Transfer`, `Debit Card`, `Venmo`, `Apple Pay`, `Google Pay`, `Network Token`, `Pay Upon Invoice`, or a supported APM
52	`shipping_name`	Varchar; blanks allowed; max 130 characters	The name of the person to whom the item was shipped
53	`authorization_review_status`	Varchar; blanks allowed; max 2 characters	The current review status of the transaction: `01` (Green), `02` (Yellow), or blank if the transaction is not under review
54	`protection_eligibility`	Varchar; blanks allowed; max 2 characters	Whether the transaction is eligible for protection: `01` (eligible), `02` (not eligible), or `03` (partially eligible)
55	`payment_tracking_id`	Varchar; blanks allowed; max 127 characters	Unique ID that partners use to obtain information about a payment or to request a refund
56	`store_id`	Varchar; blanks allowed; max 50 characters	(Applicable to Point of Sale transactions only.) ID of the store where the transaction occurred
57	`terminal_id`	Varchar; blanks allowed; max 50 characters	(Applicable to Point of Sale transactions only.) ID of the terminal where the transaction occurred
58	`coupons`	Varchar; max 2048 characters	(Applicable to Point of Sale transactions only.) Information about all coupons that are associated with the transaction. Contains pipe-delimited data for each coupon in this format `incentive_code\|amount\|currency\|campaign_id`. For example, a USD $20 coupon with code `1234` and campaign ID `ABCD` is represented as `1234\|2000\|USD\|ABCD`.
59	`special_offers`	Varchar; max 2048 characters	(Applicable to Point of Sale transactions only.) Information about all store credits associated with the transaction. Contains pipe-delimited data for each store credit in the format `incentive_code\|amount\|currency\|campaign_id`. For example, a USD $20 store offer with code `1234` and campaign ID `ABCD` is represented as `1234\|2000\|USD\|ABCD`.
60	`loyalty_card_number`	Varchar; blanks allowed; max 100 characters	(Applicable to Point of Sale transactions only.) Customer's loyalty card number that was provided to the merchant
61	`checkout_type`	String; blanks allowed; max 1 character	Type of transaction: `F` (Forced Post) or `S` (Single Call Checkout)
62	`secondary_shipping_address_line_1`	Varchar; blanks allowed; max 300 characters	Line 1 of the street address for the secondary shipping address that the payer specified. International addresses may contain non-street information in this field.
63	`secondary_shipping_address_line_2`	Varchar; blanks allowed; max 300 characters	Line 2 of the street address for the secondary shipping address that the payer specified. International addresses may contain non-street information in this field.
64	`secondary_shipping_address_city`	Alphanumeric; blanks allowed; max 120 characters	City for the secondary shipping address that the payer specified. International addresses may contain non-city information in this field.
65	`secondary_shipping_address_state`	Varchar; blanks allowed; max 120 characters	State, province, or territory for the secondary shipping address that the payer specified. International addresses may contain non-state information in this field.
66	`secondary_shipping_address_country`	Varchar; blanks allowed; max 64 characters	Country for the secondary shipping address that the payer specified
67	`secondary_shipping_address_zip`	Varchar; blanks allowed; max 32 characters	Postal code for the secondary shipping address that the payer specified
68	`3pl_reference_id`	String; blanks allowed; max 32 characters	Reference ID of the third-party logistics partner
69	`gift_card_id`	String; blanks allowed	Deprecated. Previously represented the gift card that the consumer used as a funding instrument for the transaction

Additional fields

The following fields require report customization. To request these fields, contact your PayPal account manager or customer support.

Position, Field name, Data characteristics, Description
Position	Field name	Data characteristics	Description
1	`original_invoice_id`	Varchar; blanks allowed; max 200 characters	The invoice ID of the original payment record. This value helps you track all related transactions through their parent transaction.
2	`buyer_wallet`	Varchar; blanks allowed; max 10 characters	Identifies the company (PayPal or one of its subsidiaries) that processes the payment
3	`item_details`	Varchar; blanks allowed; max 1024 characters	The item details for the transaction
4	`comment_1`	Varchar; blanks allowed; max 1000 characters	A note that accompanies a transaction
5	`comment_2`	Varchar; blanks allowed; max 10 characters	A note that accompanies a transaction
6	`invoice_number`	Varchar; blanks allowed; max 200 characters	The identifier of the invoice that the merchant issued
7	`po_number`	Varchar; blanks allowed; max 200 characters	The identifier of the purchase order (manifest of goods bought from the merchant)
8	`customer_reference_number`	Varchar; blanks allowed; max 80 characters	The merchant's identifier for the customer
9	`payflow_transaction_id_pnref`	Varchar; blanks allowed; max 80 characters	The unique identifier for the gateway transaction (PNREF)
10	`transaction_buyer_country_code`	Varchar; blanks allowed; max 45 characters	The buyer's country code
11	`receipt_id`	Varchar; blanks allowed; max 19 characters	The receipt identification number in this format `xxxx-xxxx-xxxx-xxxx`
12	`tax_id`	Varchar; blanks allowed; max 80 characters	(Available for Brazil only.) The buyer's taxpayer registry number
13	`contact_phone_number`	Numeric; blanks allowed; max 22 characters	The contact phone number for the transaction
14	`country_code`	Varchar; blanks allowed; max 64 characters	The 2-letter country code of the shipping address
15	`payment_source_subtype`	String; blanks allowed	The payer's payment source subtype: `VISA`, `MASTERCARD`, `AMEX`, `BANKCARD`, `DISCOVER`, `DINERS`, `SWITCH`, `SOLO`, `CARTES_BANCIARES`, `GE`, `JCB`, `CB_NATIONALE`, Pay Later offer types, or `Installment`. For wallets and network tokens, this field shows the card type and card brand, for example `Credit Card-VISA` or `Debit Card-MASTERCARD`.
16	`decline_code`	String; blanks allowed	UDD SEPA decline code.
17	`fastlane_checkout_transaction`	Varchar	Indicates whether the transaction was checked out using Fastlane accelerated checkout

Section footer data

The section footer contains a row count for the current section. You can use this with the section record count to verify completeness.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (section footer, `SF`)
2	`row_count`	Number	Total number of section body records in this section

Section record count data

The section record count provides a second row count that is scoped to the current section. You can use this for reconciliation.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (section record count, `SC`)
2	`row_count`	Number	Total number of section body data rows in this section. You can use this for reconciliation.

Reference IDs

Some transaction types derive from or relate to an existing transaction or event. PayPal assigns a unique reference ID to identify the originating transaction or event for related transactions.

Reference IDs follow a one-to-many relationship: a single reference transaction can have multiple referring transactions, but each referring transaction has only one reference transaction. Reference transactions are limited to events that move money or are related to future money movement, such as orders, authorizations, subscriptions, and preapproved payments.

The following table maps transaction types to their reference ID source.

Transaction type, Reference ID
Transaction type	Reference ID
Settlement on authorization	Original authorization
Full refund	Originating settlement
Partial refund	Originating settlement
Settlement on reauthorization	Originating settlement
Completed chargeback (merchant loss)	Disputed sale or settlement
Completed buyer complaint (merchant loss)	Disputed sale or settlement
Settlement adjustment	Settlement or sale transaction
Reimbursement	Settlement or sale transaction
Reversal	Original settlement
Account correction	Original transaction against which the correction was made

For a list of supported ISO 4217 currency codes, see PayPal-supported currencies.
For a list of transaction event codes, see T-codes.
For help accessing the SFTP reports, see Access SFTP reports.

The following specifications apply to this report:

This report uses UTF-8 character encoding (8-bit UCS/Unicode Transformation Format).
PayPal generates this report on a daily (24-hour) basis, and it is available by 12:00 PM daily in the leading time zone of the reporting window. SFTP reports are in the /ppreports/outgoing directory.
This report is available in the Secure Dropbox for 45 days after delivery.
The report is available in CSV (comma-separated values) or TAB (tab-delimited) format. To set your data format, contact your PayPal account manager or customer support.
This report includes alternative payment methods (APMs). For more information about APMs, see the list of supported APMs.
All fields of type varchar are surrounded with double quotation marks, regardless of the field delimiter. Double quotation marks inside a field are represented as two double quotation marks in succession.
Fields that can contain spaces are indicated in the field descriptions in the following tables. All other fields must not contain spaces. For example, the transaction_id field cannot contain spaces, while the transaction_note field can contain spaces.

Prerequisites

Before you use the Transaction Detail report, ensure that you meet the following requirements:

You must be an approved merchant to use this report. To request access, contact your PayPal account manager or customer support.
You must have an SFTP account to access the report on the SFTP server. For more information about accessing SFTP reports, see Access SFTP reports.

New or revised versions

Notifications

PayPal monitors the generation and delivery of this report at all times and maintains 2 contact points for notifications:

A business contact for all notifications that relate to data integrity, data delivery, and new reporting features
A technical contact for all notifications that relate to data integrity, data delivery, system outages, system updates, and new features

PayPal notifies you of the following types of events:

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

Report file name

The file naming convention depends on whether you are using Multiple Account Management (MAM).

Single account report

For a single account, the file name follows this convention:

TRR-yyyymmdd.sequenceNumber.version.format

Field, Description
Field	Description
`TRR`	Abbreviation for "Transaction Detail report"
`yyyymmdd`	The date of the data in the report. This date stamp represents the latest, or ending, date of the data.
`sequenceNumber`	The sequence number of the file. 2 characters, right-justified, and zero-filled. Begins with `01` and increments until all parts are recorded. Always present, even if there is only 1 file.
`version`	The version of the report. 3 characters, right-justified, and zero-filled.
`format`	The report format: `CSV` (comma-separated values) or `TAB` (tab-delimited)

Multiple account report

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

TRR-yyyymmdd.reportingWindow.sequenceNumber.totalFiles.version.format

Field, Description
Field	Description
`TRR`	Abbreviation for "Transaction Detail Report"
`yyyymmdd`	The date of the data in the report. This date stamp represents the latest, or ending, date of the report data.
`reportingWindow`	The window of time when the report was generated: `A` (America/New York to America/Los Angeles), `H` (America/Los Angeles to Asia/Hong Kong), `R` (Asia/Hong Kong to Europe/London), or `X` (Europe/London to America/New York)
`sequenceNumber`	The sequence number of the file. 2 characters, right-justified, and zero-filled. Begins with `01` and increments until all parts are recorded. Always present, even if there is only 1 file.
`totalFiles`	The total number of files for this date. Always 2 digits and zero-padded. For example, `02` for 2 total files.
`version`	The version of the report. 3 characters, right-justified, and zero-filled.
`format`	The report format: `CSV` (comma-separated values) or `TAB` (tab-delimited)

Report file structure

Each row consists of a two-letter row type code that is followed by the details for that row type.

The FH, SC, RC, and RF rows are not available in Transaction Detail report version 001.

Row types

The following table lists the valid row type codes for this report. Each code identifies the type of data in that row.

Code, Description, Section
Code	Description	Section
`RH`	Report header	Report header data
`FH`	File header	File header data
`SH`	Section header	Section header data
`CH`	Column header	Section body data
`SB`	Row data	Section body data
`SF`	Section footer	Section footer data
`SC`	Section record count	Section record count data
`RF`	Report footer	Report footer data
`RC`	Report record count	Report record count data
`FF`	File footer	File footer data

Single file report structure

When the report contains fewer than 1 million records, it is a single file with 1 section, organized as follows.

RH  Report header
FH  File header
SH  Section header
CH  Column header
SB  Row data
... (additional row data)
SF  Section footer
SC  Section record count
RF  Report footer
RC  Report record count
FF  File footer

Multi-file report structure

File 1, File 2
File 1	File 2
`RH` Report header	`FH` File header
`FH` File header	`SB` Row data
`SH` Section header	...
`CH` Column header	`SB` Row data
`SB` Row data	`SF` Section footer
...	`SC` Section record count
`SB` Row data	`RF` Report footer
`SF` Section footer	`RC` Report record count
`SC` Section record count	`FF` File footer
`SH` Section header
`CH` Column header
`SB` Row data
...
`FF` File footer

Report data

Report header data

The report header identifies the report and the account that received it. It appears once at the beginning of the first file. All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (report header, `RH`)
2	`report_generation_date`	Date/time	The date and time the report file was generated, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
3	`reporting_window`	Varchar	The window of time when the report was generated: `A` (America/New York to America/Los Angeles), `H` (America/Los Angeles to Asia/Hong Kong), `R` (Asia/Hong Kong to Europe/London), or `X` (Europe/London to America/New York)
4	`account_id`	Varchar	The account number that receives the report (Payer ID is the encrypted hash of the PayPal account.)
5	`report_version`	Varchar	The version of the report

The report footer contains a total row count for the report. You can use it to verify that you received all records.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (report footer, `RF`)
2	`row_count`	Number	The number of body data rows in the report. You can use this for reconciliation. The report may span multiple files.

Report record count data

The report record count provides a second total row count for the entire report, also used for reconciliation. All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (report record count, `RC`)
2	`row_count`	Number	The number of body data rows in the report. You can use this for reconciliation. The report may span multiple files.

File data

This section describes the data in the file header and file footer rows. Each file in the report has a file header and file footer, even if the report contains only 1 file.

File header data

The file header identifies the sequence number of each file in the report. It appears at the beginning of every file. All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (file header, `FH`)
2	`file_count`	Number	The sequence number of the file in the report. You can use this for reconciliation.

File footer data

The file footer contains a row count for the individual file. You can use this to verify that you received all records in that file.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (file footer, `FF`)
2	`row_count`	Number	The number of body data rows in the file. You can use this for reconciliation.

Section data

This section describes the data in the section header, section footer, and section record count rows. If you are not using Multiple Account Management, the report contains only 1 section.

Section header data

The section header identifies the reporting period and account for the section. It appears once for each section.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (section header, `SH`)
2	`reporting_period_start_date`	Date/time	The beginning of the reporting period, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
3	`reporting_period_end_date`	Date/time	The end of the reporting period, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
4	`account_id`	Varchar	Account number that PayPal generated
5	`partner_account_id`	Varchar; blanks allowed; max 127 characters	The partner's account ID for the merchant. This is the value that the partner passes in the `<PartnerMerchantExternalID>` tag of the Multiple Account Management batch input file.

Section body data

For transactions with associated disputes, claimant information appears only in the dispute report, not in the settlement report or transaction detail report.

Position, Field name, Data characteristics, Description
Position	Field name	Data characteristics	Description
1	`column_type`	Literal	The column type (section body, `SB`)
2	`transaction_id`	Varchar; blanks allowed; max 24 characters	Transaction ID of the money movement event. PayPal generates this ID, and a merchant cannot alter it.
3	`invoice_id`	Text; blanks allowed; max 127 characters	Invoice ID that the merchant sets for the transaction. If the merchant sent an invoice ID with the capture request, that value is reported here. Otherwise, the value of the invoice ID (if any) from the authorizing transaction is reported here.
4	`paypal_reference_id`	Varchar; blanks allowed; max 24 characters	A PayPal reference ID that identifies a related, existing transaction or event from which this event originated. For more information about reference events, see Reference IDs.
5	`paypal_reference_id_type`	Text; blanks allowed; max 3 characters	The type of the PayPal reference ID: `ODR` (order ID), `TXN` (transaction ID), `SUB` (subscription ID), or `PAP` (preapproved payment ID)
6	`transaction_event_code`	Alphanumeric; max 5 characters	Transaction event type (T-code). For a complete list of transaction event codes, see T-codes.
7	`transaction_initiation_date`	Date/time; blanks allowed; max 25 characters	Date and time when the transaction was initiated, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
8	`transaction_completion_date`	Date/time; blanks allowed; max 25 characters	Date and time the transaction was completed, in this format `YYYY/MM/DD HH:MM:SS offset`. `offset` is a 5-character signed offset from GMT, for example `+0800`.
9	`transaction_debit_or_credit`	Literal; max 2 characters	Direction of money movement for the gross amount: `CR` (credit) or `DR` (debit)
10	`gross_transaction_amount`	Money; max 26 characters	The payment amount before fees. This field contains the gross transaction value for all transactions. Handling fees and other non-transactional fees are reported as gross amounts with no corresponding fee column entry. For more information, see T-codes.
11	`gross_transaction_currency`	3-character currency code; max 3 characters	Currency of the transaction
12	`fee_debit_or_credit`	Char; max 2 characters	Direction of money movement for the fee: `CR` (credit) or `DR` (debit)
13	`fee_amount`	Number; blanks allowed; max 26 characters	The fees that are associated with the settlement. This amount includes all transactional fees. Fees are never amortized across multiple transactions. Handling fees and other non-transactional fees are reported as gross amounts with no corresponding entry in this field. For more information, see T-codes.
14	`fee_currency`	Char; blanks allowed; max 3 characters	Currency of the fees
15	`transactional_status`	Alphanumeric; max 1 character	A 1-character code that indicates the transaction status: `S` (successfully completed), `D` (denied), `P` (pending), `V` (reversed), or `F` (partially refunded). A status of `V` (reversed) is returned if the transaction is completely refunded.
16	`insurance_amount`	Money; blanks allowed; max 25 characters	The insurance amount that PayPal or the merchant reported for the transaction
17	`sales_tax_amount`	Money; blanks allowed; max 25 characters	The sales tax amount that PayPal or the merchant reported for the transaction
18	`shipping_amount`	Money; blanks allowed; max 25 characters	The shipping amount that PayPal or the merchant reported for the transaction
19	`transaction_subject`	Alphanumeric; blanks allowed; max 256 characters	Subject of payment as passed through by the payer to the payee. This is a pass-through of data that the payer controls. PayPal does not recommend using this field for special purposes.
20	`transaction_note`	Varchar; blanks allowed; max 4000 characters	Special note of payment as passed through by the payer to the payee (the memo or note variable). This is a pass-through of data that the payer controls, and it may contain special customer requests, such as shipping instructions.
21	`payers_account_id`	Alphanumeric; blanks allowed; max 127 characters	The email address of the payer. If there is no payer, this field is blank.
22	`payer_address_status`	Char; blanks allowed; max 1 character	Whether the counterparty's shipping address is confirmed: `Y` or `N`
23	`item_name`	Alphanumeric; blanks allowed; max 127 characters	The item name that the buyer specified in the auction or item title field, or the seller specified in button creation fields (`item_name` or `item_name_x`) for PayPal Shopping Cart, Buy Now, Donations, or Subscriptions
24	`item_id`	Alphanumeric; blanks allowed; max 127 characters	The item ID that the buyer specified in the auction or item title field, or the seller specified in button creation fields (`item_number` or `item_number_x`) for PayPal Shopping Cart, Buy Now, Donations, or Subscriptions
25	`option_1_name`	Alphanumeric; blanks allowed; max 64 characters	The name of Option 1 as the seller specified in button creation fields (`on0` or `on0_x`) for PayPal Shopping Cart, Buy Now, or Subscription Option 1 Name
26	`option_1_value`	Alphanumeric; blanks allowed; max 200 characters	The value of Option 1 as entered by the buyer or specified by the seller for PayPal Shopping Cart, Buy Now, or Subscription Option 1 Value
27	`option_2_name`	Alphanumeric; blanks allowed; max 64 characters	The name of Option 2 as the seller specified in button creation fields for PayPal Shopping Cart, Buy Now, or Subscription Option 2 Name
28	`option_2_value`	Alphanumeric; blanks allowed; max 200 characters	The value of Option 2 as entered by the buyer or specified by the seller for PayPal Shopping Cart, Buy Now, or Subscription Option 2 Value
29	`auction_site`	Varchar; blanks allowed; max 255 characters	Name of the auction site: `eBay`, `Yahoo! Auctions`, `uBid.com`, `Amazon.com Auctions`, `MSN Auctions`, `BidVille`, or `Other`
30	`auction_buyer_id`	Varchar; blanks allowed; max 255 characters	The ID of the buyer who is making the purchase in the auction. This ID can differ from the payer ID that is provided for the payment.
31	`auction_closing_date`	Alphanumeric; blanks allowed; max 100 characters	(For eBay auction items only.) Closing date of the eBay auction item.
32	`shipping_address_line_1`	Varchar; blanks allowed; max 300 characters	Line 1 of the street address for the shipping address that the payer specified. This is a pass-through of what the payer provided. International addresses may contain non-street information in this field.
33	`shipping_address_line_2`	Varchar; blanks allowed; max 300 characters	Line 2 of the street address for the shipping address that the payer specified. This is a pass-through of what the payer provided. International addresses may contain non-street information in this field.
34	`shipping_address_city`	Alphanumeric; blanks allowed; max 120 characters	City of the shipping address that the payer specified. This is a pass-through of what the payer provided. International addresses may contain non-city information in this field.
35	`shipping_address_state`	Alphanumeric; blanks allowed; max 120 characters	State, province, or territory for the shipping address that the payer specified. International addresses may contain non-state information in this field, such as a prefecture name, or this field can be blank if no state equivalent exists.
36	`shipping_address_zip`	Varchar; blanks allowed; max 60 characters	Postal code for the shipping address that the payer specified
37	`shipping_address_country`	Varchar; blanks allowed; max 64 characters	Country for the shipping address that the payer specified
38	`shipping_method`	Varchar; blanks allowed; max 10 characters	Shipping method that is associated with this order
39	`custom_field`	Varchar; blanks allowed; max 256 characters	(Reserved for merchant use.) Custom text that the merchant sets for the transaction. Unlike the invoice ID, the custom field has no uniqueness restrictions and is not searchable with PayPal search tools. In the Transaction Detail report, this field can include the unique ID of payments that are made with Mass Payment.
40	`billing_address_line_1`	Varchar; blanks allowed; max 300 characters	Line 1 of the street address for the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
41	`billing_address_line_2`	Varchar; blanks allowed; max 300 characters	Line 2 of the street address for the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
42	`billing_address_city`	Alphanumeric; blanks allowed; max 120 characters	City of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
43	`billing_address_state`	Alphanumeric; blanks allowed; max 120 characters	State, province, or territory of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
44	`billing_address_zip`	Varchar; blanks allowed; max 60 characters	Postal code of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
45	`billing_address_country`	Varchar; blanks allowed; max 64 characters	Country of the payer's billing address. Provided only if the merchant is authorized to receive the billing address and has set the `REQBILLINGADDRESS` field in `SetExpressCheckout` or `SetBillingAddressCustomer`. Otherwise, this field is blank.
46	`consumer_id`	Varchar; max 127 characters	The consumer's PayPal account number, as an encrypted hash
47	`first_name`	Varchar; blanks allowed; max 127 characters	Consumer's first name as recorded in their PayPal account
48	`last_name`	Varchar; blanks allowed; max 127 characters	Consumer's last name as recorded in their PayPal account
49	`consumer_business_name`	Varchar; blanks allowed; max 127 characters	Consumer's business name as recorded in their PayPal account. Included in the report as applicable.
50	`card_type`	Varchar; blanks allowed; max 30 characters	Card used in the transaction: `VISA`, `MASTERCARD`, `AMEX`, `BANKCARD`, `DISCOVER`, `DINERS`, `SWITCH`, `SOLO`, `GE`, `CARTES_BANCIARES`, `JCB`, or `UNKNOWN`
51	`payment_source`	Varchar; blanks allowed; max 50 characters	The payer's payment source: `PayPal`, `Direct Credit Card`, `Express Checkout`, `Virtual Terminal`, `eCheck`, `Credit Card`, `Electronic Funds Transfer`, `Debit Card`, `Venmo`, `Apple Pay`, `Google Pay`, `Network Token`, `Pay Upon Invoice`, or a supported APM
52	`shipping_name`	Varchar; blanks allowed; max 130 characters	The name of the person to whom the item was shipped
53	`authorization_review_status`	Varchar; blanks allowed; max 2 characters	The current review status of the transaction: `01` (Green), `02` (Yellow), or blank if the transaction is not under review
54	`protection_eligibility`	Varchar; blanks allowed; max 2 characters	Whether the transaction is eligible for protection: `01` (eligible), `02` (not eligible), or `03` (partially eligible)
55	`payment_tracking_id`	Varchar; blanks allowed; max 127 characters	Unique ID that partners use to obtain information about a payment or to request a refund
56	`store_id`	Varchar; blanks allowed; max 50 characters	(Applicable to Point of Sale transactions only.) ID of the store where the transaction occurred
57	`terminal_id`	Varchar; blanks allowed; max 50 characters	(Applicable to Point of Sale transactions only.) ID of the terminal where the transaction occurred
58	`coupons`	Varchar; max 2048 characters	(Applicable to Point of Sale transactions only.) Information about all coupons that are associated with the transaction. Contains pipe-delimited data for each coupon in this format `incentive_code\|amount\|currency\|campaign_id`. For example, a USD $20 coupon with code `1234` and campaign ID `ABCD` is represented as `1234\|2000\|USD\|ABCD`.
59	`special_offers`	Varchar; max 2048 characters	(Applicable to Point of Sale transactions only.) Information about all store credits associated with the transaction. Contains pipe-delimited data for each store credit in the format `incentive_code\|amount\|currency\|campaign_id`. For example, a USD $20 store offer with code `1234` and campaign ID `ABCD` is represented as `1234\|2000\|USD\|ABCD`.
60	`loyalty_card_number`	Varchar; blanks allowed; max 100 characters	(Applicable to Point of Sale transactions only.) Customer's loyalty card number that was provided to the merchant
61	`checkout_type`	String; blanks allowed; max 1 character	Type of transaction: `F` (Forced Post) or `S` (Single Call Checkout)
62	`secondary_shipping_address_line_1`	Varchar; blanks allowed; max 300 characters	Line 1 of the street address for the secondary shipping address that the payer specified. International addresses may contain non-street information in this field.
63	`secondary_shipping_address_line_2`	Varchar; blanks allowed; max 300 characters	Line 2 of the street address for the secondary shipping address that the payer specified. International addresses may contain non-street information in this field.
64	`secondary_shipping_address_city`	Alphanumeric; blanks allowed; max 120 characters	City for the secondary shipping address that the payer specified. International addresses may contain non-city information in this field.
65	`secondary_shipping_address_state`	Varchar; blanks allowed; max 120 characters	State, province, or territory for the secondary shipping address that the payer specified. International addresses may contain non-state information in this field.
66	`secondary_shipping_address_country`	Varchar; blanks allowed; max 64 characters	Country for the secondary shipping address that the payer specified
67	`secondary_shipping_address_zip`	Varchar; blanks allowed; max 32 characters	Postal code for the secondary shipping address that the payer specified
68	`3pl_reference_id`	String; blanks allowed; max 32 characters	Reference ID of the third-party logistics partner
69	`gift_card_id`	String; blanks allowed	Deprecated. Previously represented the gift card that the consumer used as a funding instrument for the transaction

Additional fields

The following fields require report customization. To request these fields, contact your PayPal account manager or customer support.

Position, Field name, Data characteristics, Description
Position	Field name	Data characteristics	Description
1	`original_invoice_id`	Varchar; blanks allowed; max 200 characters	The invoice ID of the original payment record. This value helps you track all related transactions through their parent transaction.
2	`buyer_wallet`	Varchar; blanks allowed; max 10 characters	Identifies the company (PayPal or one of its subsidiaries) that processes the payment
3	`item_details`	Varchar; blanks allowed; max 1024 characters	The item details for the transaction
4	`comment_1`	Varchar; blanks allowed; max 1000 characters	A note that accompanies a transaction
5	`comment_2`	Varchar; blanks allowed; max 10 characters	A note that accompanies a transaction
6	`invoice_number`	Varchar; blanks allowed; max 200 characters	The identifier of the invoice that the merchant issued
7	`po_number`	Varchar; blanks allowed; max 200 characters	The identifier of the purchase order (manifest of goods bought from the merchant)
8	`customer_reference_number`	Varchar; blanks allowed; max 80 characters	The merchant's identifier for the customer
9	`payflow_transaction_id_pnref`	Varchar; blanks allowed; max 80 characters	The unique identifier for the gateway transaction (PNREF)
10	`transaction_buyer_country_code`	Varchar; blanks allowed; max 45 characters	The buyer's country code
11	`receipt_id`	Varchar; blanks allowed; max 19 characters	The receipt identification number in this format `xxxx-xxxx-xxxx-xxxx`
12	`tax_id`	Varchar; blanks allowed; max 80 characters	(Available for Brazil only.) The buyer's taxpayer registry number
13	`contact_phone_number`	Numeric; blanks allowed; max 22 characters	The contact phone number for the transaction
14	`country_code`	Varchar; blanks allowed; max 64 characters	The 2-letter country code of the shipping address
15	`payment_source_subtype`	String; blanks allowed	The payer's payment source subtype: `VISA`, `MASTERCARD`, `AMEX`, `BANKCARD`, `DISCOVER`, `DINERS`, `SWITCH`, `SOLO`, `CARTES_BANCIARES`, `GE`, `JCB`, `CB_NATIONALE`, Pay Later offer types, or `Installment`. For wallets and network tokens, this field shows the card type and card brand, for example `Credit Card-VISA` or `Debit Card-MASTERCARD`.
16	`decline_code`	String; blanks allowed	UDD SEPA decline code.
17	`fastlane_checkout_transaction`	Varchar	Indicates whether the transaction was checked out using Fastlane accelerated checkout

Section footer data

The section footer contains a row count for the current section. You can use this with the section record count to verify completeness.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (section footer, `SF`)
2	`row_count`	Number	Total number of section body records in this section

Section record count data

The section record count provides a second row count that is scoped to the current section. You can use this for reconciliation.

All fields are non-blank unless otherwise noted.

Position, Column name, Data type, Description
Position	Column name	Data type	Description
1	`column_type`	Literal	The column type (section record count, `SC`)
2	`row_count`	Number	Total number of section body data rows in this section. You can use this for reconciliation.

Reference IDs

Some transaction types derive from or relate to an existing transaction or event. PayPal assigns a unique reference ID to identify the originating transaction or event for related transactions.

The following table maps transaction types to their reference ID source.

Transaction type, Reference ID
Transaction type	Reference ID
Settlement on authorization	Original authorization
Full refund	Originating settlement
Partial refund	Originating settlement
Settlement on reauthorization	Originating settlement
Completed chargeback (merchant loss)	Disputed sale or settlement
Completed buyer complaint (merchant loss)	Disputed sale or settlement
Settlement adjustment	Settlement or sale transaction
Reimbursement	Settlement or sale transaction
Reversal	Original settlement
Account correction	Original transaction against which the correction was made

For a list of supported ISO 4217 currency codes, see PayPal-supported currencies.
For a list of transaction event codes, see T-codes.
For help accessing the SFTP reports, see Access SFTP reports.

Transaction Detail report

Report specification for the Transaction Detail SFTP report, including file naming, structure, and field definitions.

On this page

On this page

On this page

We currently use cookies to improve and customize your experience on our site. If you accept, we’ll also use marketing cookies to show you personalized ads. Manage your cookies and learn more.

Transaction Detail report

Report specification for the Transaction Detail SFTP report, including file naming, structure, and field definitions.

On this page

On this page