Handle payment reports as tickets
Turn disputes, failed payments and failed refunds into Uppo tickets. Signed webhooks and idempotent event handling.
Status
Available. The connector is switched on from the Uppo panel, company by company. It is not a finance dashboard inside the ticket: it is the guarantee that a payment problem does not sit in a console nobody watches.
What it exchanges
From Stripe to Uppo, the events that deserve a support response:
- Dispute opened on a charge (
charge.dispute.created) - Early fraud warning from Stripe Radar
- Payment under review
- Invoice payment failed
- Payout failed
- Refund failed — only when it actually fails, not on every refund
When the same matter is settled in Stripe (dispute closed, review closed), the linked ticket is closed accordingly. Where Stripe supplies the customer email, the ticket is created in their name.
Direction of the flow
Inbound only, from Stripe to Uppo. Uppo writes nothing to Stripe: it does not issue refunds, close disputes or change payments.
Authentication and permissions
The webhook has a signing secret per company: every incoming call is verified before it is interpreted, and an invalid signature is rejected. No secret is shared between different customers.
Each event is identified by the id of the Stripe object, so opening and closing land on the same ticket. If Stripe redelivers the event, the ticket is not created twice.
Prerequisites
- A Stripe account and permission to configure a webhook endpoint on it
- The endpoint and the signing secret come from the Uppo panel and are pasted into Stripe
Known limits
- The agent panel does not show transaction history, subscriptions or customer value
- The events handled are the ones listed above: other Stripe events do not open tickets
- An event that arrives while the connection is switched off is not recovered afterwards
If you need more
For events the connector does not cover there is still the signed incoming webhook, which accepts whatever event you want to send it, and Uppo's public API to open and update tickets from a service of your own. Base URL, authentication and endpoints are on the developers page.
Card
- Category
- Payments
- Updated
- 3 Sept 2026
See also
Fatture in Cloud
Bring the customer records that live in your accounting software next to the ticket, so whoever replies knows who they are talking to without opening another application.
GitHub
Link an Uppo ticket to a GitHub issue: opening, comments and closing travel both ways, over a webhook signed per company.
Slack
Send Slack notifications from Uppo about assignments, mentions and ticket activity. The flow is outbound only: replies stay in Uppo.
Trello
Attach a Trello card to the ticket and work on it from the Uppo panel: title, status and comments stay aligned without changing window.
See the integration on your own case
Configure the connector during your free trial and check its flow, permissions and limits with test data.