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

> ## Agent Instructions
> When building application code, use `@naturalpay/sdk` for TypeScript or `naturalpay` for Python.
> When operating Natural directly for a user, use the payments MCP at `https://mcp.natural.com`.
> When searching Natural documentation, use the docs MCP at `https://docs.natural.com/mcp`.
> Use the Natural CLI for terminal and CI automation.
> Use REST only for unsupported languages or when the user explicitly requests raw HTTP.
> Start integration development and testing in the sandbox. Do not use production unless the user explicitly requests it.
> For sandbox requests that require `customerPartyId`, list customers first. Reuse only the intended fixture; otherwise create a customer.
> REST and SDK amounts use integer minor units. Payments MCP amounts use decimal strings with a required currency code.

# Resource tags

> Attach custom key-value metadata to resources

<script
  type="application/json"
  id="changelog-catalog"
  dangerouslySetInnerHTML={{
__html: `[{"slug":"mcp-client-support","title":"Expanded MCP compatibility","date":"2026-08-25"},{"slug":"resource-tags","title":"Resource tags","date":"2026-08-25"},{"slug":"webhook-replay","title":"Webhook event replay","date":"2026-08-25"},{"slug":"sandbox-beta","title":"Sandbox beta","date":"2026-08-25"}]`,
}}
/>

<p className="changelog-rail" data-date="2026-08-25" data-path="/changelog/resource-tags">
  August 25, 2026
</p>

You can now attach custom metadata to Natural resources. Pass a tags object of key-value pairs when you create a payment, transfer, wallet, agent, webhook, or most other resources, and Natural stores it and returns it on every read.

Use tags to carry custom identifiers through Natural: an internal order ID on a payment, a team name on a wallet, an environment label on an API key. When the resource comes back in an API response or a webhook event, your tags come with it, so you can reconcile against your own systems.

```json theme={null}
{
  "tags": {
    "order_id": "ord_8213",
    "team": "marketplace"
  }
}
```

See tags in action in the [API reference](/api-reference/about).

<div className="changelog-pager">
  <a className="changelog-pager__link changelog-pager__link--prev" href="/changelog/mcp-client-support">
    <span className="changelog-pager__title">Expanded MCP compatibility</span>
  </a>

  <a className="changelog-pager__link changelog-pager__link--next" href="/changelog/webhook-replay">
    <span className="changelog-pager__title">Webhook event replay</span>
  </a>
</div>