---
title: "Update an acquirer connection"
method: PATCH
path: "/merchants/{username}/acquirers/{conn_id}"
tags: ["Acquirer connections"]
---

# Update an acquirer connection

`PATCH /merchants/{username}/acquirers/{conn_id}`

## Request

- Base URL: `https://gateway.pmnts.io/v2/partners`
- URL: `https://gateway.pmnts.io/v2/partners/merchants/{username}/acquirers/{conn_id}`
- Auth: HTTP basic

Patches the mutable fields only: `priority`, `currencies`,
`card_types`. Changing `currencies` / `card_types` re-evaluates which
underlying processors stay active. `card_types` is narrowed to each
processor's routable set, so a PATCH can't enable a scheme the acquirer
can't settle. The `acquirer` and the MID/TID (`merchant_id` /
`terminal_id`) are immutable once the connection exists.

## Request body

- AcquirerConnectionUpdateRequest: Only `priority`, `currencies` and `card_types` are mutable. Changing `currencies` / `card_types` re-evaluates which underlying processors stay active. The `acquirer` and the MID/TID are immutable.
  - `priority` integer
  - `currencies` string[]
  - `card_types` string[]: Narrowed to the acquirer's routable set; schemes the acquirer can't settle are dropped rather than applied.

## Response `200`

The updated connection.

- AcquirerConnection: The combined state across every acquirer link provisioned for one acquirer. Boarding is synchronous, so a connection that exists is always boarded.
  - `acquirer_name` string, nullable, required: The acquirer's display name (e.g. `NAB`).
  - `merchant_id` string, nullable: The acquirer-assigned MID (e.g. `ent_a1b2c3d4`).
  - `terminal_id` string, nullable: The acquirer-assigned TID (e.g. `T0001`), or a Fat Zebra-generated 8-character placeholder (e.g. `ACMEC001`) if none was supplied at board time. Immutable once set.
  - `currencies` string[]: Currencies the connection can transact.
  - `schemes` string[]: Networks the merchant can transact for this acquirer.
  - `modes` string[]: Transaction modes the connection supports.
  - `wallets` string[]: Wallets the connection accepts.
  - `three_ds_enabled` boolean: Whether a boarded processor for this acquirer supports 3DS.
  - `status` 'enabled' | 'disabled', required: Routing toggle across the underlying links — disable to turn the connection off without deleting it.

## Other responses

- `401`: Missing or invalid HTTP Basic credentials.
- `404`: Resource not found.
- `422`: The request couldn't be completed. A `validation_error` is something the caller can fix — a bad payload, a merchant that failed validation, or a processor rejecting a field (e.g. the MID); the reason is in `fields`, keyed by a processor-agnostic field name. A `processor_error` is an unactionable upstream failure (a processor was unreachable, busy, or errored); `fields` is empty and the caller should retry or escalate. Raw upstream detail is never surfaced here — only a parsed, processor-neutral reason.

---

[API](https://skmtc.dev/fatzebra/apis/fat-zebra-partner-api.md) - [All operations](https://skmtc.dev/fatzebra/apis/fat-zebra-partner-api/llms.txt) - [OpenAPI document](https://skmtc.dev/fatzebra/apis/fat-zebra-partner-api/revisions/10f1181ea916?raw)