> For the complete documentation index, see [llms.txt](https://plexo.gitbook.io/rest-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://plexo.gitbook.io/rest-api/merchant-configuration/merchant-management.md).

# Merchant Management Guide

This page describes the merchant operations that are relevant to the public REST API.

## Overview

The public documentation in this section is aimed at integrators who already have merchant access. Day-to-day merchant onboarding and administration are often handled outside this public API surface.

Use this guide for merchant discovery and merchant-scoped public endpoints. For payment-method configuration details and Gateway vs PayFac settings, use [Payment Methods Setup Guide](/rest-api/merchant-configuration/payment-methods-setup.md).

## What Is Outside This Public API Guide

The following areas are not documented here as public REST endpoints for external integrators:

* Merchant creation and hierarchy management
* Team and user administration
* API key generation or rotation workflows
* Merchant-wide callback configuration
* Settlement, bank-account, and security administration

Use the Plexo Dashboard or your Plexo contact for those operational tasks.

## Merchant Endpoints That Are Part of the Public Contract

Depending on your account permissions, the public spec documents merchant-scoped configuration and discovery endpoints such as:

* `GET /v1/merchants`
* `GET /v1/merchants/{merchantId}`
* `GET /v1/merchants/{merchantId}/payment-methods`
* `POST /v1/merchants/{merchantId}/payment-methods`
* `GET /v1/merchants/{merchantId}/payment-methods/{paymentMethodId}`
* `PUT /v1/merchants/{merchantId}/payment-methods/{paymentMethodId}`
* `DELETE /v1/merchants/{merchantId}/payment-methods/{paymentMethodId}`
* `GET /v1/merchants/{merchantId}/payment-methods/{paymentMethodId}/threeds`
* `POST /v1/merchants/{merchantId}/payment-methods/{paymentMethodId}/threeds`
* `PUT /v1/merchants/{merchantId}/payment-methods/{paymentMethodId}/threeds`
* `PUT /v1/merchants/{merchantId}/profile/logo`

## Merchant Profile Logo

Use `PUT /v1/merchants/{merchantId}/profile/logo` to upload the logo shown in hosted payer-facing experiences such as Payment Links. The request must be `multipart/form-data` with a `file` part.

Accepted content types are `image/png`, `image/jpeg`, and `image/webp`. SVG uploads are rejected. The response returns a CDN-backed `logoUrl`, `logoContentType`, and `logoUploadedAt`.

```bash
curl -X PUT "https://api.plexo.com.uy/v1/merchants/12345/profile/logo" \
  -u "YOUR_USERNAME:YOUR_PASSWORD" \
  -F "file=@logo.webp;type=image/webp"
```

## Typical Public Integration Workflow

1. Obtain your `merchantId` during onboarding
2. Confirm which payment methods and 3DS settings are enabled for that merchant
3. Use that `merchantId` in `POST /v1/payments` and `POST /v1/sessions`
4. Adjust payment-method or 3DS configuration only through the merchant endpoints that are exposed to your account

## Related Resources

* [Payment Methods Setup Guide](/rest-api/merchant-configuration/payment-methods-setup.md)
* [3D Secure Integration Guide](/rest-api/payments/3ds-integration.md)
* [Google Pay API Guide](/rest-api/wallets/google-pay/google-pay-api.md)
* [Apple Pay Guide](/rest-api/wallets/apple-pay.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://plexo.gitbook.io/rest-api/merchant-configuration/merchant-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.