Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- On August 19, 2026, eBay added ReferenceTypeEnum.PSNAD_ID in Finances API 1.19.1.
- The value identifies Partial Significantly Not as Described claims and can appear in the Reference returned by getTransactions.
- This is not a new refund API and does not mean every PSNAD is a full refund. Actions still depend on transaction type, amount, status and associated references together.
- First inspect enum deserialization, SDK versions, database constraints, warehouse mappings and unknown-value alerts so one new enum cannot block an entire sync batch.
- Roll out compatible parsing, retention of original values, sample replay and finance review. Never silently map an unknown enum to an ordinary refund.
PSNAD_ID changes a reference type, not the main transaction status
PSNAD stands for Partial Significantly Not as Described, a claim involving part of the goods or amount being significantly different from the description. This release only confirms the addition of PSNAD_ID to ReferenceTypeEnum and its use to identify such claims.
Reference associates a transaction with external business objects. Do not automatically refund, close orders or rewrite dispute status merely because PSNAD_ID appears. Read the current transaction type, status, amount, currency and other references together, then let existing business rules determine the action.
The hard-to-detect failure: a 200 response with a gap in the accounts
This is easy to misdiagnose: the request succeeds and the scheduled job reports completion, so the team keeps checking the network and rerunning jobs until finance finds mismatched transaction counts and totals at day-end. Clients that generate strict enums from official schemas and throw on unknown values face the highest risk. One PSNAD_ID can make an entire getTransactions page fail deserialization after the response arrives.
If failure occurs before saving the cursor, the same page may be fetched repeatedly. If an exception is swallowed while pagination advances, a less visible accounting gap remains. Check database CHECK constraints, BI dimension tables, message schemas and switch branches too. Upgrading the SDK alone cannot repair closed lists in downstream warehouses or reports.
Five compatibility checks
First, find every ReferenceTypeEnum parser and branch. Second, ensure unknown values can be saved as original strings and classified as UNKNOWN_OR_NEW. Third, add the PSNAD_ID mapping to the database and warehouse. Fourth, replay redacted payloads containing it through pagination, retries and idempotency logic. Fifth, have finance confirm the report label and handling boundaries.
Compatible parsing does not mean ignoring new values. Record the API version, transaction id, reference id, first-seen time and original enum, and raise a low-noise alert for new values. Assign a stable classification after confirming the business meaning.
Separate reconciliation from automated actions
A report can display PSNAD_ID as a “partial significantly-not-as-described reference” to find related transactions. Financial confirmation still follows the amounts and transaction semantics returned by the Finances API. Do not infer a refund percentage from the abbreviation or merge it with full SNAD, returns or general adjustments.
Any rule that automatically refunds, sends messages or updates ERP status needs explicit conditions and idempotency keys. When the new enum first goes live, observe it read-only and compare samples with Seller Hub records before gradually enabling automated actions.
Checks before and after release
Before release, test old and new payloads, an invented unknown enum, empty references, multiple references and pagination replay. Confirm one parsing failure cannot discard an entire batch. After release, compare API fetch counts, stored counts, unknown-enum counts and finance report totals, retaining replayable request ids and time windows.
If the SDK does not yet publicly support the value, a temporary string-compatible layer can help, but do not alter the official response or discard the original value. If totals differ, freeze automated actions first, preserve raw responses and cursors, then inspect parsing, mappings and finance rules separately.
Keep network errors separate from schema errors
Timeouts, DNS, TLS and proxy authentication occur before a request reaches the API; a PSNAD_ID parsing failure occurs after receiving a successful response. Record the HTTP status, whether the response body is complete and the parsing exception location before deciding to retry or fix the schema.
For stable developer-console access across regions, visit the PuppyIP website to learn about fixed network exits and consult the proxy connection checklist. A network exit does not change eBay enums or claim rules.
Sources
Frequently Asked Questions
What is eBay PSNAD_ID?
It is a new Finances API ReferenceTypeEnum value identifying a reference to a Partial Significantly Not as Described claim.
Which API can return PSNAD_ID?
The official release notes point to Reference in getTransactions. Check that API and parsing paths sharing the Reference schema.
Should PSNAD_ID trigger an automatic refund?
No financial action should depend on this reference type alone. Also check the transaction type, status, amount, currency and associated business records.
What if an old SDK does not recognize the enum?
Check for an SDK supporting the 1.19.1 schema. Before and after upgrading, retain compatibility for unknown strings, original values and alerts so an entire batch does not fail deserialization.
Which database mappings need updating?
Check enums, CHECK constraints, dimension tables and report groups, and add PSNAD_ID. Keep an UNKNOWN_OR_NEW fallback so the next new value does not interrupt processing again.
How can we verify the upgrade did not omit transactions?
Replay old and new payloads through pagination and idempotency logic, then compare fetched counts, stored counts, unknown values and financial totals. Pause automated actions until differences are explained.