Use Pingpong to review a draft or format a PDF within your own Stripe dispute workflow. Your integration remains responsible for collecting records and submitting the response to Stripe.
Keep the steps separate
- Read the Stripe dispute, claim, status and due date using your authorized integration.
- Gather transaction records and prepare a response to the actual claim.
- Optionally ask the Pingpong review API to examine the draft for gaps. Verify any suggested changes.
- Send approved text to the PDF formatter if a PDF is useful for your submission.
- Upload the required evidence to Stripe, then confirm submission using Stripe’s own response and status.
What to store
Keep the Stripe dispute ID, source record references, approved response, generated file and submission confirmation together. Save the exact version submitted. Avoid treating a generated PDF or an AI response as proof that Stripe received the evidence.
Access and limits
The PDF endpoint uses eligible business API keys and account quotas. A web Plus or Pro review subscription does not provide PDF API entitlement. The PDF API documentation lists its fields and error responses.
Stripe submission requirements
Stripe provides its own dispute APIs and evidence fields. Follow that contract for file upload and final submission; a Pingpong request never replaces a Stripe API call. Read the current Stripe documentation before implementing retries or an automated submission.