# Widgets (https://docs.chargeflow.io/docs/platforms/connect/widgets)



Widgets put live dispute data inside your product, so a merchant sees their disputes where they already work instead of in a second tool.

<Callout title="Beta">
  Widgets are in beta. Availability is set per platform by your Chargeflow account manager, and the
  catalog is still growing. See [Support](https://docs.chargeflow.io/docs/reference/support) to get access.
</Callout>

## What you get [#what-you-get]

* **Widget catalog.** Pre-built components that display real-time dispute data: counts, statuses, deadlines, recovery performance.
* **Dashboard builder.** Assemble your own view from those components rather than taking a fixed layout.

Widgets read the same data as the [Disputes](https://docs.chargeflow.io/docs/platforms/connect/disputes) screen, scoped to the merchant viewing them.

## When to use a widget instead of the API [#when-to-use-a-widget-instead-of-the-api]

| Use a widget                                                 | Use the API                                                    |
| ------------------------------------------------------------ | -------------------------------------------------------------- |
| You want dispute data visible in your product this sprint    | You need the data inside your own components and design system |
| The standard dispute views are close enough to what you need | You are building a workflow, not a display                     |
| You would rather not maintain the rendering                  | You already have a dashboard framework                         |

Both read the same engine, so starting with widgets and moving to the API later does not mean re-onboarding merchants.

## Next step [#next-step]

<Cards>
  <Card className="cf-card-outline" iconName="card-add-layer" title="Developers" href="/docs/platforms/connect/developers">
    API keys, HMAC, and the webhook endpoints the widget fires from.
  </Card>
</Cards>