Skip to main content
POST
Ignore a transaction

Authorizations

Authorization
string
header
required

Bearer token authentication (format: "Bearer {token}")

Headers

X-Request-Id
string

A unique identifier for tracing the request across services.

X-Idempotency
string

Optional idempotency key for safe retries. Matcher reads the key only from this header, and only when you send one. A request that carries a key only in X-Idempotency-Key or Idempotency-Key is refused with 400 (MTCH-0015), and nothing is processed. If the same key is sent again and the original request was already processed, the stored response is returned with X-Idempotency-Replayed: true. A malformed key returns 400, a key whose first request is still in progress returns 409, and an idempotency storage failure returns 500. These refusals are problem documents.

Path Parameters

contextId
string<uuid>
required

The unique identifier of the reconciliation context. Context ID

transactionId
string<uuid>
required

The unique identifier of the transaction. Transaction ID

Body

application/json

Ignore transaction request

reason
string
required

Reason for ignoring the transaction

Minimum string length: 1
Example:

"Duplicate entry - already processed manually"

Response

Indicates that the request was successful and the response contains the expected data.

amount
string
required

Transaction amount as a decimal string in the transaction currency (precision preserved verbatim; never a float)

Example:

"1000.50"

contextId
string<uuid>
required

Reconciliation context this transaction belongs to

Example:

"550e8400-e29b-41d4-a716-446655440000"

createdAt
string<date-time>
required

Creation timestamp (RFC 3339)

Example:

"2025-01-15T10:30:00Z"

currency
string
required

ISO 4217 currency code of the amount

Example:

"USD"

date
string<date-time>
required

Transaction value date (RFC 3339)

Example:

"2025-01-15T00:00:00Z"

dedupeKey
string
required

Read-only: the duplicate-key value this row was imported under, derived from the source's duplicate key declaration at import time. A source can change that declaration later, so this is the only place that says which identity THIS row carries. Prefixed v1 when the key spells out the fields it was derived from, v1h when those fields were hashed because the spelled-out key was too long to index.

Example:

"v1|external_id=9:TXN-12345"

externalId
string
required

External identifier carried from the source system

Example:

"TXN-12345"

extractionStatus
enum<string>
required

Field-extraction status: PENDING (queued), COMPLETE (fields parsed), FAILED (extraction error)

Available options:
PENDING,
COMPLETE,
FAILED
Example:

"COMPLETE"

id
string<uuid>
required

Unique identifier for the transaction

Example:

"550e8400-e29b-41d4-a716-446655440000"

jobId
string<uuid>
required

Ingestion job that produced this transaction

Example:

"550e8400-e29b-41d4-a716-446655440000"

sourceId
string<uuid>
required

Source this transaction belongs to

Example:

"550e8400-e29b-41d4-a716-446655440000"

status
enum<string>
required

Matching status: UNMATCHED (no match found), MATCHED (reconciled), IGNORED (excluded from reconciliation by an operator), PENDING_REVIEW (imported under the blank-external-id review policy and awaiting an operator decision)

Available options:
UNMATCHED,
MATCHED,
IGNORED,
PENDING_REVIEW
Example:

"UNMATCHED"

description
string

Free-text description carried from the source

Example:

"Wire transfer from ABC Corp"

metadata
object

Normalized source metadata: unmapped source columns the engine projects into composite match keys and FX-conversion inputs (e.g. counterparty, bank_transaction_code, fx_rate). Arbitrary key/value, tenant-scoped to the caller's own data.