Sample Files
Download validated sample payloads for the X12 and ISO 20022 transactions this platform parses. Every file passes the production engine in the test suite before it ships.
ANSI X12 5010 samples
837P Professional Claim
A professional (837P) healthcare claim with submitter, billing provider, subscriber, diagnosis, and service line segments.
835 Remittance Advice
An electronic remittance advice with payment details, a claim payment loop, a CARC/RARC adjustment, and the service line.
270 Eligibility Inquiry
An eligibility and benefits inquiry with payer, provider, and subscriber hierarchy plus the service type code being requested.
834 Benefit Enrollment
A benefit enrollment and maintenance transaction with sponsor, payer, member, demographics, and health coverage segments.
837I Institutional Claim
An institutional (837I) healthcare claim with submitter, receiver, billing provider, subscriber, principal diagnosis, and revenue line segments.
271 Eligibility Response
An eligibility and benefits response with payer, provider, and subscriber hierarchy plus an EB benefit segment.
276 Claim Status Inquiry
A claim status inquiry with payer, provider, and subscriber hierarchy plus the claim reference and service date.
277 Claim Status Response
A claim status response with the payer, provider, and subscriber hierarchy plus a claim status category and amount.
ISO 20022 samples
pacs.008 Credit Transfer
A FI-to-FI customer credit transfer with UETR, settlement amount, debtor, creditor, and both agent BICs.
camt.053 Bank Statement
An end-of-day bank statement with opening and closing balances plus one booked credit entry with counterparty details.
pain.001 Payment Initiation
A customer credit transfer initiation with debtor and creditor accounts, agents, execution date, and instructed amount.
camt.054 Debit/Credit Notification
A debit/credit notification with account details and one booked credit entry including the counterparty and end-to-end reference.
pacs.002 Payment Status Report
A payment status report with the original end-to-end reference, UETR, rejection status, and a reason code.
pain.002 Payment Status Report
A customer payment status report with the original message reference, group status, and per-transaction acceptance status.
GS1 samples
GS1 Element String
A GS1 AI element string carrying the GTIN, batch/lot number, expiration date, and serial number for a serialized trade item.
SSCC Element String
A GS1 serial shipping container code (AI 00) element string for logistics unit labelling and ASN testing.
GS1 Digital Link URI
A GS1 Digital Link URI resolving a GTIN with batch/lot and serial qualifiers for 2D barcode and resolver testing.
Frequently Asked Questions
Yes. Every payload is synthetic test data with no real patient, payer, account holder, or company information. Use them for parser tests, sandbox fixtures, and integration development.
Each file is parsed by the production Stanza engine in the test suite: X12 payloads pass envelope and SNIP checks, and ISO 20022 messages are validated and parsed before publishing. If a sample breaks, the build fails.
Yes. Change identifiers, amounts, and dates to suit your scenario. Keep the segment counts, control numbers, and check digits consistent, or run the edited payload through the matching parser to confirm it still validates.
The browser tools cover IBAN, container, air waybill, and GTIN checks. For X12 and ISO 20022 payloads, use the API playground or the parser endpoints documented on each specification page.