How to Cross-List on Every Marketplace with UniCon
Reading Time: 9 minutes Your buyers are not shopping in one place anymore. They search…
Heads-up: eBay is changing what U.S. personal and financial data appears in MIP Order Reports accessed via SFTP. Review your integrations before the deadline.
What’s changing
eBay has informed sellers using its Merchant Integration Platform (MIP) that, starting September 30, 2025, certain user and financial data for U.S. persons will be handled differently in Order Reports, in preparation for compliance with the U.S. Data Security Program (DSP).
- Username replacement: Publicly displayed usernames (e.g.,
buyerID,sellerID) for U.S. persons will no longer appear in MIP Order Reports accessed via SFTP. Instead, reports return a unique, immutable user ID. - Financial data restriction: Information about payment instruments/methods (e.g., instrument type or last 4 digits) for U.S. buyers will no longer be returned to third-party applications owned or developed in specific regions (China & its territories, Venezuela, North Korea, Russia, Cuba, Iran) via MIP Order Reports over SFTP.
Why these changes are being made
- To align eBay’s data handling with requirements under the U.S. Data Security Program (DSP), limiting access to sensitive personal data of U.S. persons, especially by apps/entities in high-risk regions.
- With a federal deadline approaching, platforms are updating reporting, data access, and compliance policies to reduce legal/regulatory exposure.
Who is affected
- All eBay sellers using MIP who access Order Reports via SFTP and/or have authorized third-party apps developed in the specified regions.
- Sellers whose reporting systems or downstream services rely on buyer usernames/IDs or partial payment instrument info for U.S. users. These systems will need updates.
What sellers should do
- Review apps & integrations: If your tools or third-party apps (especially from affected regions) rely on buyer usernames or last-4 card digits, plan for those fields to stop appearing.
- Switch identifiers: Migrate logic to use the immutable user ID for buyer/seller identification where required.
- Audit data flows: Check downstream systems/reports for dependencies on excluded fields; adjust workflows, mapping, and validations.
- Check compliance & risk: Confirm that you and any partners meet DSP requirements; non-compliance can lead to penalties.
- Watch official guidance: Monitor eBay MIP developer documentation, announcements, and seller emails for any field mapping updates before/after go-live.
Important nuances & caveats
- Applies to U.S. persons’ data in the MIP + SFTP context and to certain third-party app regions. Not all sellers or all data.
- Changes affect what data is returned in Order Reports; they do not necessarily change how orders are processed or payments are handled.
- Regions with stricter limitations: China & its territories, Venezuela, North Korea, Russia, Cuba, Iran. If your tools/company operate in or are partly based in these regions, verify whether you’re restricted.
| Scope | Detail |
|---|---|
| Data subjects | U.S. persons (buyers/sellers) in MIP Order Reports |
| Delivery channel | MIP Order Reports via SFTP |
| Restricted third-party regions | China & its territories, Venezuela, North Korea, Russia, Cuba, Iran |
FAQ
Will buyer/seller usernames still appear?
No. For U.S. persons, public usernames like buyerID and sellerID will be replaced with a unique, immutable user ID in MIP Order Reports via SFTP.
Will payment method details (e.g., last-4) be visible?
Not to third-party apps owned or developed in the listed regions. Those fields will no longer be returned for U.S. buyers in MIP Order Reports via SFTP.
Does this affect order processing or payouts?
These changes focus on reporting data. They do not necessarily change how orders are processed or payments are handled outside of reporting.
When does this take effect?
September 30, 2025. Review and update your integrations ahead of this date.
Source: Value Added Resource
Next step: If you rely on MIP Order Reports, ensure your workflows are ready by Sept 30, 2025 by working closely with your integration or tech partners.
