Direct answer

A client opened a PayPal dispute on your AI work. Here is the evidence PayPal actually asks sellers of services for.

PayPal disputes on services turn on one phrase in PayPal Seller Protection rules for intangible goods: compelling evidence that the item was delivered or the service was completed as described. Their own examples point at a system of record showing the date the work was sent and that it was received or accessed by the buyer. That is a delivery record, an acceptance record, and a communication trail, assembled inside the Resolution Center deadline. This page builds that packet.

Make the delivery exhibit checkable before you upload it: check any Zambo receipt free at zambo.dev/verify, with no signup. If the job ran through Zambo, its handover is the system of record PayPal describes, with the date and the result attached.

Updated October 24, 2026.

First, name the claim type and the deadline

Open the case in the Resolution Center and note the claim type and the date PayPal gives you to respond. The common types for service work are:

Item not received. The client says the work never arrived. Your answer is the delivery record: what was sent, on what date, to whom, and any record of receipt or access.
Unauthorized transaction. The client says they did not approve the payment. Your answer ties the client to the order: the agreement thread, the invoice, delivery to the client own address or accounts, and communications from the client about the work.
Significantly not as described. Note the hard limit first: PayPal Seller Protection, by its published terms, does not cover claims of this type. You can still respond in the case with the agreed scope beside the delivered output and the acceptance, but go in knowing the protection program is not standing behind this category.
A card chargeback instead of a PayPal claim. If the client went to their card issuer rather than to PayPal, the process and the reader change. That route is covered in Stripe chargeback evidence for AI work, and the packet logic is the same even when the platform is not Stripe.

The packet, in Resolution Center order

1. A short summary that uses PayPal language. State that the service was completed as described and delivered on a named date, and list the evidence that shows it. Reviewers process many cases; a summary that mirrors the test they apply is read first and best.

2. The agreement. Contract, statement of work, approved proposal, or the message thread where scope and price were agreed. This establishes what as described means for this job.

3. Proof of delivery from a system of record. This is the exhibit PayPal names for intangible goods: a record showing the date the work was sent and that it was received or accessed. The delivery email with its full date, the download or access record, and strongest of all a delivery record saved at handover time, with the result attached. The method is in prove I delivered the work and prove the client downloaded the files.

4. Proof of acceptance or use. The client approval reply, the recorded acceptance on the handover, or the work live in the client product, site, or campaign with its date. Acceptance converts delivery into completion as described.

5. The communication trail. Messages showing the client received, commented on, requested changes to, or used the work. A client who gave detailed feedback on Tuesday has a difficult item not received claim on Friday, and the trail is where that shows.

6. The invoice and payment match. The invoice for the exact amount, matching the PayPal transaction, with any earlier invoices this client paid through PayPal on the same terms.

Where the work record fits

Services and AI work share a weakness in PayPal cases: there is no parcel and no tracking number, so everything rides on records you kept. Zambo is the verifiable work layer for AI, and HANDOVER is its flagship product. A job run through Zambo saves the result of every call as it runs, and closes with a handover the client opens and accepts. That handover is a system of record in exactly PayPal sense: dated, tied to the work, and readable by a third party. Print it, upload it, and include the live link, because anyone can check the record at zambo.dev/verify and confirm the saved result was not changed after it was saved. The format under it is AER-1, an open Internet-Draft (draft-zambo-aer1-26), not a finalized standard.

If the client has not gone to PayPal yet and is only refusing to pay, you are one step earlier in the sequence: start with the demand letter with the evidence pack, which uses this same packet before any platform is involved.

Honest limits

PayPal decides its own cases under its own terms, which change, and Seller Protection has eligibility conditions and exclusions, including the not as described exclusion noted above and cases filed directly with a card issuer. Read the terms that apply to your account and your case, and treat this page as practical guidance for organizing evidence, not legal or financial advice.

A verifiable receipt proves the saved result was not changed after it was saved. It does not prove the work was good or worth the price. In an item not received case, the delivery and access facts are the dispute, and the record answers those. On quality, the packet leans on the agreed scope, the delivered output, and the acceptance, as it should.

Set up the record before you need it

Freelancers who get paid through PayPal for digital work should set the record up at delivery, not at dispute. Deliver through a handover, get the acceptance recorded, and keep the invoice and the handover link together. If a case ever opens, exhibits 3 and 4 are already the system of record PayPal asks for.

Work run through the Zambo MCP endpoint at zambo.dev/mcp (153 tools, 35 on the default surface) saves its result when the call runs and returns a verifiable AER-1 receipt (draft-zambo-aer1-26) for every call. In short, an agent receipt is a record of one ai agent tool call that anyone can check: it keeps the exact saved bytes and their sha-256 digest, and it proves the result was not changed since it was saved, not that it was right. Start free: 20 free calls per day, then they upgrade. The Day Pass is $0.99 for 24 hours. Checking any receipt is always free at zambo.dev/verify.

Questions, answered

What evidence does PayPal want for a services dispute?

In PayPal published Seller Protection terms for intangible goods, compelling evidence that the item was delivered or the service was completed as described. Their examples point to a system of record showing the date the item was sent and that it was either sent to the recipient address or received or accessed by the recipient. In practice: the agreement, a dated delivery record, an acceptance or use record, and the communication trail.

Does PayPal Seller Protection cover services and digital work?

It can, for eligible item not received and unauthorized transaction claims, when the seller provides the delivery or completion evidence and responds inside the required timeframes. It does not cover significantly not as described claims, or item not received claims the buyer files directly with their card issuer, under the published terms. Check the terms on your own account, because eligibility is case specific.

How long do I have to respond to a PayPal dispute?

PayPal sets the response date inside the case in the Resolution Center, and missing it can close the case in the client favor. There is also usually a window where the case is a dispute between you and the client before it escalates to a claim decided by PayPal. Use that window: one factual message to the client, then upload the full packet either way.

My client paid by PayPal and says they never got the files. What settles it?

The access record. If the files were delivered through a system that records the send date and the client access, upload that record with the delivery email and any messages where the client discusses the files. A download or access record from the delivery system answers the claim directly, which is why delivering through a recorded handover beats attaching files to an email.

Should I refund through PayPal to make the case go away?

For a small amount with thin evidence, sometimes. Weigh the packet first: if the delivery and acceptance exhibits are strong, respond and let PayPal decide. If delivery was never recorded anywhere, settling this case and fixing delivery for the next job is usually the honest arithmetic.

Start where the work starts: run the next job through zambo.dev/mcp, close it with a handover, and check any receipt free at zambo.dev/verify. If you only need a day, the Day Pass is at zambo.dev/day-pass.

Proof works best when it travels with the work itself. The AER-1 badge kit turns verifiable receipts into an embeddable badge for project pages, docs, and profiles, so anyone who sees the claim can reach the check in one click.