> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/engineering-reference/db/tables/std_currencies.md).

# std\_currencies

{% hint style="info" %}
Generated from the staging database schema, with descriptions drafted by agents ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/db/tables/std_currencies.md).
{% endhint %}

## Description

Reference list of ISO currencies; snapfix\_supported marks the ones a package price may use.

<details>

<summary><strong>Table Definition</strong></summary>

```sql
CREATE TABLE `std_currencies` (
  `code` char(3) NOT NULL COMMENT 'Three-letter country code (ISO)',
  `name` varchar(255) NOT NULL COMMENT 'Currency name',
  `entity` varchar(255) NOT NULL COMMENT 'Entity name',
  `number` char(3) NOT NULL COMMENT 'Three number ISO code',
  `fund` tinyint NOT NULL DEFAULT '0' COMMENT 'Some currency codes are just used in the financial markets',
  `notes` varchar(5000) DEFAULT NULL COMMENT 'Notes field',
  `sort_order` int DEFAULT '1000',
  `sort_order_web` int DEFAULT '1000',
  `symbol` char(3) CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci DEFAULT NULL,
  `snapfix_supported` tinyint NOT NULL DEFAULT '0',
  PRIMARY KEY (`code`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1
```

</details>

## Columns

| Name               | Type          | Default | Nullable | Comment                                                           |
| ------------------ | ------------- | ------- | -------- | ----------------------------------------------------------------- |
| code               | char(3)       |         | false    | Three-letter country code (ISO)                                   |
| name               | varchar(255)  |         | false    | Currency name                                                     |
| entity             | varchar(255)  |         | false    | Entity name                                                       |
| number             | char(3)       |         | false    | Three number ISO code                                             |
| fund               | tinyint       | 0       | false    | Some currency codes are just used in the financial markets        |
| notes              | varchar(5000) |         | true     | Notes field                                                       |
| sort\_order        | int           | 1000    | true     |                                                                   |
| sort\_order\_web   | int           | 1000    | true     |                                                                   |
| symbol             | char(3)       |         | true     |                                                                   |
| snapfix\_supported | tinyint       | 0       | false    | 1 = allowed as a package price currency; 6 currencies on staging. |

## Viewpoints

| Name                                                                                  | Definition                                                                                                                                                                           |
| ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [billing](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-13.md)   | Plans and packages, the billing organisation (`tPri_Org`) with its Stripe, GoCardless, Xero and HubSpot deal records, in-app purchases, the paywall, support minutes and currencies. |
| [reference](https://docs.snapfix.com/engineering-reference/db/tables/viewpoint-22.md) | Code lists and standard data: the enum tables, countries, currencies, industry codes, defaults the apps download, and the API endpoint lists.                                        |

## Constraints

| Name    | Type        | Definition         |
| ------- | ----------- | ------------------ |
| PRIMARY | PRIMARY KEY | PRIMARY KEY (code) |

## Indexes

| Name    | Definition                     |
| ------- | ------------------------------ |
| PRIMARY | PRIMARY KEY (code) USING BTREE |

## Relations

```mermaid
erDiagram


"std_currencies" {
  char_3_ code PK
}
```

***

> Generated by [tbls](https://github.com/k1LoW/tbls)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/engineering-reference/db/tables/std_currencies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
