# Run Connect (https://docs.chargeflow.io/docs/platforms/connect)



You have a Connect account and you need to get merchants recovering. This section covers the Connect dashboard: what each area does and what you can do in it.

In one line: connect merchants, route their disputes automatically, Chargeflow wins the money back.

Connect runs as a dashboard that carries both your brand and Chargeflow's. Your merchants see your platform. The recovery engine runs underneath.

## Five steps to running [#five-steps-to-running]

<Steps>
  <Step>
    ## Set up your platform [#set-up-your-platform]

    Pick your platform name, brand colour, logo, and industry. A live preview shows how your brand pairs with Chargeflow in the co-branded header. Branding can change at any time from [Settings](https://docs.chargeflow.io/docs/platforms/connect/settings).
  </Step>

  <Step>
    ## Connect a payment processor [#connect-a-payment-processor]

    From [Integrations](https://docs.chargeflow.io/docs/platforms/connect/integrations), connect a PSP. The smart connection flow detects the merchants on that account and imports them, so you are not adding them by hand.
  </Step>

  <Step>
    ## Onboard your merchants [#onboard-your-merchants]

    Invite them to the co-branded portal, or activate them instantly. A Magic Link is copyable per merchant if you want to send the invite through your own channel. See [Merchants](https://docs.chargeflow.io/docs/platforms/connect/merchants).
  </Step>

  <Step>
    ## Let the engine work [#let-the-engine-work]

    Disputes flow in from connected processors and are scored, evidenced, and submitted automatically. Recovery performance builds up across [Merchants](https://docs.chargeflow.io/docs/platforms/connect/merchants) and [Disputes](https://docs.chargeflow.io/docs/platforms/connect/disputes).
  </Step>

  <Step>
    ## Optional: go API-first with EaaS [#optional-go-api-first-with-eaas]

    If you would rather load dispute data programmatically than connect a PSP, follow the eight-step [Evidence-as-a-Service setup](https://docs.chargeflow.io/docs/platforms/eaas/setup) instead of step 2.
  </Step>
</Steps>

## What Connect gives you [#what-connect-gives-you]

| Capability                                                     | Where                                                      |
| -------------------------------------------------------------- | ---------------------------------------------------------- |
| Onboard and manage merchants, track their recovery performance | [Merchants](https://docs.chargeflow.io/docs/platforms/connect/merchants)             |
| Every dispute across every merchant, with status and deadlines | [Disputes](https://docs.chargeflow.io/docs/platforms/connect/disputes)               |
| Connect processors so disputes route in automatically          | [Integrations](https://docs.chargeflow.io/docs/platforms/connect/integrations)       |
| Generate evidence over the API with no PSP connection          | [Evidence-as-a-Service](https://docs.chargeflow.io/docs/platforms/eaas/introduction) |
| Embed live dispute widgets in your own dashboard               | [Widgets](https://docs.chargeflow.io/docs/platforms/connect/widgets)                 |
| API keys, HMAC, webhooks                                       | [Developers](https://docs.chargeflow.io/docs/platforms/connect/developers)           |
| Branding, team, roles and permissions                          | [Settings](https://docs.chargeflow.io/docs/platforms/connect/settings)               |

## Next step [#next-step]

<Cards>
  <Card className="cf-card-outline" iconName="card-multi" title="Merchants" href="/docs/platforms/connect/merchants">
    Onboard the first merchant and watch the first dispute arrive.
  </Card>
</Cards>

Building against the API rather than the dashboard? Start at the [Platforms quickstart](https://docs.chargeflow.io/docs/platforms/quickstart).