Submission Report Specification (Open Wallet API)

DOCS

Last updated: Aug 15th, 7:23am

This report contains all relevant transactions between 12:00 AM to 11:59 PM PST of the day after the transaction. Each submission file has transactions for a given financial instrument. Transactions across instruments are not mixed in a single file.

File specifications

The following specifications apply to the submission report file:

Record length2000 byte fixed length.
File formatUTF-8 encoded.
Transmission day and timeThe day of the transaction before 2 AM PST.
File directionIn general, transmitted from PayPal to partner.

Field specifications

The following specifications apply to the Submission report fields:

Submission file header

The full file contains only one file header.

PositionFieldTypeLength;
Start and end positions
ValueRequired?Description
1RECORD_TYPEAlphanumeric, uppercase7
1 and 7
SFHR001YesCorresponds to the record type and must be the first item in the record. The SFHR001 constant indicates a file header record.
2RECORD_NUMBERNumeric, right justified, zero filled (if no value)8
8 and 15
00000001YesContains a record sequence number to monitor the integrity and continuity of data in a file. The header record is always set to 00000001. Each subsequent record in the file must be incremented to the RECORD_NUMBER value in the preceding record plus 1.
The number of records per file must not exceed 99999999.
3CLIENT_IDAlphanumeric, uppercase, left justified, character space filled (if no value)11
16 and 26
--YesThe unique PayPal-assigned ID.
4FILE_DIRECTIONAlphanumeric, uppercase, left justified, character space filled (if no value)1
16 and 26
--YesThe unique PayPal-assigned ID.
5FILE_REFERENCE_NUMBERAlphanumeric, uppercase, left justified, character space filled (if no value)12
28 and 39
Unique system-generated file reference number (unique across PayPal)YesContains a submitter-specified file reference number. Can be used to track this file. Value must be unique for each submitted file. A file identification and tracking cross-reference to the corresponding File Validation Report.
6FILE_CREATION_DATENumeric, CCYYMMDD8
40 and 47
The date when the submission file was created (PST)YesCorresponds to the date when the submitter created the file. The format is CCYYMMDD, where:
  • CC. Century.
  • YY. Year
  • MM. Month
  • DD. Day.
For example, enter 20200215 for February 15, 2020.
7FILE_CREATION_TIMENumeric, HHMMSS (24-hour clock)6
48 and 53
The time when the submission file was created (PST)YesCorresponds to the time when the submitter created the file. The format is HHMMSS, where
  • HH Hour (24-hour clock).
  • MM. Minute.
  • SS. Second.
For example, enter 143000 for 2:30 PM.
8FILE_VERSION_NUMBERAlphanumeric8
54 and 61
Version of the fileYesVersion of the file.
9FILLERAlphanumeric1939
62 and 2000
Character spacesYesPayPal internal use only.

Submission batch header

A single file can contain multiple batch headers, which are sorted by product and wallet brand.

PositionFieldTypeLength;
Start and end positions
ValueRequired?Description
1RECORD_TYPEAlphanumeric, uppercase7
1 and 7
SDPR001YesCorresponds to the record type and must be the first item in the record. The SDPR001 constant indicates a detail primary record.
2RECORD_NUMBERNumeric, right justified, zero filled (if no value)8
8 and 15
00000003YesContains a record sequence number to monitor the integrity and continuity of data in a file. The header record is always assigned 00000001. Each subsequent record must be incremented by 1 more than the RECORD_NUMBER entry in the preceding record.
The number of records per file must not exceed 99999999.
3PRODUCT_IDAlphanumeric, uppercase, left justified, character space filled (if no value)11
16 and 26
--YesThe unique PayPal-assigned ID.
4WALLET_BRANDNumeric, right justified, zero filled (if no value)3
27 and 29
  • 001. PayPal.
  • 002. Venmo.
YesWallet associated with the specific attraction
5FILLERAlphanumeric1971
30 and 2000
Character spacesYesPayPal internal use only.

Submission detail primary record

Only one Yes record per transaction.

PositionFieldTypeLength;
Start and end positions
ValueRequired?Description
1RECORD_TYPEAlphanumeric, uppercase7
1 and 7
SDPR001YesCorresponds to the record type and must be the first item in the record. The SDPR001 constant indicates a detail primary record.
2RECORD_NUMBERNumeric, right justified, zero filled (if no value)8
8 and 15
00000003YesContains a record sequence number to monitor the integrity and continuity of data in a file. The header record is always set to 00000003. Each subsequent record must be incremented to the RECORD_NUMBER value in the preceding record plus 1.
The number of records per file must not exceed 99999999.
3REFERENCE_FINANCIAL_INSTRUMENT_IDNumeric15
16 and 30
--YesUniquely identifies the P2P Pass instrument used for the transaction. Equivalent to the FPAN in the card world.
4PAYER IDAlphanumeric19
31 and 49
--YesThe sender's PayPal account number.
5TRANSACTION_TYPEAlphanumeric2
50 and 51
  • 01. Capture.
  • 02. Refund.
  • 03. Withdrawal.
YesType of transaction. Depending on the product and file direction, results in a credit to PayPal or a debit from PayPal.
6TRANSACTION_DATENumeric, CCYYMMDD8
52 and 59
Transaction Date (PST)YesCorresponds to the date when the submitter created the file. The format is CCYYMMDD, where:
  • CC. Century.
  • YY. Year
  • MM. Month
  • DD. Day.
For example, February 15, 2020 would be entered as: 20200215
7TRANSACTION_TIMENumeric, HHMMSS (24-hour clock)6
60 and 65
Transaction Time (PST)YesCorresponds to the time when the submitter created the file. The format is HHMMSS, where:
  • HH Hour (24-hour clock).
  • MM. Minute.
  • SS. Second.
For example, enter 143000 for 2:30 PM.
8ISSUER_ORIGINATION_IDAlphanumeric15
66 and 80
In P2P Pass discussions, this was referred to as the Amex Origination IDConditionalThis ID is unique. This ID is always generated by the issuer for every transaction from the issuer. PayPal includes this ID in the API call it makes to the issuer as part of executing that transaction from the issuer.
9REFERENCE_KEYAlphanumeric20
81 and 100
RRNYesPayPal generates and sends this ID to Amex for every original transaction API call
10REFUND_REFERENCE_KEYAlphanumeric20
101 and 120
Refund/Reversal RRNConditionalPayPal generates and sends this ID to Amex for reverse money movement API calls associated with the original transaction
11APPROVAL_IDAlphanumeric, left-justified, character space filled12
121 and 132
Unique ID received from the client when the authorization and reserve funds request is approved in real timeYesThis field should contain the same value the issuer transmitted in the original authorization response message. This value must be unique. In cases where an approval code is inapplicable, such as credit transactions, fill this field with character space.
12REFUND_APPROVAL_IDAlphanumeric, left-justified, character space filled12
133 and 144
--ConditionalShould contain the same value transmitted from the issuer in the refund/reversal response to reverse the original transaction. Must be unique. In cases where an approval code does not apply, such as credit transactions, this field must be character space filled.
13AMOUNTNumeric, right justified, zero filled (if no value)12
145 and 156
Transaction amount in the currency designated by the currency code fieldYesContains the total transaction amount in the currency designated by the currency code. Zero-value transactions are not accepted.
14CURRENCY_CODEAlphanumeric, uppercase3
157 and 159
Currency code of the transactionYesContains the code of the currency used to execute the original transaction. It corresponds to the currency used for the AMOUNT field. The currency code format supports both ISO alpha and numeric values. For example, the ISO alpha code for U.S. Dollars is USD, and the numeric code is 840 .
15CONVERSION_RATEAlphanumeric6
160 and 165
--No--
16SEQUENCE_NUMBERNumeric, zero-filled if no value6
166 and 171
--No--
17CLEARING NUMBERNumeric, zero-filled if no value6
172 and 177
--No--
18SETTLEMENT_IDAlphanumeric20
178 and 197
--No--
19REFUND_SETTLEMENT_IDAlphanumeric20
198 and 217
--No--
20INSTRUMENT_EXPIRY_DATENumeric4
218 and 221
--No--
21MERCHANT_IDAlphanumeric2
222 and 233
--No--
22FILLERAlphanumeric1767
234 and 2000
Character spacesYesFor PayPal internal use only

Submission detail associated record

A No record. The primary record might have zero or multiple records tied to it.

PositionFieldTypeLength;
Start and end positions
ValueRequired?Description
1RECORD_TYPEAlphanumeric, uppercase7
1 and 7
SDAR002NoCorresponds to the record type and must be the first item in the record. The SDAR002 constant indicates a detail associated record.
2RECORD_NUMBERNumeric, right justified, zero filled (if no value)8
8 and 15
--NoContains a record sequence number to monitor the integrity and continuity of data in a file. The header record is always set to 00000001. Each subsequent record must be incremented to the RECORD_NUMBER value in the preceding record plus 1.
The number of records per file must not exceed 99999999.
3FILLERAlphanumeric1985
16 and 2000
Character spacesNoReserved for PayPal internal use.

Submission batch trailer

One file can contain multiple batch trailers, which correspond to the number of batch headers and are sorted by product and wallet brand.

PositionFieldTypeLength;
Start and end positions
ValueRequired?Description
1RECORD_TYPEAlphanumeric, uppercase7
1 and 7
SBTR001YesCorresponds to the record type and must be the first item in the record. The SBTR001 constant indicates a batch trailer record.
2RECORD_NUMBERNumeric, right justified, zero filled (if no value)7
8 and 14
YesContains a record sequence number to monitor the integrity and continuity of data in a file. The Header record is always assigned the value 00000001; and each subsequent record in the file must be incremented to a value "1" more than the RECORD_NUMBER entry.
The number of records per file must not exceed 99999999.
3PRODUCT_IDAlphanumeric, uppercase, left justified, character space filled11
15 and 25
--YesThe unique PayPal-assigned ID for a product.
4WALLET_BRANDNumeric, right justified, zero filled3
26 and 28
  • 001 PayPal.
  • 002. Venmo.
YesWallet associated with the specific transaction.
5TOTAL_NUMBER_OF_BATCH_TRANSACTIONSNumeric, right justified, zero filled8
29 and 36
--YesTotal number of 'Detail Primary Records' (DPR001) in this batch.
6TOTAL_NUMBER_OF_BATCH_CREDIT_TRANSACTIONSNumeric, right justified, zero filled8
37 and 44
--Yes--
7TOTAL_BATCH_CREDIT_AMOUNTNumeric, right justified, zero filled20
45 and 64
--Yes--
8TOTAL_NUMBER_OF_BATCH_DEBIT_TRANSACTIONSNumeric, right justified, zero filled8
65 and 72
--Yes--
9TOTAL_BATCH_DEBIT_AMOUNTNumeric, right justified, zero filled20
73 and 92
--Yes--
10NET_BATCH_AMOUNTAlphanumeric, uppercase, two decimal places implied, right justified, zero-filled, signed positive or negative20
93 and 112
TOTAL_BATCH_CREDIT_AMOUNT
TOTAL_BATCH_DEBIT_AMOUNT
YesFor US dollar (USD) and Canadian dollar (CAD) transactions, two decimal places are implied. An uppercase alpha code replaces the last digit in the transaction. This code indicates a debit amount. The debit codes and their numeric equivalents are:
  • 1. A.
  • 2. B
  • 3. C
  • 4. D
  • 5. E
  • 6. F
  • 7. G
  • 8. H
  • 9. I
  • 0. {.
  • -1. J.
  • -2. K
  • -3. L
  • -4. M
  • -5. N
  • -6. O
  • -7. P
  • -8. Q
  • -9. R.
The following example amounts show how debit and credit values appear:
AmountDebitCredit
$1.110000000011A0000000011J
$345.050000003450E0000003450N
$22.700000000227{0000000227}
11FILLERAlphanumeric8
113 and 2000
Character spacesYesReserved for PayPal internal use.

Submission file trailer

The full file contains only one file trailer. The file trailer corresponds to the submission file header.

PositionFieldTypeLength;
Start and end positions
ValueRequired?Description
1RECORD_TYPEAlphanumeric, uppercase7
1 and 7
SFTR001YesCorresponds to the record type and must be the first item in the record. The SFTR001 constant indicates a header record.
2RECORD_NUMBERNumeric, right justified, zero filled8
8 and 15
00000001YesContains a record sequence number to monitor the integrity and continuity of data in a file. The header record is always set to 00000001. Each subsequent record must be incremented to the RECORD_NUMBER value in the preceding record plus 1.
The number of records per file must not exceed 99999999.
3CLIENT_IDAlphanumeric, uppercase, left justified, character space filled11
16 and 26
--YesUnique PayPal-assigned ID.
4FILE_DIRECTIONAlphanumeric, uppercase, left justified, character space filled1
27 and 27
--YesDirection in which to send the submission file:
  • 1. PayPal to client.
  • 2. Client to PayPal.
5FILE_REFERENCE_NUMBERAlphanumeric, uppercase, left justified, character space filled12
28 and 39
System-generated file reference number, unique across PayPalYesContains a submitter-specified file reference number. Can be used to track this file. Value must be unique for each submitted file. A file identification and tracking cross-reference to the corresponding File Validation Report.
6FILE_CREATION_DATENumeric, CCYYMMDD8
40 and 47
Date the file was created (PST)YesCorresponds to the date when the submitter created the file. The format is CCYYMMDD, where:
  • CC. Century.
  • YY. Year
  • MM. Month
  • DD. Day.
For example, enter 20200215 for February 15, 2020.
7FILE_CREATION_TIMENumeric, HHMMSS (24-hour clock)6
48 and 53
Time the file was created (PST)YesCorresponds to the time when the submitter created the file. The format is HHMMSS, where
  • HH Hour (24-hour clock).
  • MM. Minute.
  • SS. Second.
For example, enter 143000 for 2:30 PM.
8FILE_VERSION_NUMBERAlphanumeric8
54 and 61
Version of the FileYesVersion of the File
9TOTAL_NUMBER_OF_BATCHESNumeric, right justified, zero filled8
62 and 61
--Yes--
10TOTAL_NUMBER_OF_FILE_TXNSNumeric, right justified, zero filled8
62 and 69
Yes--
11TOTAL_NUMBER_OF_FILE_CREDIT_TXNSNumeric, right justified, zero filled8
70 and 77
--Yes--
12TOTAL_FILE_CREDIT_AMOUNTNumeric, right justified, zero filled20
78 and 97
--Yes--
13TOTAL_NUMBER_OF_FILE_DEBIT_TXNSNumeric, right justified, zero filled8
98 and 105
--Yes--
14TOTAL_FILE_DEBIT_AMOUNTNumeric, right justified, zero filled20
106 and 125
--Yes--
15NET_FILE_AMOUNTAlphanumeric, uppercase, two decimal places implied, right justified, zero-filled, signed positive or negative20
126 and 145
Sum of all NET_BATCH_AMOUNTsYesFor US dollar (USD) and Canadian dollar (CAD) transactions, two decimal places are implied. An uppercase alpha code replaces the last digit in the transaction. This code indicates a debit amount. The debit codes and their numeric equivalents are:
  • 1. A.
  • 2. B
  • 3. C
  • 4. D
  • 5. E
  • 6. F
  • 7. G
  • 8. H
  • 9. I
  • 0. {.
  • -1. J.
  • -2. K
  • -3. L
  • -4. M
  • -5. N
  • -6. O
  • -7. P
  • -8. Q
  • -9. R.
The following example amounts show how debit and credit values appear:
AmountDebitCredit
$1.110000000011A0000000011J
$345.050000003450E0000003450N
$22.700000000227{0000000227}
16NET_FILE_ABSOLUTE_AMOUNTNumeric, right justified, zero filled20
146 and 165
NET_FILE_AMOUNT removing the sign--NET_FILE_AMOUNT removing the sign
17PAYMENT_DIRECTIONAlphanumeric, uppercase, left justified, character space filled (if no value)1
166 and 166
--YesDirection in which to send the submission file:
  • 1. PayPal to client.
  • 2. Client to PayPal.
18FILLERAlphanumeric1834
167 and 2000
Character spacesYesReserved for PayPal internal use.