Overview
A Transaction Type carries the field schema for a Transaction and not much else. Everything that happens when a Transaction is created happens in Workflows, which is why the implementation behind a Transaction Type is hard to see from the type itself and easy to read on its Platform Connections page.
Replicating an implementation for a new type
As an organization grows, it often needs to replicate a solution it already runs. A team launching a new Transaction Type commonly starts by replicating the implementation of an existing one, then makes small product-specific adjustments.
Connections is the shortcut for that. It lets you recall and rebuild an implementation without clicking through multiple screens or relying on memory, and it works even if you were not the person who built the original.
What the tabs show for a Transaction Type
Transaction Types have no Direct connections section on the Creates tab, because that section appears only for Workflows and Inquiry Templates. The sections you use are:
- Workflows, listing the Workflows this Transaction Type triggers.
- Downstream connections, listing what those Workflows create. For an API-first integration this is where the Verifications, Reports, and Cases that one Transaction sets in motion appear.
The Created By tab lists the upstream Workflows that can create a Transaction of this type, which a Workflow does with the Create Transaction step.
A Transaction created directly through the Create a Transaction API endpoint comes from your own system rather than from a Persona template, so for that integration path the Creates tab is the side worth reading. Creating a Transaction compares the two methods.
Types are not versioned
Connections is available for the latest published version of a template, and Transaction Types have no versions: a saved change to a type applies to new Transactions immediately, while existing Transactions stay associated with the type as it was configured when they were created. See Transaction Types and Change Management.