TPA - OpenCard

TPA = Transaction Processing Authorization. It is the legal agreement between a client company and OpenCard that card transaction data from a specific card program may flow to your EMS. Without a signed and activated TPA, no transactions are delivered for that client and issuer combination.

What it represents

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

The individual employee signs a separate document — PDPC — when they onboard as a 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

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`)
`card_issuer_id`	Which card program
`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 · eID signing