Finance & Payments

The templates in this pack

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

Try in Workbench Full template page

Schema

The canonical field set, printed as it ships.

7 fields with multilingual hints (DE / FR / IT / EN / ES) and field-level validators. Any source column that resolves to one of these is mapped by the cascade — most of them on the deterministic layers, with no LLM call.

payments_v1

fields: 7
required: 3
validated: 1
hints: 41

Canonical column	Type	Required	Validators	Header hints the cascade matches
`card_last4`	string	yes	`regex`	kartennummer letzte 4derniers 4 chiffresultime 4 cifrelast 4últimos 4
`card_brand`	enumvisamastercardamexdiscover	—	—	kartentypkartenmarkemarkemarque de cartemarquemarca cartacard brandcard typemarca de tarjeta
`amount`	number	yes	—	betragmontantimportoamountimporte
`currency`	string	yes	—	währungdevisevalutacurrencymoneda
`status`	enumauthorizedcapturedrefundedfailed	—	—	statusstatutstatoestado
`processor_ref`	string	—	—	referenzréférenceriferimentoreferencereferencia
`captured_at`	date	—	—	buchungsdatumerfasst amerfassungsdatumgebucht amdate de capturedata di addebitocaptured atfecha de captura

Read the same definition as JSON at GET /v1/templates/payments_v1. A hint match resolves on layer 2 — no LLM call, no token spend, just the flat per-map fee. Hover a validator id to see what it checks.

7 canonical fields
3 required
1 validated
41 header hints
Finance & Payments pack

Try it

A real file, a real call, one template id.

8 rows, masked card data (last 4 only). Fully synthetic — safe to share, commit, and run in CI.

bash

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

→ upload created · mappings ready · confirm before commit

Download payments_sample.csv Open in Workbench →

This is a high-risk template. Its mappings response comes back with requires_hitl: true so you can gate your own commit. Schema-only mode — headers plus at most three sample rows, each clamped to 80 characters — is a data-minimization mode. Full-data routes the metered layer-5 call in-region under a BAA at a 20% uplift, and stays locked until the workspace accepts the BAA/NDA in-app.

mcp

adaptivmapr.match_headers({
  template_id: "payments_v1",
  headers: ["card_last4", "card_brand", "amount", "currency"]
})

schema-only · headers and ≤3 clamped rows only

Put payments in production — without shipping raw records.

Schema-only mapping leaves only headers and a handful of clamped samples. Add full-data when you need row-level AI, routed in-region under a BAA.

Full template page See pricing