“How do people pay in India?” and “Which providers support this payment method?” are both payments questions, but they need different starting points. The first begins with a market and its local mix. The second begins with a method and the businesses connected to it. Atlas is designed to let you enter through either route and keep following the subject.

The main search can take you to a record you already know. The Atlas menu gives you the collection views when you want to browse a category instead. A catalog is useful for finding candidates; a record page is where you inspect one subject in depth. Moving between the two is how a broad question becomes a specific investigation.

This is the browser view of the same connected information available through Graph. Hub adds tools for saving, comparing and analyzing it. You do not need to set up an API connection to explore Atlas.

Payments vocabulary often compresses several roles into one familiar brand name. A customer-facing method, a scheme’s rules and a clearing system can be closely connected without being interchangeable. Atlas keeps those subjects as separate records, with links between them.

That separation makes questions more precise. A card product page describes a particular offering from a bank. A payment-method page describes the broader way to pay. A PSP page describes services an organization provides. Follow the links when you need to move from the product someone uses to the institutions and infrastructure behind it.

A record begins with its name, identity and short description. The Aurato ID is a stable reference to that subject. The description helps you establish whether you have found the right thing before interpreting detailed fields or following a similarly named brand.

Next, read the headline facts and measurements. These are an overview, not a substitute for the sections underneath. Continue through the page to inspect capabilities, related records, historical views or product details relevant to that record type. A market and a card product do not need the same fields, so Atlas organizes their detail differently.

The breadcrumb takes you back to the collection. Linked names and record icons lead to related subjects. This is particularly useful when you arrive from search: the page can answer your immediate question while showing where to investigate next.

Open Markets and select India as a working example. Begin with the market context: population, GDP, GDP per capita and GDP growth help describe the scale and conditions around the payment ecosystem. Financial-access measures such as ATMs, bank branches and card ownership add a different perspective where observations are available.

The Payment Methods section shows the methods linked to the market, with available users, transactions and payment-volume measurements. Read these as different dimensions of scale. A high transaction count may reflect frequent small payments; a high value total may reflect fewer large payments. Neither tells you the full story on its own.

Schemes and Systems provide another view of the market. The scheme breakdown groups payment instruments; the system breakdown concerns payment infrastructure. Their scopes and source populations can differ, so read the labels and details before treating the two tables as parts of one common total. The market’s historical charts help you inspect how the recorded mix develops over time.

From the market page, open a method that matters to your question. The method record adds its own description, capabilities, market relationships and available historical measurements. This is where you investigate the practical meaning behind an entry in a country table.

Pay attention to what each connection establishes. Recorded availability in a market does not mean universal acceptance by merchants there. A provider’s support can also depend on the country and integration. Follow the related record and its supporting evidence if you need to establish a specific capability or local arrangement.

A method’s history gives you a way to distinguish its current scale from its trajectory. For a recurring review, saving the method is useful; saving an individual headline measurement can make a particular update easier to spot. Dashboard and the Measurements guide explain those tracking options.

If your next question concerns implementation, follow the providers associated with the method or market. A PSP’s services and coverage describe a different part of the ecosystem from the method’s consumer usage. Compare the relevant capabilities and recorded market scope rather than assuming a large provider supports every local payment arrangement.

For cards, follow the issuing bank and the actual product record. A network logo alone does not establish the annual fee, credit terms or insurance conditions of a bank’s card. Card pages give those product-level details a place of their own, while retaining routes back to the broader payment catalog.

Regulator, regulation and standard records can explain another layer: the authority overseeing an area, a framework applying to it, or a technical specification used in the infrastructure. Their role is context for the investigation; open the original publication when the exact wording or effective date matters.

Before comparing two figures, check the metric, unit, reference period and geography. Monthly users and registered accounts are different populations. A country observation and a global total answer different questions. Currency amounts need their currency and conversion basis. The Measurements guide gives a fuller explanation of these distinctions.

Some records have deeper coverage than others. An empty field means the detail is not available in that view; it should not become zero, “no” or proof that a service does not exist. The same care applies to relationships: absence from the recorded map can be a coverage gap.

Use charts to identify questions, then inspect the underlying record and evidence to answer them. An unexpected movement might be a new period, a revision or a change in methodology. Those explanations can produce very different conclusions from the same visual shape.

In a record’s Graph section, “Show all sources for …” opens Sources with that record selected. Follow a publication to read the original material, or use the registry’s search to find a particular report. This is the route from an overview back to the evidence behind it.

“Show all changes for …” opens the Changelog filtered to the record. It helps you identify substantive additions and revisions since a previous visit. Sources explain supporting evidence; Changes explain how Aurato’s published information develops. When you quote or reuse a finding, retaining both the record link and the relevant source makes the conclusion easier to revisit.

The percentages alongside these buttons describe completeness and freshness. Completeness concerns how much applicable information is filled; freshness relates to the record’s update age. Neither is a guarantee that every fact is correct or that an external publication describes the current month.

For a market review, choose one question narrow enough to answer. For example: identify the methods that matter in India, inspect how their measured usage differs, and explain the infrastructure behind one of them. Keep your notes tied to the records and periods you actually inspected.

Once you have a working set, use Dashboard to revisit it and Compare to inspect compatible records together. Open Workbench when you need a prepared dataset or a chart for further analysis. If the review becomes a recurring software workflow, Graph provides API and MCP access to the same subjects.

1. Find the market

   Open Markets, select the country and read its context before the method rankings.

2. Inspect a method

   Follow a linked method to its capabilities, market scope and available measurements.

3. Explain the connection

   Open the relevant provider, scheme, system or bank to understand its role.

4. Check the evidence

   Use the record’s Sources link and read the original publication for the claim you need.

5. Keep a route back

   Save the record or measurement, retain the period and source, and check Changes when you revisit it.