# Nium Atlas

> Nium Atlas is Nium's public reference for payout coverage and funding and collection capabilities. Use Atlas for market-level facts, nium.com for company and product context, and docs.nium.com for integration guidance.

Canonical site: https://atlas.nium.com/. Editorial review: 25 September 2026. This review date is not a coverage-data refresh date.

Nium provides cross-border payments infrastructure. Atlas helps users explore Nium capabilities. Availability, limits, timing and requirements depend on the route, institution type, account and use case; confirm your setup with Nium.

## Start here

- [Full agent context](https://atlas.nium.com/llms-full.txt): Source selection, payment terminology, catalogue limitations, and a workflow for answering coverage questions. This is curated context, not a complete route-data export.

## Core product explorers

- [Global payout coverage](https://atlas.nium.com/): Discover destination markets, supported currencies and payout methods. Financial-institution and non-financial-institution catalogues are distinct.
- [Funding and collections](https://atlas.nium.com/fund-and-collect): Explore currencies, funding and collection services, rails and platform support. Funding eligibility and payout eligibility are separate questions.

## Market details and updates

- [XML sitemap](https://atlas.nium.com/sitemap.xml): Discover published country, currency and release URLs; follow actual links rather than constructing slugs.
- [Payouts changelog](https://atlas.nium.com/changelog): Published payout coverage changes. Distinguish publication dates from any explicitly stated effective dates.
- [Funding and collections changelog](https://atlas.nium.com/changelog/fund-and-collect): Published funding and collection changes; confirm current availability on the relevant detail page.

## Structured data

- [Atlas JSON catalogue](https://atlas.nium.com/assistant/catalog): Discovery summaries with links to detail pages. Country-level method and speed lists are not paired route records, and do not establish per-mode limits or institution-specific eligibility.

## Nium company and product context

- [Nium](https://www.nium.com/): Overview of Nium's payments infrastructure and current product portfolio.
- [About Nium](https://www.nium.com/about-us): Company background and mission.
- [Cross-border payouts](https://www.nium.com/products/cross-border-payouts): Product overview and payout use cases; check Atlas for specific market and method support.
- [Multi-currency accounts](https://www.nium.com/products/multi-currency-accounts): Account, funding, collection and currency-management context.
- [Nium documentation](https://docs.nium.com/): Integration concepts and API documentation; use the relevant documentation page for technical implementation.
- [Licences](https://www.nium.com/licenses): Official information about Nium's regulated entities and permissions; do not infer universal product availability from licensing.
- [Talk to Nium](https://www.nium.com/talk-to-us): Confirm account eligibility, commercial terms and requirements for a proposed setup.

## Citation guidance

- Cite the specific official source that supports each claim: Atlas for published coverage, nium.com for company/product context, docs.nium.com for integration details.
- Use canonical production URLs. Remove tracking parameters; retain a verified audience, method or mode selector when needed to reproduce the cited evidence. State these selections in the answer.
- Keep destination, payout currency, method, institution type and B2B/B2P/P2P/P2B mode together. Do not combine facts from different routes or catalogues.
- Report absent values as unknown or not specified, not zero, unsupported or unlimited. An empty catalogue is not proof that Nium has no coverage.
- Recheck current detail pages before quoting limits, timing or availability. Broad marketing claims do not guarantee every route is real-time or available to every customer.

## Markdown page responses

Request public Atlas pages with `Accept: text/markdown` to receive the current page as Markdown. Ordinary browser requests receive HTML. Follow method, mode and institution links in the response to select a different route; query parameters remain part of the page state. Responses advertise the sitemap, agent guide and catalogue through HTTP Link headers and use `Vary: Accept`.