Stripe

Update a connected Stripe account

Updates a connected Stripe account; omitted fields keep their value.

Editable: name, series_id (null uses the company default series) and the per-account fiscal policy.
invoice_note (up to 500 characters) goes in auto-created invoices; null clears it.

patch/companies/{company}/connected-accounts/{account}

Request

Base URL: https://api.factuarea.com/v1
URL: https://api.factuarea.com/v1/companies/{company}/connected-accounts/{account}
Auth: one of:
- HTTP bearer
- API key in header X-API-Key

Path parameters

companystring uuid required

Public identifier (UUID v7) of the company. Get it from GET /v1/me (data.scope[].id).

accountstring uuid required

Public identifier (UUID v7) of the connected payment account.

Headers

Idempotency-Keystring required

Example:01928f10-7c0e-7c4a-9b7d-2f8a6e3c1d4b

Client-generated opaque key (up to 255 characters; UUID v7 recommended) that makes retries safe: the first response is cached and replayed for repeats without re-executing the mutation. Reusing a key with a different body returns 422 idempotency_key_reused; the values of secret fields (password, secret…) count as part of the body, so retrying with a corrected secret under the same key is a different request, never the replay of the earlier answer. See the Idempotency guide. Required on this operation: repeating it delivers an effect that cannot be taken back (an email sent, a file generated, a third-party call, a charge), so a request without this header is rejected with 422 idempotency_key_required before any business logic runs.

Factuarea-Versionstring date

Example:2026-06-01

Pin the API version (YYYY-MM-DD, Stripe-style date versioning) for this request; omit to use the key's pinned version, or the latest if none. Unsupported version → 400 unsupported_api_version; malformed → 400 parameter_invalid_format. The effective version is echoed in the Factuarea-Version response header. See the Versioning guide.

Request body

namestring

series_idstring nullable

simplified_threshold_centsinteger

autoinvoicing_enabledboolean

require_nifboolean

refunds_enabledboolean

subscription_autoinvoicing_enabledboolean

default_line_conceptstring nullable

invoice_notestring nullable

fee_expenses_enabledboolean

Turns on or off the monthly purchase expense that records the Stripe fees of this account (Stripe accounts only). Turning it on requires the purchases module of the plan and, once on, a fee_expenses_tax_treatment and a fee_expenses_since (sent in the same request or already stored). Turning it off keeps the stored treatment and month and the expenses already created.

fee_expenses_tax_treatmentstring

Tax treatment of the fee expense: reverse_charge_eu (intra-community purchase at 21 %, self-assessed) or exempt (0 %, exemption cause E1). Any other value is rejected with 422 parameter_invalid_value.

fee_expenses_sincestring

First month to record as a fee expense, as YYYY-MM. It cannot be later than the current month, and only closed months are recorded. A malformed or future month is rejected with 422 parameter_invalid_value.

Response

Example response

{
  "data": {
    "id": "0192e7c2-4d5e-7f3b-a012-3c4d5e6f7081",
    "object": "connected_account",
    "name": "Tienda principal",
    "external_account_id": "acct_1QabcDEF2ghIJklm",
    "external_account_name": "Tienda principal S.L.",
    "series_id": "0192e7b1-3c4d-7e2a-9f01-2b3c4d5e6f70",
    "simplified_threshold_cents": 40000,
    "refunds_enabled": true,
    "default_line_concept": "Cobro Stripe",
    "invoice_note": "Pago recibido. Gracias por su compra.",
    "connection_method": "account_links",
    "authorization_status": "authorized",
    "status": "active",
    "connected_at": "2026-06-15T10:30:00+00:00",
    "fee_expenses_tax_treatment": "reverse_charge_eu",
    "fee_expenses_since": "2026-01"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.