• We’re modernizing the commercial card platform to enhance your current programs and enable more flexible, reliable capabilities going forward.

• The upgrade is planned for 2027. We will share more specific timelines as they are finalized.

• Transactions, auto-debit payments and cycle end dates will process every day—including weekends and holidays.
• If you receive files for card activity reporting, some data elements may change—such as company number—along with reporting frequency. We will engage you in the coming months based on what is applicable to your configuration.

• Card/account numbers, expiration dates, CVV/security codes and card plastics
• Company/account structure and credit limits
• Current platform, login credentials, payment groups/organizations and APIs
• Existing Auto Pay schedule and payment remittance addresses
• Relationship manager and customer service contacts

• Please check this website periodically for the latest updates (https://www.jpmorgan.com/payments/client-resource-center/mcp).
• We recommend ensuring the email address payment.solutions@paymentsolutions.jpmorgan.com and modern.card.payments.upgrade@jpmorgan.com is not reverting to your spam folders as it will be leveraged to send official communications related to the Modern Card Payments upgrade.

• Card transaction processing will move from 5 days to 7 days a week, including weekends and holidays to support daily posting and daily reconciliation.
• Posted transactions will now be processed 7 days a week, resulting in expanded online data availability. You may receive up to 7 files per week. 

• Review and update your scheduler for 365-day file intake and / or UI report downloads.
• Review whether any downstream processes or reporting routines need to be updated to adjust to the updated processing schedule and updated data fields.
• Ensure you have sufficient funds in your Demand Deposit Account (DDA) on Monday to cover auto-debit payments posted over the weekend.

• The DDA debit occurs on Monday, as money movement remains 5 days a week per ACH standard. Credit postings will now occur 7 days a week.
• On Monday, you may see separate debits for each day’s activity (e.g., Friday, Saturday, and Sunday) as applicable.

• Yes. Rebates will reflect weekend posting activity, including purchases and payments.

• You may need to update any reporting schedules in PaymentNet® that are not tied to billing cycles. Only reports and schedulers tied to your billing cycle will be updated when used in report criteria or scheduling.

• Your statement layout and formatting will be refreshed, resulting in a more standardized, modern format.

• Statement content and functionality is not changing—you will continue to receive the same information.
• Statements will continue to be delivered and available through your existing delivery channels and follow your delivery schedule.

• For most users, no action is required. If you consume statements electronically (e.g., using OCR to read statements), you may need to adjust your process.
• You may choose to review the updated statement format once available to familiarize your team with the refreshed layout.

• Yes – click here to preview your updated statement.

• No. Once the updated statement format is enabled, it cannot be reverted.
• The new layout is designed to improve clarity, consistency, and ease of review.

• No. FX fees will remain the same and will continue to appear in the format you currently receive (embedded or shown separately, as applicable).

• The higher limits will apply broadly across the program,  enabling significantly higher capacity for corporate account limits (per-cycle dollar, transaction count and virtual card issuance caps), reducing the likelihood of hitting platform-imposed thresholds.

• No action is required.

• Yes. The increased capacity applies across products and programs, including virtual card issuance, at time of upgrade.

• Once the upgrade is complete, work with your Relationship Manager to evaluate whether a simplified structure is appropriate for your program.

• Due to the  infrastructure upgrade, account change requests are moving from batch processing to real-time processing within the same day requests are received.
• For example, new account issuance will change to same-day processing.

• No action is required.

• Purchases and payments will be available during the upgrade.

• Access to account details will be available.
• Access to balance inquiries will be available, but there may be delays.

• File transfers and file-based processing may be temporarily delayed during the upgrade. Normal processing will resume once upgrade activities are complete.
• In addition, certain setup activities – such as new card issuance or account creation for plastic cards – may be briefly paused while the upgrade is completed.
• Please check this site regularly for updates; additional timing considerations will be shared in Q4, 2026.

• No. Your card numbers, account numbers and login credentials will not change as a result of the upgrade.
• Your platform access and servicing contacts will also remain the same.

• The upgrade sequence is in two separate waves (approximately 3 months apart in 2027). J.P. Morgan will reach out in the coming months to confirm if any of your programs span two waves.
• If your programs upgrade in two waves, you may temporarily have two processing cadences in parallel—with some programs on 7‑day processing and others remaining on 5‑day processing. During this period, upgraded programs will use new data elements and delivery frequencies, while non-upgraded programs will continue with the current file/report formats and delivery patterns.

• You will continue receiving your files, but files from the earlier wave may differ in both data content and delivery cadence, so you’ll need to handle and process them appropriately (typically based on file naming). Once Wave 2 upgrades, both waves can follow the same future-state file protocol.

• A J.P. Morgan Modern Card Payments specialist will contact you to review which programs are in each wave. Please assess whether any downstream processes, reconciliation, reporting or vendor feeds will be impacted by running two standards in parallel.
• Ensure all recommendations from your J.P. Morgan Modern Card Payments specialist are incorporated prior to the upgrade to process correctly during the period between waves.

• Process files related to programs moving in Wave 1 using the new protocol. Keep files related to programs moving in Wave 2 on the current protocol until it upgrades, then ensure both follow the new protocol.

• CDF files are Mastercard’s standard outbound files that deliver commercial card transaction and hierarchy/reporting data into your systems (e.g., ERPs, expense tools, data warehouses). As part of the platform update, some CDF fields will populate with updated values. New fields may be added to enhance reporting.
• “On‑Receipt” (upon end of day processing) CDF file daily delivery will also align to 7‑day processing, shifting from a 5‑day cadence to 7 files per week (including one file on Saturday and one file on Sunday) to reflect weekend activity.
• CDF files are being updated to align to the new processing platform and modernized data standards. The file format remains the same; the changes relate to the values populated in certain fields.

• Content/value update: CDF field values will be updated for consistency, and we’ll provide an updated field-mapping summary. A J.P. Morgan Modern Card Payments specialist will reach out with further details in 2026.
• Frequency update: On‑Receipt CDFs will shift to daily delivery aligned with 7‑day processing, while fixed-schedule reports will remain unchanged.

• For CDF content/value changes
  • Review the mapping guide and sample files and identify where you use CDF fields, especially any hard-coded logic.
  • Review whether any downstream processes or reporting routines need to be updated to adjust to the updated processing schedule and updated data fields.
• For CDF frequency changes
  • Confirm your ingestion can pick up and process files over the weekend, including Sunday delivery.
  • Adjust automation/workflows and reconciliation to support more frequent file arrivals.

• Updates may be needed if your logic relies on specific CDF values that are changing, hard-coded mappings or custom business rules.

• Review the linked field-mapping summary and compare it to your current mapping and business rules to identify any updates that may be needed. If you have any questions, please contact your Relationship Manager or Modern Card Payments specialist. Please check back on this site later in 2026 for additional information and updates.

A sample file containing generic data is linked below.  To assist with reviewing the sample file, a schema and reference document are included. If you have questions regarding your program files, please review the table of changes for your respective file(s).

Mastercard CDF 

CDF Overview 

CDF Schema File 

Important: The attached sample reports contain generic test data and are provided for reference purposes only. Client-specific fields and values are not included. If testing with organization-specific data is required, the sample reports should be amended by the client prior to use. If you have any issues or concerns with your generic sample file, please inform your Relationship Manager or J.P. Morgan Modern Card Payments Specialist.

• No. The CDF structure remains the same; changes occur at the field values, mappings and data rules level.

• J.P. Morgan will work directly with major third-party vendors for Mastercard Common Data Format (CDF) file receipt to support continuity and visibility of data. You may receive outreach from your ERP/expense provider based on their readiness process.
• If affected, J.P. Morgan will reach out to you with additional information on your CDFs. Please review this site at a later date on how to handle additional vendors.

• On‑Receipt CDFs will shift to daily delivery aligned with 7‑day processing, while fixed-schedule reports will remain unchanged.

• It can affect the distribution of volume by day. For example, the Monday file may be smaller because weekend transactions are delivered on Saturday and Sunday.

• Files are not overwritten because they use unique date/time-based naming. However, if your systems do not retrieve and ingest a file, you may experience a gap in transaction data until it is processed.

• We will provide the field-level change details and supporting materials. Review whether any downstream processes or reporting routines need to be updated to adjust to the updated processing schedule and updated data fields.

• You should plan to complete internal updates and validation ahead of your upgrade wave. This allows time for testing using the field-mapping summary and any sample outputs we may provide. As a best practice, aim to complete readiness checks by year-end 2026.

• Mastercard User‑Defined Exports (UDEs) let you select specific fields from the CDF specification to create customized extracts and reports.
• After the platform upgrade, some UDE field values will change to align with updated data standards.
• These updates affect data values only—the UDE structure and layout does not change.

• Because UDEs are highly configurable, the exact impact can vary based on how your Smart Data administrator has designed your exports.
• If you also receive CDF files, you should expect UDE value changes to align with the corresponding CDF value changes.
• We will provide an updated field-mapping summary to support your review and validation. Please check this site later in 2026.

• Identify where your systems, integrations or reports reference UDE fields, especially any custom logic or hard-coded values.
• Review the field-change summary when shared by your Relationship Manager or Modern Card Payments specialist and compare it to your current mapping and business rules to identify required updates.
• Review whether any downstream processes or reporting routines need to be updated to adjust to the updated processing schedule and updated data fields.
• Decide whether you want to consume any newly introduced fields (optional).
• Confirm your engineering and/or reporting teams are prepared to implement and validate updates ahead of upgrade.

• Potentially—especially if you rely on specific data values, hard-coded mappings or custom business rules. Review whether any downstream processes or reporting routines need to be updated to adjust to the updated processing schedule and updated data fields.

• Review the field-mapping summary when shared by your Relationship Manager or Modern Card Payments specialist and compare it to your current mapping and business rules to identify required updates. Please check this site later in 2026.

A sample file containing generic data is linked below. If you have questions regarding your program files, please review the table of changes for your respective file(s).

Mastercard UDE

Important: The attached sample reports contain generic test data and are provided for reference purposes only. Client-specific fields and values are not included. If testing with organization-specific data is required, the sample reports should be amended by the client prior to use. If you have any issues or concerns with your generic sample file, please inform your Relationship Manager or J.P. Morgan Modern Card Payments Specialist.

• We will provide the field-level change details and supporting materials for you to update your internal mappings, rules and downstream processing as needed. If this affects you, a J.P. Morgan Modern Card Payments specialist will reach out with further details in 2026. You are always welcome to contact your Relationship Manager or Program Coordinator with questions.

• You should plan to complete internal updates and validation ahead of your upgrade wave. This allows time for testing using the field-mapping summary and any sample outputs we provide. As a best practice, aim to complete readiness checks by year-end 2026. 

• Yes. UDEs can be scheduled or run on demand. With 7‑day processing you can generate exports using the most recent data, or run them as needed.

• It depends on how your organization uses UDE/CDF data. If you ingest many fields or rely on hard-coded mappings and business rules, updates may require coordination across multiple teams. Once a Modern Card Payments specialist reaches out, they will provide a field-mapping summary to help you assess scope for your specific integrations.

• There is no fallback or fall-forward logic for scheduled UDEs that fall on a weekend.  Scheduled UDEs follow a fixed calendar date, rather than shifting based on weekends.

• Visa Common Format (VCF) files are Visa’s standard outbound files used to deliver commercial card transaction details, hierarchy attributes and other critical data into your systems (e.g., ERPs, expense tools, data warehouses).
• As part of the upgrade:
  • Several VCF fields will populate with updated values for consistency across the modernized platform.
  • New fields may be introduced to enhance reporting.
• In addition, VCF delivery frequency will change to align with 7‑day processing:
  • VCF files are currently delivered on a 5‑day cadence for many setups.

Depending on your existing file frequency, you may see an increase up to 7 days a week after the upgrade.

• Content/value updates
  • We will provide an updated field-mapping summary so you can validate changes before they take effect. Please check this site later in 2026.
  • Your hierarchy structure is not changing. However, certain hierarchy node values in the file will be updated as part of the platform change.
• Frequency updates
  • FIFO (First In First Out files sent upon activity) will be delivered daily, including weekends, to reflect 7‑day processing.
  • Fixed-schedule reports (weekly, monthly, custom schedules) will remain unchanged.
  • If you receive daily files on a set number of days per week (e.g., 4/5/6 days), you may want to consider moving to 7 days to align with daily processing.

• Identify where your systems, integrations or reports reference VCF fields, especially any custom logic or hard-coded mappings.
• Review the field-mapping summary when provided and compare it to your current processing logic to determine any updates needed.
• Review whether any downstream processes or reporting routines need to be updated to adjust to the updated processing schedule and updated data fields.
• Ensure your ingestion and operational processes can support weekend file arrivals (automation, staffing coverage, reconciliation).

• Review the linked field-mapping summary and compare it to your current mapping and business rules to identify any updates that may be needed. If you have any questions, please contact your Relationship Manager or Modern Card Payments specialist. Please check back on this site later in 2026 for additional information and updates.

A sample file containing generic data is linked below. If you have questions regarding your program files, please review the table of changes for your respective file(s).

Important: The attached sample reports contain generic test data and are provided for reference purposes only. Client-specific fields and values are not included. If testing with organization-specific data is required, the sample reports should be amended by the client prior to use. If you have any issues or concerns with your generic sample file, please inform your Relationship Manager or J.P. Morgan Modern Card Payments Specialist.

• Your new Company ID will be communicated ahead of the change.

• A dedicated test environment will not be provided, but sample VCF files will be shared to support validation and updates.

• J.P. Morgan will work directly with major third-party vendors for Visa Commercial Format (VCF) file receipt to support continuity and visibility of data. You may receive outreach from your ERP/expense provider based on their readiness process.
• If affected, J.P. Morgan will reach out to you with additional information on your VCFs. Please review this site at a later date on how to handle additional vendors.

• Yes. You can request changes through your Program Coordinator.
• Weekly files remain unchanged. For daily delivery on a fixed set of days, moving to a 7‑day cadence is typically recommended to align with daily processing.
• For FIFO (upon activity) delivery, frequency changes to align with 7‑day processing are expected to be handled automatically.

• Yes, though if you receive files on many scheduled days per week, moving to 7 days a week is generally recommended to better align to activity and daily processing.

• VCF files are not overwritten because they include unique identifiers, but missing ingestion can create gaps in downstream reporting and reconciliation until the files are processed.

Select report and mapper outputs will include updated data elements and will increase in frequency from 5-day to 7-day processing. Some report fields will populate with updated values while others will be removed. New fields may be added to enhance reporting.

We will provide an updated field-mapping summary so you can validate changes before they take effect. A J.P. Morgan Modern Card Payments specialist will reach out with further details later in 2026.

• The following data fields will be decommissioned but the report column headers will persist in preserving file structure consistency:
  • Bank, Agent, Credit Ratings
  • Credit Rating field will be retired from PaymentNet user interfaces and will no longer be visible in screens such as Account Detail pages or in standard reports.
• Company Number (ID) is upgraded from 5-digits to a 7-digit number. This number will include a tailored 2-digit prefix to the current 5-digit ID.
  • Fixed-Length Files: increase in 2 bytes due to the additional 2-digits in the company number. Ensure the file format change aligns with your systems and processes.
  • Non-Fixed-Length Files: Ensure your systems and processes can support the new 7-dit company number format.
• Review the linked field-mapping summary and compare it to your current mapping and business rules to identify any updates that may be needed. If you have any questions, please contact your Relationship Manager or Modern Card Payments specialist. Please check back on this site later in 2026 for additional information and updates.

Adjustments to company number and bulk remittance data should be seamless for the client. J.P. Morgan will translate the remittance data on behalf of existing clients.

• Transaction posting activity will now occur Monday through Sunday and will be reflected in PaymentNet accordingly.
• Scheduled mapper or report files that run Monday through Friday only will be updated  to align with a 7-day schedule. After upgrade, all outputs will generate  7 days a week.
• Transmitted file extracts will be scheduled for 7 days a week, which may require updates to internal processes responsible for retrieving, processing, or reconciling files, particularly if weekend access is not currently supported (e.g., SFTP).

No client action is required. Ahead of the upgrade date, J.P. Morgan will proactively update your PaymentNet cycle configurations to align with this new logic. 

Updates may be needed if your logic relies on specific report values that are changing i.e., bank, company number, etc. and if you have hard-coded mappings or custom business rules.

We will provide the field-level change details and supporting materials for you to update your internal mappings, rules and downstream processing as needed. If this affects you, a J.P. Morgan Modern Card Payments specialist will reach out with further details later in 2026. You are always welcome to contact your Program Coordinator or Relationship Manager with questions.

For PaymentNet content/value changes:

• Review the mapping guide and identify where you use PaymentNet fields, especially if you have any hard-coded logic.
• Validate parsing, transformations, and output logic to ensure the updated/blank values are handled correctly.
• Ensure data transmissions, technical, engineering and reporting teams are ready to support and intake updated field values after the upgrade.

For PaymentNet file frequency changes:

• Review whether any downstream processes or reporting routines need to be updated to adjust from the 5-day to 7-day processing schedule and updated data fields.
• Confirm your ingestion can pick up and process files over the weekend, including Sunday delivery.
• Adjust automation/workflows and reconciliation to support more frequent file arrivals.

Once we provide field level details, you should plan to complete internal updates and validation ahead of your upgrade in 2027. This allows time for testing using the field-mapping summary. Please target validations and any triage by year-end 2026. 

You can request the removal of the empty field headers columns after the upgrade through your J.P. Morgan relationship manager. 

• As part of J.P. Morgan’s Modern Card Payments (MCP) initiative, enhancements to underlying data elements, including updates to Company Number formats and other impacted fields, will be reflected across PaymentNet following migration.
• After upgrade, these outputs reflect the updated data values available within the platform at that time. 
• Historical reports or exported files generated prior to upgrading will not be updated and will continue to reflect the data values that were present at the time those files were created.

• Review the linked field-level details which includes new and removed data elements. You may use these supporting materials to help you update your internal mappings, rules, and downstream processes as needed.
• The following data fields will be decommissioned but the report column headers will persist in preserving file structure consistency:
  • Bank, Agent, Credit Ratings
• Company Number (ID) is upgraded from 5-digits to a 7-digit number. This number will include a tailored 2-digit prefix to the current 5-digit ID. 
• Cardholder Application (previously Account Request Manager) will include the updated 7-digit Company Number. This update will be systematic and not impact any processing or application experience. Historical applications will continue to reflect the prior 5-digit Company Number. The existing application web links provided to your employees will not change with this event. 

• No, you do not need to take action. J.P. Morgan will manage updates to mapper schedules and billing cycle reports on your behalf.
• J.P. Morgan will also proactively update your PaymentNet cycle configurations to align with 7-day processing if needed. This will simplify PaymentNet cycle configurations and enable more consistent and predictable criteria for file extracts and scheduling.
• Additional PaymentNet Help topics will be made available later in 2026 for additional guidance. 

No, J.P. Morgan will not adjust PaymentNet Hierarchy IDs. If a you would like to adjust these, you may do so within PaymentNet.

Your file configuration will remain unchanged. If you currently receive blank files or if files are only generated when activity occurs, this behavior will remain the same after the update unless you choose to modify your configuration.

• PaymentNet will introduce a process to eliminate all static file names generated within the platform.
• For PaymentNet users with Host-to-Host (H2H) configuration using a static file name, if a file is not retrieved, it will be overwritten.
• Clients are strongly encouraged to update their internal processes, including file mapper scheduling and file ingestion jobs, to ensure readiness for 7‑day processing.

• Due to the infrastructure upgrade, select Smart Data Standard Reports will include updated data values.
• These updates primarily affect data values only.  Report schedules, structures, layouts, and calculations remain unchanged.

• Smart Data Standard Reports will automatically reflect updated data values after your program upgrades. No client action is required to facilitate the change.
• We will provide an updated field-mapping summary so you can validate changes before they take effect. A J.P. Morgan Modern Card Payments specialist will reach out with further details later in 2026.

• Identify where your systems, integrations or reports reference Smart Data Standard Report fields, especially any custom logic or hard-coded values.
• Once we provide the field mapping summary, review the field-change summary and sample reports and compare it to your current mapping and business rules to identify required updates.
• Review whether any downstream processes or reporting routines need to be updated to adjust to the updated data fields.
• Ensure data transmissions, technical, engineering and reporting teams are ready to support and intake updated field values after the upgrade.

Updates may be needed if your logic relies on specific report values that are changing i.e., bank, company number, etc. and if you have hard-coded mappings or custom business rules.

Review the linked field-mapping summary and compare it to your current mapping and business rules to identify any updates that may be needed. If you have any questions, please contact your Relationship Manager or Modern Card Payments specialist. Please check back on this site later in 2026 for additional information and updates.

A sample file containing generic data is linked below. If you have questions regarding your program files, please review the table of changes for your respective file(s).

Monthly_Spend_Report

Delinquency_Report

Audit_Report

Important: The attached sample reports contain generic test data and are provided for reference purposes only. Client-specific fields and values are not included. If testing with organization-specific data is required, the sample reports should be amended by the client prior to use. If you have any issues or concerns with your generic sample file, please inform your Relationship Manager or J.P. Morgan Modern Card Payments Specialist.

We will provide the field-level change details and supporting materials for you to update your internal mappings, rules and downstream processing as needed. If this affects you, a J.P. Morgan Modern Card Payments specialist will reach out with further details later in 2026. You are always welcome to contact your Program Coordinator or Relationship Manager with questions.

You should plan to complete internal updates and validation ahead of your upgrade in 2027. This allows time for testing using the field-mapping summary. As a best practice, aim to complete readiness checks by year-end 2026. 

Reports will maintain the existing column structures and layouts after the upgrade as well as the same calculation logic.  Only the underlying data values and fields may change.

No reports will be sunset or retired, all standard reports will remain available after the upgrade.

• Due to the infrastructure upgrade, Smart Data Custom Reports will include updated data values.
• These updates primarily affect data values only.  Report schedules, structures, layouts, and calculations remain unchanged.

• Smart Data Custom Reports will automatically reflect updated data values after your program upgrades. No client action is required to facilitate the change.
• We will provide an updated field-mapping summary so you can validate changes before they take effect. A J.P. Morgan Modern Card Payments specialist will reach out with further details in 2026.

• Identify where your systems, integrations or reports reference Smart Data Custom Report fields, especially any custom logic or hard-coded values.
• Once we provide the field-change summary and sample reports, compare it to your current mapping and business rules to identify required updates.
• Review whether any downstream processes or reporting routines need to be updated to adjust to the updated data fields.
• Ensure data transmissions, technical, engineering and reporting teams are ready to support and intake updated field values after the upgrade.

Updates may be needed if your logic relies on specific report values that are changing i.e., bank, company number, etc. and if you have hard-coded mappings or custom business rules.

Review the linked field-mapping summary and compare it to your current mapping and business rules to identify any updates that may be needed. If you have any questions, please contact your Relationship Manager or Modern Card Payments specialist. Please check back on this site later in 2026 for additional information and updates.

Yes. We expect to have a generic sample file containing dummy data between Q3 and Q4 2026. If you have questions regarding your program files, please review the table of changes for your respective file(s). If you still require a sample file and one has not been made available to you by Q4 2026, please contact your Relationship Manager or Modern Card Payments representative.

We will provide the field-level change details and supporting materials for you to update your internal mappings, rules and downstream processing as needed. If this affects you, a J.P. Morgan Modern Card Payments specialist will reach out with further details in 2026. You are always welcome to contact your Relationship Manager or Program Coordinator with questions.

You should plan to complete internal updates and validation ahead of your upgrade in 2027. This allows time for testing using the field-mapping summary. As a best practice, aim to complete readiness checks by year-end 2026. 

Yes. We expect to have sample custom reports containing simulated data available later in 2026.

Reports will maintain the existing column structures and layouts after the upgrade as well as the same calculation logic.  Only the underlying data values and fields may change.

• Yes. Custom reports that have not been executed within the past 24 months will be discontinued as part of the upgrade.  If this affects you, a J.P. Morgan Modern Card Payments specialist will reach out with further details in 2026. You may also contact your Relationship Manager or Program Coordinator with any questions.
• Custom reports that have been run within the past 24 months will remain available after the upgrade.  This includes the following custom reports:
  • Cardholder Management Report
  • Chase Account Statement Report
  • MCCG (Merchant Category Code Group) Report
  • New Card Account Application Audit Report and
  • Select Client-Specific Custom Reports
• If you have concern about the availability of a specific report, please let your J.P. Morgan Representative know and we will be happy to check the availability of the report after the upgrade.