Transaction file specification
Release 1.0 · CSV or JSON · 1–1,000 records · Up to 2 MiB
Use source records you are authorised to process. Do not include names, wallet addresses, identity documents or other extra identifiers. Files are processed in this browser and are not uploaded. Downloaded reports contain the permitted source references; safeguard them as confidential records.
| Field | Required | Accepted value |
|---|---|---|
| source_system | Yes | Provider or ledger system label|
| source_record_id | Yes | Unique source reference within the source system|
| transaction_timestamp | Yes | UTC timestamp, for example 2026-10-04T10:30:00Z|
| transaction_type | Yes | BUY, SELL, CONVERSION or TRANSFER|
| asset_code | Yes | Uppercase ticker, up to 20 characters|
| fiat_currency | Yes | NGN, USD, EUR or GBP|
| gross_fiat_value | Yes | Nonnegative decimal string; maximum two decimal places; no separators|
| source_status | Yes | ORIGINAL, CORRECTED or REVERSED|
| duty_amount_fiat | No | Provider-reported duty; same decimal format. No rate is calculated|
| remitted_amount_fiat | No | Source-reported remittance; same currency and decimal format|
| receipt_amount_fiat | No | Source-reported receipt amount; same currency and decimal format|
| vasp_remittance_batch | No | Remittance reference. Shared references trigger batch-level review|
| nrs_receipt_reference | No | Receipt reference from your source. No authority lookup is performed|
| state_code | No | Nigerian State code, for example LA or RI. Not a verified allocation instruction|
| original_record_id | For corrections/reversals | Original source reference; cannot equal the correction's own ID
Interpretation
All fields in JSON must be strings. CSV retains amounts as strings. Duplicate source IDs, unsupported columns and malformed values are excluded from original-record totals. Corrections and reversals are held for review and never silently netted against originals.
Amounts agree only when a valid original supplies all three amounts, distinct remittance and receipt references, and equal reported values. Shared payment references require a separate batch-level reconciliation. Agreement does not establish receipt authenticity, payment settlement or legal liability.
The report records both the exact original file SHA-256 and a normalised-record hash. Retain the original source file together with the report. The hash is an integrity reference, not a digital signature or a permanent server audit record.
No tax liability or State allocation is established. Review expiry, engagement mandates, filing and collection are outside this standalone tool.