> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bango.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Eligibility overview

> Understand how DVM supports checking whether a consumer can see, take up, and be provisioned with an Offer.

Eligibility lets Partners (reseller and content provider roles) determine whether a consumer can see, take up, and be provisioned with an Offer.

DVM supports eligibility checks at different stages of the consumer journey. Each check answers a different question and can apply different eligibility rules.

<Note>
  Eligibility is available through DVM APIs and does not depend on using DVM Consumer Experience.
</Note>

## The three types of eligibility

<CardGroup cols={3}>
  <Card title="Offer eligibility" icon="tags">
    Checks whether an Offer should be available to a consumer during offer discovery.
  </Card>

  <Card title="Purchase or redemption eligibility" icon="cart-circle-check">
    Checks whether a consumer can take up the selected Offer before provisioning continues.
  </Card>

  <Card title="Content Provider eligibility" icon="box-open-full">
    Checks whether the Content Provider will accept the consumer for the requested product or benefit before the Entitlement is created.
  </Card>
</CardGroup>

### Offer eligibility

**Should this Offer be available to this consumer?**

Offer eligibility is checked while the consumer is discovering Offers, before they choose one.

The result lets a Reseller decide how to treat an Offer in its consumer journey. For example, the Reseller can show the Offer normally, explain why it is unavailable, or give the consumer another route to become eligible, such as upgrading their mobile plan.

### Purchase or redemption eligibility

**Can this consumer take up this Offer now?**

Purchase or redemption eligibility is checked when the consumer attempts to purchase or redeem an Offer.

This provides an eligibility decision for the selected Offer before provisioning continues.

### Content Provider eligibility

**Will the Content Provider accept this consumer for the requested product or benefit?**

Content Provider eligibility is checked during provisioning, before the Entitlement is created.

A Content Provider can apply its own rules. For example, the consumer might already have a direct subscription that cannot be transferred, or might not qualify for a benefit such as a free trial.

## Where eligibility happens

```mermaid theme={null}
flowchart LR
    A[Discover Offers] --> B[Offer eligibility]
    B --> C[Select Offer]
    C --> D[Purchase or redemption eligibility]
    D --> E[Create Consumer Offer]
    E --> F[Content Provider eligibility]
    F --> G[Provision Entitlement]
```

The checks happen at different points because they serve different purposes. An Offer may be appropriate to show during discovery but still require a fresh eligibility decision when the consumer takes it up. The Content Provider can then apply its own eligibility rules before accepting the consumer.

## Who determines eligibility?

| Check | Eligibility decision |
| - | - |
| Offer eligibility | Reseller eligibility rules |
| Purchase or redemption eligibility | Reseller eligibility rules |
| Content eligibility | Content Provider eligibility rules |

DVM coordinates the eligibility flow and returns the relevant result to the requesting system.

## What happens when a consumer is not eligible?

An eligibility result lets the Reseller decide what should happen next in its consumer journey.

A consumer who is not currently eligible might be shown an explanation, offered another action that could make them eligible, or prevented from continuing with the selected Offer.

Eligibility is part of the consumer journey rather than simply an API success or failure.

## What's next?

<CardGroup cols={2}>
  <Card title="Check consumer eligibility" icon="user-check" href="/eligibility/check-consumer-eligibility">
    Learn when to perform each eligibility check and how to use the result.
  </Card>

  <Card title="Eligibility API" icon="rectangle-api" href="/api-reference/eligibility/check-user-eligibility">
    View the eligibility API operation, request fields, and response model.
  </Card>
</CardGroup>
