---
title: Connected accounts | API Docs
description: How Stripe Connect, direct charges, and merchant-of-record status work for Linq Agent Pay — and why refunds and disputes are yours.
---

Linq Agent Pay is built on **Stripe Connect**. You connect your own Stripe account once, and every payment settles **directly to it**. Linq orchestrates the request and the checkout but is never in the funds flow.

## Standard accounts and direct charges

Your connected account is a **Stripe Standard account**, and charges are created as **direct charges** on it. The practical consequence: **you are the merchant of record.**

That means the following are all yours, exactly as if you integrated Stripe directly:

- **The money.** Funds land in your Stripe balance and pay out on your own schedule. Linq never holds or touches them.
- **The customer relationship.** Statement descriptors, receipts, and payout timing are governed by your Stripe account settings.
- **Compliance and risk.** Your account’s verification, tax, and reporting obligations are yours.

Because it’s a Standard account, you also keep full access to your own Stripe Dashboard and can use the Stripe API on your account directly for anything beyond what this API covers.

## One-time setup

Connect your Stripe account once before you create your first payment request:

1. Open **Agent Pay** in your Linq dashboard: `https://zero.linqapp.com/organization/payments`.
2. Click **Connect Stripe** and complete Stripe’s onboarding — business details and a bank account for payouts.
3. Set a **display name** and **brand image**. These appear on the checkout page and on the App Clip card, and saving them also registers your [App Clip experience](/guides/payments/sending-payment-links#apple-pay-app-clip/index.md).

## Verification and `charges_enabled`

Creating a payment request requires your connected account to be able to accept charges (Stripe’s `charges_enabled`). Until it is, [creating a request](/api/resources/payment_requests/methods/create/index.md) returns `403`.

Onboarding usually flips this on immediately. Stripe may still run some verification in the background afterward — that’s expected, and **you can keep collecting payments while it finishes.** If Stripe ever needs more information, you’ll be prompted in your Stripe Dashboard.

## Refunds, disputes, and chargebacks are yours

Because charges settle directly to your Standard account, **Linq has no custody of the funds and cannot issue refunds or contest disputes on your behalf** — and there is deliberately no refund or dispute endpoint in this API.

Handle the money lifecycle after a payment succeeds in **your own Stripe Dashboard** (or via the Stripe API on your account):

- **Refunds** — issue full or partial refunds from the payment in your Stripe Dashboard.
- **Disputes / chargebacks** — these are raised against your account; respond to them in Stripe. The cardholder relationship and any dispute fees are between you and Stripe.

This is the flip side of being merchant of record: you keep the funds and the control, so you also own the post-payment lifecycle.

## Related

- [Agent Pay overview](/guides/payments/index.md) — the end-to-end flow.
- [Sending payment links](/guides/payments/sending-payment-links/index.md) — delivering the checkout link and Apple Pay App Clips.
- [Payment webhooks](/guides/payments/webhooks/index.md) — reconciling `succeeded`, `canceled`, and `expired` server-side.