> 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/getting-started/environments.md).

# API Environments

This guide provides complete information about Plexo API environments, including base URLs, purposes, and when to use each environment.

***

## Environment Overview

Plexo API provides three environments for different stages of integration and deployment:

| Environment    | Base URL                           | Purpose                 | Use For                              |
| -------------- | ---------------------------------- | ----------------------- | ------------------------------------ |
| **Production** | `https://api.plexo.com.uy`         | Live payment processing | Real transactions with real money    |
| **Testing**    | `https://api.testing.plexo.com.uy` | Integration testing     | Testing integrations with test cards |

***

## Production Environment

**Base URL**: `https://api.plexo.com.uy`

**Purpose**: Live payment processing with real transactions and real money.

**Use Cases**:

* Processing real customer payments
* Production merchant integrations
* Live e-commerce transactions
* Production mobile apps and websites

**Characteristics**:

* ✅ Real card processing
* ✅ Real money transfers
* ✅ PCI DSS Level 1 compliant
* ✅ 99.9% uptime SLA
* ✅ 24/7 monitoring and support
* ⚠️ All transactions are final and billable

{% hint style="danger" %}
**Production Environment**: All transactions in production are real and will result in actual money transfers. Use test environment for development and testing.
{% endhint %}

***

## Testing Environment

**Base URL**: `https://api.testing.plexo.com.uy`

**Purpose**: Safe environment for integration testing without financial risk.

**Use Cases**:

* Integration development and testing
* Learning the API
* Testing error scenarios
* Validating integration logic
* QA and automated testing

**Characteristics**:

* ✅ Test card numbers accepted
* ✅ No real money processed
* ✅ Same API structure as production
* ✅ Realistic test data
* ✅ Safe for experimentation
* ℹ️ May have occasional downtime for updates

**Example Request**:

```bash
curl -X GET "https://api.testing.plexo.com.uy/v1/merchants/123" \
  -u "test-username:test-password" \
  -H "Content-Type: application/json"
```

{% hint style="success" %}
**Recommended for Development**: Use the testing environment for all integration development and testing. It's safe, free, and mirrors production behavior.
{% endhint %}

***

**Last Updated**: 2025-12-11 **API Version**: v1

***


---

# 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:

```
GET https://plexo.gitbook.io/rest-api/getting-started/environments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.