> For the complete documentation index, see [llms.txt](https://docs.feedb2b.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feedb2b.com/guides/markets-bets-and-settlements-mapping.md).

# Markets, Bets & Settlements Mapping

Different providers often use different names, identifiers, and structures for the same betting markets and outcomes.

FeedB2B maps provider-specific markets, bets, and settlement values into a unified structure, allowing you to work with multiple providers through the same integration.

### Market Mapping

The same betting market may have different names or identifiers across providers.

For example, one provider may use **Match Result**, another **1X2**, while another may use its own internal market name and ID.

FeedB2B maps corresponding provider markets to a common FeedB2B market type.

This allows your platform to recognize the same market regardless of which provider supplies it.

#### Example

| Provider   | Provider Market    | FeedB2B Market |
| ---------- | ------------------ | -------------- |
| Provider A | Match Result       | 1X2            |
| Provider B | Full Time Result   | 1X2            |
| Provider C | Match Winner 3-Way | 1X2            |

### Bet Name Mapping

Bet and outcome names can also differ between providers.

FeedB2B maps provider-specific bet names to a consistent FeedB2B structure.

For example:

| Provider   | Provider Bet Name | FeedB2B Bet Name |
| ---------- | ----------------- | ---------------- |
| Provider A | Home              | Home             |
| Provider B | Team 1            | Home             |
| Provider C | 1                 | Home             |

The same approach is used for other common outcomes such as **Away**, **Draw**, **Over**, **Under**, **Yes**, and **No**.

For markets containing dynamic values, such as totals or handicaps, FeedB2B uses market parameters to preserve the relevant value while keeping the market and bet structure consistent.

### Settlement Mapping

Providers may also represent settlement results differently.

FeedB2B maps provider-specific settlement values into a common settlement structure so that the same settlement status has the same meaning regardless of the provider.

Typical settlement results may include:

* Win
* Lose
* Void
* Half Win
* Half Lose

This allows your settlement processing to follow the same logic across supported providers instead of implementing separate settlement handling for every provider.

### Why Mapping Matters

Without mapping, integrating another provider may require implementing its market taxonomy, bet naming conventions, parameters, and settlement logic separately.

FeedB2B handles these differences within the platform.

This allows you to:

* Use consistent market types across providers
* Process bets and outcomes using the same structure
* Apply consistent settlement handling
* Reduce provider-specific logic in your platform
* Add or switch providers with significantly less implementation work

### Provider Differences

Mapping creates a common structure, but it does not make the underlying provider feeds identical.

Providers may still differ in:

* Available markets
* Market parameters and lines
* Odds
* Market suspension behavior
* Settlement timing
* Available settlement information

A market available from one provider may not be available from another provider for the same event.

### Mapping Coverage

FeedB2B continuously maintains and expands its mappings as new providers, sports, and market types are added.

If a provider introduces a market or bet type that does not yet have a corresponding FeedB2B mapping, it may require additional mapping before it can be represented through the unified structure.

### Next Steps

Continue to the **Glossary** section to understand how events, markets, bets, outcomes, and their relationships are represented in FeedB2B.

For exact identifiers, fields, and settlement values, see the **API Documentation**.