Reference

Evidence schemas

CSV uses these headers. JSON uses the same names inside payments, events, rows, or submissions. A cutoff schedule travels in cutoff_schedule next to submissions. Account numbers in these files are fingerprinted on intake and are not copied into the sealed record.

Back to upload

Optional evidence

Prior payment history

payment_history

Columns (8)

beneficiary_key
account
amount_minor
value_date
originator_id
trace
timestamp
tz

CSV header row

beneficiary_key,account,amount_minor,value_date,originator_id,trace,timestamp,tz

Historical approval events

approval_events

Columns (4)

payment_ref
approver_id
timestamp
tz

CSV header row

payment_ref,approver_id,timestamp,tz

Approval matrix with effective dates

approval_matrix

Columns (6)

originator_id
rail
dual_control_minor
amount_limit_minor
effective_from
effective_to

CSV header row

originator_id,rail,dual_control_minor,amount_limit_minor,effective_from,effective_to

Beneficiary account change events

beneficiary_changes

Columns (6)

beneficiary_key
old_account
new_account
timestamp
tz
authorized_by

CSV header row

beneficiary_key,old_account,new_account,timestamp,tz,authorized_by

Submission timestamps and bank cutoff schedule

submissions

Columns (7)

payment_ref
submitted_at
tz
rail
weekday
cutoff_local
cutoff_tz

CSV header row

payment_ref,submitted_at,tz,rail,weekday,cutoff_local,cutoff_tz

Payment file

Normalized wire CSV or JSON

Columns (14)

originator_name
originator_id
originator_account
beneficiary_name
beneficiary_key
beneficiary_account
creditor_agent
amount_minor
currency
value_date
message_type
end_to_end_id
instruction_id
remittance

CSV header row

originator_name,originator_id,originator_account,beneficiary_name,beneficiary_key,beneficiary_account,creditor_agent,amount_minor,currency,value_date,message_type,end_to_end_id,instruction_id,remittance

JSON may also include group.number_of_transactions and group.control_sum_minor. A CSV has no group totals, so those checks are unavailable.