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

# Policy enforcement

> Two ways to constrain who may fulfill a payment.

## Overview

Two different policy-enforcement levers: defined by different participants, but applied by Atum.

A **credential type** names *what* was attested about someone, not *who* they are — for example [Known to Atum](/get-started/identity/credentials#known-to-atum), the type Atum issues today. See [types today](/get-started/identity/credentials#types-today).

|                     | By identity                                                                                                      | By credential type                                                                                |
| ------------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- |
| **Who sets**        | You, on each [payment request](/get-started/concepts/payment-intent#settlement-providers-on-this-payment)        | Atum, for your environment                                                                        |
| **Who applies**     | Atum                                                                                                             | Atum                                                                                              |
| **What it matches** | Named [settlement provider](/get-started/reference/glossary#settlement-provider) identities                      | [Credential types](/get-started/identity/credentials#types-today) and trusted issuers             |
| **Scope**           | The payment                                                                                                      | Your environment                                                                                  |
| **Today**           | Available as [`settler_requirements`](/get-started/concepts/payment-intent#settlement-providers-on-this-payment) | Atum configures which types and issuers to trust. You cannot yet require a type of the other side |

## Related concepts

* **[Payment request](/get-started/concepts/payment-intent)** — the object you submit to start a payment. The identity list is an optional field on it ([`settler_requirements`](/get-started/concepts/payment-intent#settlement-providers-on-this-payment)).
* **[Credentials](/get-started/identity/credentials)** — signed facts about a participant. Atum trusts types and issuers from its own list.
* **[Authorization and counterparties](/get-started/concepts/authorization-and-counterparties)** — recipient consent. A separate step, not a third column of this table.

The credential-type column is available today as Atum-side configuration: which types a perimeter requires, and which issuers it trusts. You attach those credentials; Atum verifies them.

## Next steps

<CardGroup cols={2}>
  <Card title="Payment request" icon="file-invoice" href="/get-started/concepts/payment-intent">
    What you submit to start a payment
  </Card>

  <Card title="Credentials" icon="id-card" href="/get-started/identity/credentials">
    Known to Atum and third-party types
  </Card>

  <Card title="Who owns what" icon="table" href="/get-started/support/who-owns-what">
    You set the identity list; Atum applies both levers
  </Card>

  <Card title="Authorization and counterparties" icon="handshake" href="/get-started/concepts/authorization-and-counterparties">
    Recipient consent — a different step
  </Card>
</CardGroup>