Chatarmin CX creates one inbox ticket per PayPal dispute automatically.
When to use it
Use PayPal when you accept PayPal payments and your support team regularly handles:- chargebacks and payment disputes
- buyer claims about items not received or not as described
- evidence deadlines and offers before a case escalates
How dispute tickets work
When a dispute is created or updated on a connected PayPal account, cx indexes it and — if it has a buyer email and doesn’t already have a ticket — creates one automatically:- Channel — the ticket lands on your PayPal channel, separate from your other conversations.
- Contact — cx finds or creates a contact using the buyer’s email address.
- Subject — the ticket subject follows the pattern
PayPal dispute — {reason} — {amount}. - Tags — the ticket is tagged
disputeandpaypalso you can build views, routing rules, or AI Agent triggers around it. - Status — the ticket opens as open, or resolved if the dispute was already closed when it first synced. When PayPal later marks the dispute resolved, cx updates the ticket to resolved automatically.
Set up PayPal
You need a PayPal REST app with Disputes enabled. Create or open the app in the PayPal Developer Dashboard.1
Open integrations
Open integrations from your workspace settings and choose PayPal.If PayPal is not listed, contact your Chatarmin CX account team to enable it for your workspace.
2
Connect an account
Click Connect, enter an optional display name (helpful when you connect more than one merchant account), then paste the Client ID and Client Secret from your REST app.
3
Connect additional accounts (optional)
Repeat Connect for each PayPal merchant account your team manages. Each account syncs its own disputes.
Use PayPal in the inbox
Every PayPal dispute has its own ticket in your PayPal channel, and the same dispute also surfaces in the customer panel of any other ticket for that contact.- Open the dispute’s ticket in your PayPal channel, or open any other ticket whose contact shares the buyer’s email address.
- In the customer panel, find the Disputes section listing that dispute alongside any other cases for the same contact.
- Click a dispute to open the detail sheet with case status, amount, timeline, messages, and evidence requests.
- Use Respond to dispute to take the actions PayPal allows for that case state — for example send a message, make an offer, provide evidence, escalate, accept a claim, appeal, or acknowledge a returned item.
- Use Open in PayPal Resolution Center when you need the full PayPal UI.
How disputes stay up to date
cx indexes disputes from PayPal when they are created or updated. A background sync also runs every few hours to pick up cases that changed outside cx. After you act on a dispute in cx, the case refreshes automatically.Matching disputes to contacts
Disputes are linked by buyer email. The contact’s primary email and any other email identifiers on the contact are used for matching.Inbox dispute actions
Available actions depend on the dispute’s current state. PayPal controls which responses are allowed at each stage.Evidence files
When PayPal requests evidence, you can attach files from your computer when submitting from the inbox. Supported formats are PDF, PNG, JPG, and GIF. Each file can be up to 10 MB, with a 50 MB total per request. Notes are limited to 2,000 characters.AI Agent actions
Give an AI Agent PayPal actions when you want automation to look up disputes or draft responses on dispute-related tickets. The agent must run on a ticket with a contact that has an email address. Connect PayPal first, then enable actions on the agent and select which connected PayPal account(s) the agent may use.Read actions
- List PayPal disputes — Find indexed disputes for the ticket contact’s email.
- Get PayPal dispute — Load full live dispute detail before taking a write action. Always use this after listing disputes.
Write actions
- Send message — Reply in the dispute thread.
- Make offer — Propose a resolution.
- Provide evidence — Submit evidence and optional attachments from customer messages on the ticket.
- Escalate — Escalate to claim when allowed.
- Accept claim — Accept the dispute loss.
- Appeal — File an appeal when allowed.
- Acknowledge returned item — Confirm receipt of a return.
Best practices
- Always copy the Client ID and Client Secret from your app’s Live tab in the PayPal Developer Dashboard — cx has no sandbox option, so Sandbox credentials will not work.
- Keep the contact email aligned with the email the customer used on PayPal. Update the contact if they wrote from a different address.
- Use display names when you connect multiple PayPal accounts so agents and AI Agents pick the right integration.
- Set up a view or routing rule for your PayPal channel so new dispute tickets reach the right queue automatically.
- Require approval on money-moving actions until you trust the agent’s dispute playbook.
- For complex cases, use cx for context and the Resolution Center link when PayPal-only steps are required.
Troubleshooting
Connection test fails
- Confirm the REST app has Disputes enabled in the PayPal Developer Dashboard.
- Confirm the Client ID and Client Secret are from your app’s Live tab, not Sandbox — cx always authenticates against PayPal’s live API.
- Rotate the secret in PayPal if it was revoked, then update the integration in cx.
No disputes for a customer
- Verify the contact email matches the buyer email on the PayPal dispute.
- Allow time for indexing after connect — new and updated disputes sync automatically; the periodic reconcile can take up to a few hours for edge cases.
- Confirm the dispute belongs to a PayPal account you connected in this workspace.
- Confirm you connected with Live credentials, not Sandbox — Sandbox credentials fail to authenticate against PayPal’s live API, so disputes never sync.
No ticket for a dispute
- A dispute needs a buyer email before cx can create its ticket. The ticket appears automatically as soon as PayPal reports one.
- Check whether the dispute is already linked to another ticket — cx reuses an existing ticket instead of creating a duplicate.