> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.withpersona.com/2021-05-14/transaction-types/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.withpersona.com/_mcp/server.

# Transaction Types

## Overview

For each type of transaction, we can define a schema of what information gets passed in during creation. Each transaction type has a transaction type ID. Transaction Types consist of custom field schemas and custom statuses.

Transactions have support for the following field types:

* `Boolean`
* `Date`
* `Documents`
* `File`
* `Float`
* `Hash`
* `Integer`
* `String`
* `Multiple Choices`
* `Array`

## Archiving

Customers can archive both Transaction fields and Types, which enables updates in the event a user saves the wrong field key, or a customer's model changes over time. After a field is archived on a Transaction Type or a Transaction Type itself gets archived, all associated Workflows must get updated.

> Transaction Types define the shape of the user interaction within Persona's ecosystem.