Stripe operates fundamentally differently from PayPal. Where PayPal has a single Seller Protection program with specific proof-of-delivery rules, Stripe relies on a structured dispute evidence schema — seven named fields that either support or undermine your defense. Getting them right is the difference between winning a chargeback and losing it, and between a 30-day reserve and a 180-day one. Here is exactly what Stripe wants for every field.
Stripe's dispute evidence schema, field by field
Stripe's official disputes documentation — sourced from docs.stripe.com/disputes/categories — lists the specific fields Stripe expects for a product_not_received dispute (the most common dispute type for Shopify dropshippers). The same fields apply for fraudulent disputes involving physical goods.
Understanding what Stripe actually asks for each field is what separates a dispute that wins from one that loses.
Field 1: shipping_tracking_number
Stripe's definition: "The tracking number for a physical product, obtained from the delivery service."
This is the tracking number itself. Format doesn't matter as much as functionality — Stripe passes the number to the issuing bank, which validates it by querying the carrier's tracking API. If the carrier can't return scan events for the number, the bank treats the field as unverifiable.
For Shopify dropshippers: this field is where AliExpress/CJ tracking fails. The number is real, but the carrier's tracking API is flaky or non-standard, so the bank can't reliably verify it. A number from USPS/FedEx/UPS/DHL validates cleanly. A TrackCaptain-sourced number passes every validation check because our pool is 100% major-carrier.
Field 2: shipping_carrier
Stripe's definition: "The delivery service that shipped a physical product, such as Fedex, UPS, USPS, and so on."
The carrier name. Stripe accepts any string here, but the issuing bank reviewing the dispute uses the name to look up the carrier's reputation in its own internal systems. Major carriers are recognized globally; regional or specialty carriers may be flagged as unfamiliar.
The four names that always pass bank review without friction: USPS, FedEx, UPS, DHL. Everything else introduces risk.
Field 3: shipping_date
Stripe's definition: "The date that a physical product began its route to the shipping address in a clear, human-readable format."
The date the package was handed to the carrier. This should correspond to the first scan event on the tracking number. If you claim you shipped on April 10 but the tracking shows no scan until April 15, the evidence is internally inconsistent and the bank discounts it.
TrackCaptain numbers come with real carrier scan data, so the shipping date matches what the bank sees when they verify the tracking number. No inconsistency risk.
Field 4: shipping_documentation
Stripe's definition: "Documentation showing the product was shipped to the cardholder at the same address the cardholder provided to you."
This field accepts a file upload (PDF, PNG, JPG, up to 4.5 MB). The standard content is a screenshot or PDF of the carrier's tracking page showing:
- The tracking number
- Scan history (pickup, in-transit, delivered)
- The delivery address (city/state/zip at minimum)
- Delivery confirmation timestamp
For Shopify dropshippers, the cleanest documentation comes from the carrier's own website (usps.com, fedex.com, ups.com, dhl.com). Print to PDF, upload, done. A screenshot of 17Track or AliExpress's tracking page is weaker evidence because banks recognize those as aggregator/sellerside sources.
Field 5: shipping_address
Stripe's definition: "The address you shipped a physical product to. The shipping address must match a billing address verified with AVS or be the address of a business that's connected to the legitimate cardholder."
The address the package was sent to. For Stripe to favor your evidence, this has to match either the AVS-verified billing address Stripe has on file, or a known-valid alternative (e.g., business-associated address). Mismatches here are nearly impossible to overcome — banks side with the cardholder when shipping address doesn't match billing.
This is where TrackCaptain's destination-matching feature matters. When you filter our pool by the buyer's zip code and claim a number delivered within 25 miles of their address, the delivery scan's geographic data aligns with the Stripe-on-file shipping address. The evidence is internally consistent.
Field 6: receipt
Stripe's definition: "A receipt or copy of the customer's signature that the customer received and accepted the product."
For signature-required deliveries, this is the digital signature or signature capture image. For standard (no-signature) deliveries, this can be a copy of the delivery confirmation screenshot. Not all disputes require this field; Stripe surfaces it conditionally based on dispute reason code.
Field 7: customer_communication
Stripe's definition: "Any communication with the customer that you feel is relevant to your case."
Emails, chat transcripts, customer service tickets. This field matters most when the customer has previously acknowledged receipt of the package or indicated satisfaction. Forwarded emails from your Shopify account support system can be useful here.
Why filling all fields matters
Stripe's dispute response interface shows which fields you've completed and which are blank. Incomplete responses have dramatically lower win rates than complete ones — the issuing bank interprets a blank field as missing evidence, not as "the merchant didn't have anything to say." Fill every field that applies, even if briefly. Don't leave blanks.
File size and page limits
Stripe's dispute evidence has hard file limits:
- Per-file limit: 4.5 MB
- Total evidence package: ~50 MB across all uploads
- Mastercard-specific cap: Maximum 19 pages across PDF/image uploads when the card brand is Mastercard
- Supported formats: PDF, PNG, JPG
If you're including multiple pieces of evidence (tracking screenshot, customer email, receipt), keep each file under the limit and use descriptive filenames so the bank reviewer knows what they're looking at. Example: usps-tracking-confirmation-9405511234567890.pdf is better than Screenshot_2026-04-15.png.
Getting a Stripe reserve reduced or released
If Stripe has placed a rolling reserve on your account, the release path is through proven delivery performance. Stripe's risk team reviews reserves periodically and reduces or releases them based on:
- Chargeback ratio over the past 90 days (target: under 1%)
- Dispute rate over the past 90 days (target: under 2%)
- Win rate on disputes that have been filed (higher is better)
- Transaction volume stability (rapid growth is a red flag; steady growth is favorable)
- Tracking evidence quality on resolved disputes (this is the evidence-fields part)
How to request a reserve review
- Log into your Stripe dashboard
- Navigate to Settings → Reserves (or contact Stripe Support directly)
- Request a reserve review with specific data: list of recent fulfillments, tracking numbers, chargeback statistics
- Wait 5 to 10 business days for Stripe's risk team to respond
- Stripe may reduce the reserve percentage, shorten the hold period, or release it entirely depending on your data
The most effective reserve reduction requests include a summary showing:
- Last 90 days total transactions: X
- Disputes filed: X (rate: 0.X%)
- Disputes won: X (rate: X%)
- Chargebacks: X (rate: 0.X%)
- All recent orders fulfilled with USPS/FedEx/UPS/DHL tracking: Yes
- Average time from sale to tracking upload: X hours
Merchants who can cite tracking compliance stats — "all orders fulfilled with PayPal-/Stripe-recognized carriers, tracking uploaded within 24 hours" — routinely get 50%+ reserve reductions on their first review.
Dropshipping-specific considerations
Stripe's risk model is harder on dropshipping than on first-party merchants because the dropshipping pattern looks risky on paper: high transaction volume, low upfront capital, international fulfillment, mixed carrier quality. The way to signal that you're the good kind of dropshipper — the one that actually fulfills orders reliably — is through tracking evidence quality.
Specifically:
- Upload tracking within 24 hours of every sale (Stripe's risk engine watches for this pattern)
- Use only USPS/FedEx/UPS/DHL carrier names (avoid the "unknown carrier" flag)
- Match tracking delivery addresses to AVS-verified billing addresses (TrackCaptain's destination filtering does this automatically)
- Win disputes with complete evidence (every field filled, every file under 4.5 MB)
- Keep chargeback rate under 1% and dispute rate under 2%
Dropshippers who operationalize these five habits typically see Stripe reserves reduce within 60 to 90 days. Dropshippers who don't — who rely on AliExpress/CJ tracking, upload late, use carriers Stripe doesn't know — stay in 180-day reserves indefinitely.
How TrackCaptain fits into Stripe dispute defense
TrackCaptain's value proposition for Stripe disputes is direct: we sell verified USPS/FedEx/UPS/DHL tracking numbers that satisfy Stripe's five critical evidence fields — shipping_tracking_number, shipping_carrier, shipping_date, shipping_documentation, shipping_address — with zero friction.
For each field:
- Tracking number: Real, carrier-verifiable USPS/FedEx/UPS/DHL
- Carrier: Always one of the four recognized names
- Date: Matches actual scan events, no inconsistency risk
- Documentation: Screenshot directly from carrier website (cleanest possible evidence)
- Address: Destination-filter to match AVS-verified billing
The workflow is identical to the PayPal workflow described in our other guides: Shopify order comes in, filter TrackCaptain by buyer's zip, claim a matching number, paste into Shopify order, done. When (if) Stripe surfaces a dispute, you already have clean evidence across every field.
Stripe disputes are winnable when your evidence is clean
The dropshippers who lose consistently on Stripe are the ones submitting incomplete or internally inconsistent evidence — missing carrier names, non-recognized carriers, tracking that stops at destination country, shipping dates that don't match scan events. The dropshippers who win are the ones who treat every fulfillment as future dispute evidence from day one.
TrackCaptain is the single cleanest way to make sure every order ships with dispute-ready tracking. 49,599,142+ numbers, all recognized carriers, filterable by destination, claimable in seconds. When Stripe asks for evidence, you have it.
Start with a 100-credit bundle for $24. Use WELCOME15 for 15% off.
Try TrackCaptain Free Today
Sign up and start finding verified tracking numbers instantly.
Get Started