# Financial Services 2.1.0 — quickstart

Synthetic banking, cards, lending, payments and fraud test data with linked masking. This pack can be activated self-service.

All data in this bundle is synthetic, generated from a fixed seed by the pack's own generator. Real data is processed only by the DataNivra agent inside your network (customer-resident processing); this bundle never contains customer data, keys or credentials.

## Prerequisites

- A DataNivra account; the Free Trial includes this pack.
- One DataNivra agent inside your network (outbound HTTPS only) that ships Financial Services 2.1.0.
- Read-only access to a compatible source (verified with this pack: PostgreSQL, Local files (Parquet / CSV)).
- A non-production target environment the agent may write test data to.
- A masking key in your own secret store, referenced as vault://…, azure-kv://… or env://… (DataNivra only ever sees the reference).
- For production sources, a second person who approves policies (separation of duties).

## First certified dataset

1. **Try it with synthetic data.** Sign up and start the hosted sandbox (`POST /v1/sandbox`,
   `api/sandbox.json`, or `datanivra sandbox start`). Nothing to install.
2. **Inspect and activate the pack.** `GET /v1/industry-packs/financial-services` shows versions,
   entitlement, activation checks and which of your agents can run it;
   `POST /v1/industry-packs/financial-services/enable` (or `datanivra packs enable financial-services`) activates it.
3. **Install or reuse the agent.** One agent runs many packs. It must report
   `financial-services` 2.1.0 with the catalogued integrity digest
   (see `docs/runbooks/deploy-agent-docker.md`).
4. **Connect a source** through the normal source workflow (connection *reference* only).
   Verified with this pack: PostgreSQL, Local files (Parquet / CSV).
5. **Choose scenarios**, for example:
   - `FS_EVERYDAY_BANKING` (NORMAL): Ordinary customers, accounts, cards and activity
   - `FS_FAILED_PAYMENTS` (RARE): Outgoing payments that fail or are returned, each with a failure reason
   - `FS_DUPLICATE_TRANSACTIONS` (DUPLICATE): Transactions re-submitted with identical content under new ids (double posting)
6. **Create policy drafts from the pack templates:** `POST /v1/industry-packs/financial-services/policy-drafts`
   (`api/policy-drafts.json`). Review, submit and approve them (a second person approves policies
   for production sources).
7. **Request the dataset** (`api/dataset-request.json`). The agent subsets, masks, generates the
   scenarios, validates and **certifies** it inside your network.
8. **Provision** the certified version to a non-production environment (`api/provision.json`).
9. **Download the evidence**: certification report and evidence references
   (`GET /v1/certification-reports?dataset_id=…`, `GET /v1/evidence?dataset_id=…`).

See `TROUBLESHOOTING.md` for reason codes and recovery.