CSV Samples & Field Maps

Overview

This page provides:

Sample CSV files for each report type
Headers-only (empty file) examples
Field mapping references between CSV columns and API objects
Rail-specific field behavior and expectations

Newline CSV reports are event-driven, not timeline-based, meaning records appear based on lifecycle events such as settlement or record updates—not on fixed reporting intervals.

Available CSV Samples

Each report type includes:

Populated sample (2–5 rows)
Headers-only sample (valid empty file format)

CSV files are delivered at scheduled intervals even when no data is present, resulting in header-only files.

Intraday CSV Samples

Intraday Settled Transactions

Represents:

Transactions that have completed settlement.

Intraday Updated Transactions

Represents:

Changes to transaction records (status updates, corrections, NOCs).

Intraday Accounts

Represents:

Current account state based on processed activity.

Pending Authorizations (if enabled)

Represents:

Pending debit authorizations when Client Authorization is active.

Denied Authorizations (if enabled)

Represents:

Authorization attempts that were declined.

Prior Day CSV Samples

Prior Day Settled Transactions

Same structure as Intraday Settled, aggregated for prior day activity.

Prior Day Updated Transactions

Same structure as Intraday Updated, including:

Failed transactions
NOCs
Record corrections

Prior Day Accounts

Represents:

End-of-day balances derived from settled transactions
Optional statement_closing_balance derived from posted transactions

Prior Day Posted Transactions

Represents:

Transactions as they appear on the bank statement.

Field Mapping

Settled Transactions CSV

CSV Column	Maps To	Notes
`transaction_id`	`transaction.id`	Always populated
`amount`	`transaction.amount`	Always populated
`status`	`transaction.status`	Only settled events
`settled_at`	`transaction.settled_at`	Present at settlement

Each row represents a single settlement event.

Updated Transactions CSV

CSV Column	Maps To	Notes
`transaction_id`	`transaction.id`	Always populated
`status`	`transaction.status`	May include failed or canceled
`update_type`	Derived	Indicates update reason
`ach_details`	`transaction.ach`	May contain JSON

"Updated" refers to record-level changes, not settlement events.

Posted Transactions CSV

CSV Column	Maps To	Notes
`transaction_id`	`transaction.id`	Always populated
`posted_at`	`transaction.posted_at`	Statement date
`amount`	`transaction.amount`	Always populated

This file reflects bank statement activity, not settlement timing.

Accounts CSV

CSV Column	Maps To	Notes
`settled_balance`	Derived from settled transactions	Operational balance
`statement_closing_balance`	Derived from posted transactions	Statement-aligned

Important:

settled_balance ≠ statement_closing_balance
Posting timing can cause differences

Rail-Specific Notes

ACH

Received transactions may have blank batch_id
NOCs appear in Updated Transactions, not Settled CSV

RTP / Instant Payments

Settles in near real time
May post on the next business day if processed on weekends

Cross-Rail Behavior

Some rail-specific fields appear only when applicable.

CSVs may contain optional or empty fields depending on:

Rail type
Transaction lifecycle stage
Feature enablement

How to Read These CSVs

Event-Driven Model

CSV files reflect events, not full transaction timelines.

A transaction may appear in:

Settled only
Updated only
Both
Neither

Nested / Rail Fields

Some fields are serialized (for example, JSON in a single column).

These represent underlying rail objects (for example, ACH details).

Empty Fields

Fields may be blank when:

The rail does not provide that data
The lifecycle stage does not include it yet
The transaction type does not require it

Header-Only Files

A valid empty CSV contains:

Only column headers
No rows

These are delivered when no qualifying events occur during the reporting interval.

FAQs

Why is this field blank in my CSV?

Fields may be empty due to rail differences, lifecycle stage, or optional data availability.

Which API fields map to this CSV column?

Refer to the field mapping tables above. CSV fields are derived from transaction objects and may vary by rail.

Why does the sample CSV include JSON in a column?

Some rail-specific data (for example, ACH details) is serialized into a single column.

Why do sample files differ from my production files?

Differences may be caused by:

Program-level configuration
Enabled features (for example, Client Authorization)
Available payment rails

What does a correct empty CSV look like?

A file containing only headers and no data rows.