3) 271 from BackEnd Validation

This route receives the 271 transactions generated by the Payer, validates the transactions, and stores all the valid transactions by using the Archival Service.

Route Structure

Route Components Description

Component Name	Component Type	Description
Get 271 from Inbox	MFT Inbound	Receives the 271 response transactions from the Payer through the MFT channel.
Validate 271 Response	Native Processing	Validates the 271 transactions.
Router	Router	Transmits valid transactions further down the route.
Archive 271 Response	Archival Service Outbound	Stores the 271 transactions in the Archival Service.
Invalid 271	FS Outbound	Stores the 271 transactions that have failed the XEngine validation.
FS Outbound 271	FS Outbound	Stores valid 271 transactions on the file system.