Pack · Finance & Payments

Finance & Payments data, already modelled.

Regulated finance templates — masked card payments (PCI), bank accounts, invoices, and KYC profiles.

Templates: 4
Gate on review: 4

The templates

Every template in this pack, printed as it ships.

Canonical column names, field counts, validator ids and risk level — read straight from the shipped template definition. Paste the header row from your own export and the deterministic layers will show you, column by column, which of these 4 it lands on.

Paste your header row

Or try:

Nothing is uploaded. The match runs in this tab against the shipped template vocabulary, using the same normaliser and fuzzy scorer the Worker runs on layers 2 and 3.

Risk

Payments

high

Masked card payments: brand, last 4 digits, amount, processor reference. PCI scope — full PAN must NEVER be imported, only the last 4 digits.

7 fields41 hintsregex

card_last4 · card_brand · amount · currency · status · +2

payments_v1View

Bank accounts

high

Bank account details with IBAN/BIC validation.

6 fields26 hintsibanbic

account_holder · iban · bic · account_number · routing_number · +1

bank_accounts_v1View

Invoices

medium

Accounts-receivable invoices: amounts, due dates, payment status.

7 fields48 hints

invoice_number · customer_id · amount_due · currency · due_date · +2

invoices_v1View

KYC profiles

high

Know-Your-Customer identity profiles with risk rating. Contains PII.

7 fields34 hintsdate_rangeregex

subject_id · legal_name · date_of_birth · national_id · country · +2

kyc_profiles_v1View

4 templates
4 validators in this pack
137 header hints across 5 languages
27 canonical fields

Side by side

The whole pack as counted facts.

Same information the cards carry, in one scannable block — for the moment you are choosing between two templates that both look plausible. Every number is derived from the shipped definition at build time.

Template	Fields	Required	Validated	Hints	Risk	FHIR
Payments`payments_v1`	7	3	1	41	high	—
Bank accounts`bank_accounts_v1`	6	2	2	26	high	—
Invoices`invoices_v1`	7	4	0	48	medium	—
KYC profiles`kyc_profiles_v1`	7	2	2	34	high	—

27 canonical columns and 137 distinct header hints across the pack. "Validated" counts columns carrying at least one field-level validator; "hints" counts the distinct multilingual header names the deterministic layers resolve for free.

Validators

The checks that fire before you commit.

4 validators run on this pack. They are pure functions — the same code runs in the Worker, in the browser widget and in the MCP validate_row tool, so a dry run and a commit cannot disagree.

Validator	What it checks	Templates in this pack
`bic`	ISO 9362 bank identifier shape.	bank_accounts_v1
`date_range`	Parses the date (ISO / US / EU / epoch) and bounds it.	kyc_profiles_v1
`iban`	mod-97 checksum on the reordered value, with per-country length from the SWIFT IBAN Registry.	bank_accounts_v1
`regex`	Pattern match against the template-supplied expression.	payments_v1 · kyc_profiles_v1

Empty values bypass a validator — required-ness is checked separately. LOINC / ICD-10 / ATC additionally try to resolve a free-text value to a canonical code before failing.

Review gating

4 of 4 come back flagged for review.

A template's risk level is the only input to the flag. Medium and high templates make PATCH /uploads/:id/mappings return requires_hitl so your own workflow can hold the commit — it is a flag, not a queue. Native AgentGate HITL integration is on the roadmap for Q3 2026 and is not wired in v1.

low0

Commits straight through. No review flag on the mappings response.

medium1

Flagged `requires_hitl: true` with `hitl_status: "pending_review"` so you can gate your own commit workflow.

invoices_v1

high3

Flagged `requires_hitl: true` with `hitl_status: "pending_review"`. Regulated identifiers — card data, IBANs, payroll, KYC.

payments_v1 · bank_accounts_v1 · kyc_profiles_v1

Try it

One call maps a file onto any of them.

Name the template and POST the file. The cascade resolves what it can on the deterministic layers — statistics, heuristic, fuzzy — and only the leftovers reach the metered LLM.

bash

curl -X POST https://api.adaptivmapr.com/v1/uploads \
  -H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
  -F "template=payments_v1" \
  -F "file=@your_export.csv"

→ upload created · mappings ready · confirm before commit

Schema-only mode sends column headers plus at most three sample rows, each clamped to 80 characters — a data-minimization mode enforced at the HTTP edge. Full-data mode routes the metered layer-5 call in-region under a BAA and costs 20% more, and stays locked until the workspace accepts the BAA/NDA in Settings → Security & Data.

Read the quickstart

payments_v1Payments7 fields
bank_accounts_v1Bank accounts6 fields
invoices_v1Invoices7 fields
kyc_profiles_v1KYC profiles7 fields

Put the finance & payments pack to work — without shipping raw records.

Schema-only mode leaves only headers and up to three clamped sample rows. Full-data adds row-level AI, routed in-region under a BAA.

Get an API key See pricing