Source: https://docs.debitura.com/developer-concepts/environments

# Environments

Debitura does not provide a traditional test environment for most integrations. Instead, use the `IsTest` flag in production.

<a id="clients-and-collection-partners"></a>

## Clients and Collection Partners

There is **no separate test environment**. You integrate directly with production and use the [`IsTest` flag](https://docs.debitura.com/developer-concepts/test-cases.md) when creating cases.

Cases created with `IsTest: true`:

-   Go through full validation
-   Appear in your account
-   Do **not** trigger collection activity or communications

**Customer API:** test cases go through normal partner matching and may show an assigned `collectionPartner`, but no collection activity or real communications happen.

**Collection Partner API:** test cases are **self-assigned to the managing partner** (routing isolation). They never enter the global routing pipeline or appear on other partners' work queues. See [Test Cases](https://docs.debitura.com/developer-concepts/test-cases.md) for visibility opt-in details.

This approach means your test cases use the exact same validation and API behavior as real cases.

<a id="production-urls"></a>

### Production URLs

| API | Base URL |
| --- | --- |
| Customer API | `https://customer-api.debitura.com` |
| Collection Partner API | `https://collectionpartner-api.debitura.com` |

<a id="referral-partners"></a>

## Referral Partners

Referral partners are the exception. They receive access to a **dedicated test environment** with separate URLs, data isolation, and no real collection activity.

See [Referral Partner Environments](https://docs.debitura.com/referral-partners/getting-started/environments.md) for URLs and setup details.