Skip to main content
Optimization Protection

Incremental file

The Account Updater incremental file is a specialized batch file provided to you if you are enrolled in the Account Updater service and have opted to receive incremental updates. This file contains only the most recent changes to cardholder account information, including new card numbers, updated expiration dates, and account closures since the last file delivery. This allows you to keep your payment records current without processing redundant data. Unlike real-time updates delivered through API, the incremental file is securely transmitted through the Managed File Transfer Service (MFTS).

Before you begin:

To receive incremental updates, first ensure you have:

  • Enrolled in the Account Updater service.
  • Opted in to receive the Account Updater incremental file.
  • Contacted your J.P. Morgan relationship manager for MFTS onboarding.

How incremental files work

To initiate and receive the incremental file through MFTS, follow these steps:

  1. Request a PGP public key:
    Obtain the J.P. Morgan Pretty Good Privacy (PGP) public key from your J.P. Morgan representative.
  2. Submit your public key:
    Provide your own PGP public key to your J.P. Morgan representative.
  3. Download files:
    Access and download the daily incremental files from your designated MFTS folder. All files are encrypted using PGP with your public key.

Incremental file delivery

You receive incremental files with the following characteristics:

  • Each incremental file includes all eligible billable updates processed within a 24-hour window (00:00 UTC to 23:59 UTC).
  • Files are generated and delivered daily after the completion of the daily processing window.
  • You receive an empty daily file if there are no billable updates during the 24-hour window.
  • You receive multiple files if the number of billable updates within the 24-hour window exceeds the maximum record limit in the incremental file.

Incremental files format

The Account Updater incremental file uses a record-based layout consisting of:

  • Header records
  • Detail records
  • Control records

File naming convention

The file name follows this format:

{MerchantID}.{FileCreateDate}.{TimePrefix}.{FileSequenceNumber}

Example:
160141720555.251112.213251.001

File size and record count limits

File size and limits
Parameter Limit
Maximum file size 100MB
Maximum number of records 1,000,000 per file

Sample file 

Plaintext
*BEG,CO=160141720555,251028
DI,,6011111111111117,2411,6011111111111117,2911,NEW_EXPIRY,N,N,,
VI,,4111111211111111,2712,4111111262630101,2712,NEW_ACCOUNT,N,N,,
VI,,4111121111111113,2305,4111121138377381,2805,NEW_ACCOUNT_AND_EXPIRY,N,N,,
VI,,4111121111111112,2310,4111121111111112,2810,NEW_EXPIRY,N,N,,
VI,,4111121111111115,2411,,,CONTACT_CARDHOLDER,N,N,,
VI,,4111211111111119,2410,,,CLOSED_ACCOUNT,N,N,,
DI,,6011111111111115,2510,,,CONTACT_CARDHOLDER,N,N,,
VI,000000,4111211111111112,2310,4111211111111112,2810,NEW_EXPIRY,N,N,29d534e9-187f-42b6-b4f4-52de90944ae2,1234567890
VI,000000,4111565711111115,2412,,,CONTACT_CARDHOLDER,,N,dcdbd096-bcbb-45bb-8840-8ac00d43294c,
TRECS,9
*END,CO=160141720555,251028
EOFEOFEOF

Record definitions

Record definitions
Record type Format/Fields Description
Header record *BEG,CO={MerchantCompanyNumber},{FileDate} Indicates the start of file; includes the merchant and the date.
Detail record MOP,TxnDivisionID,OldAccount,OldExpiry,NewAccount,NewExpiry,ReasonMessage,PrevSentFlag,PaymentMethodChanged,MerchantRecordID,SubMID Contains the updated account details and the related information.
Totals record TRECS,{TotalRecordCount} Shows the total number of detail records in the file.
Trailer record *END,CO={MerchantCompanyNumber},{FileDate} Indicates the end of file; repeats the merchant and the date.
EOF marker EOFEOFEOF Marks the physical end of the file.

Detail record fields

Detail record fields
Field name Description
MOP Method of payment (for example, VI, MC, DI)
TxnDivisionID Transaction division identifier
OldAccount Previous card number
OldExpiry Previous expiry (YYMM)
NewAccount Updated card number
NewExpiry Updated expiry (YYMM)
ReasonMessage Update reason (for example, NEW_EXPIRY, NEW_ACCOUNT, CLOSED_ACCOUNT)
PrevSentFlag Indicates if record was previously sent
PaymentMethodChanged Indicates change in payment method
MerchantRecordID Merchant internal reference
SubMID Sub-merchant ID