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

# TPA

> The TPA model — Transaction Processing Authorization, the company-level legal agreement that allows card data to flow to your EMS via OpenCard.

**TPA** = **Transaction Processing Authorization**.

It is the legal agreement between a **client company** and OpenCard that card transaction data from a specific **payment product** may flow to your EMS. Without a signed and activated TPA, no transactions are delivered for that client and product combination.

***

## What it represents

| Concept               | Meaning                                                                 |
| --------------------- | ----------------------------------------------------------------------- |
| **Who consents**      | The client company — authorized signatories (CEO, board, etc.)          |
| **What they approve** | Card data from a given payment product may pass through OpenCard to you |
| **Scope**             | One TPA per **client company + payment product** pair                   |
| **Audience**          | Company level — not the individual cardholder                           |

The individual employee signs a separate document — [PDPC](/ems/eid-signing) — when they onboard as a [card holder](/ems/model/card-holder). TPA is the company saying yes; PDPC is the person saying yes.

***

## Lifecycle

| Status               | Meaning                           |
| -------------------- | --------------------------------- |
| `pending-signatures` | Signatories added, not all signed |
| `pending-activation` | Waiting for TPA to be confirmed   |
| `activated`          | Live — transactions can flow      |

```mermaid theme={null}
stateDiagram-v2
    [*] --> pending-signatures: create TPA
    pending-signatures --> pending-activation: all signed
    pending-activation --> activated: TPA confirmed
```

***

## What is attached to a TPA

* **Signatories** — people who receive email and sign with eID
* **Legal text** — snapshot at creation
* **Signed PDF** — generated when signing is complete
* **Organizations** — your runtime orgs link here via `tpa_id`

***

## Key fields

| Field                                    | Purpose                                     |
| ---------------------------------------- | ------------------------------------------- |
| `id`                                     | Use when creating organizations (`tpa_id`)  |
| `payment_product_id`                     | Which payment product the client signed for |
| `name`, `country`, `organization_number` | Client company identity                     |
| `activated`                              | Whether live transaction flow is enabled    |
| `signatures_verified`                    | Whether signing is complete                 |

***

## Your integration

You create the TPA and add signatories via API. Signatories complete signing in a web flow — you do not implement eID yourself.

→ [TPA flow — full walkthrough](/ems/tpa-flow) · [eID signing](/ems/eid-signing)