Allow to create JSON format without saving to the in-memory store

[yordis]

ACH Version

v1.22.0

What were you trying to do?

We are using the ACH to analyze a lot of files from our back-office admin tools; therefore, we create the same ACH file multiple times (because we do not have UUIDs, neither we want to deal with it) to read the JSON format of it.

That will cause a memory increase in the ACH server when we don't want to save the file anywhere, so a request-response style to parse the content

What did you expect to see?

An endpoint returns the JSON payload without saving the NACHA file in the in-memory store.

[adamdecaf]

I know this issue is requesting an HTTP endpoint, but would the achcli tool work?

$ achcli -reformat json ./test/testdata/ppd-debit.ach | jq .  

{
  "id": "",
  "fileHeader": {
    "id": "",
    "immediateDestination": "231380104",
    "immediateOrigin": "121042882",
    "fileCreationDate": "190624",
    "fileCreationTime": "0000",
    "fileIDModifier": "A",
    "immediateDestinationName": "Federal Reserve Bank",
    "immediateOriginName": "My Bank Name"
  },
  "batches": [
    {
      "batchHeader": {
        "id": "",
        "serviceClassCode": 225,
        "companyName": "Name on Account",
        "companyIdentification": "121042882",
        "standardEntryClassCode": "PPD",
        "companyEntryDescription": "REG.SALARY",
        "effectiveEntryDate": "190625",
        "settlementDate": "   ",
        "originatorStatusCode": 1,
        "ODFIIdentification": "12104288",
        "batchNumber": 1
      },
      "entryDetails": [
        {
          "id": "",
          "transactionCode": 27,
          "RDFIIdentification": "23138010",
          "checkDigit": "4",
          "DFIAccountNumber": "12345678         ",
          "amount": 100000000,
          "identificationNumber": "               ",
          "individualName": "Receiver Account Name ",
          "discretionaryData": "  ",
          "traceNumber": "121042880000001",
          "category": "Forward"
        }
      ],
      "batchControl": {
        "id": "",
        "serviceClassCode": 225,
        "entryAddendaCount": 1,
        "entryHash": 23138010,
        "totalDebit": 100000000,
        "totalCredit": 0,
        "companyIdentification": "121042882",
        "ODFIIdentification": "12104288",
        "batchNumber": 1
      },
      "offset": null
    }
  ],
  "IATBatches": null,
  "fileControl": {
    "id": "",
    "batchCount": 1,
    "blockCount": 1,
    "entryAddendaCount": 1,
    "entryHash": 23138010,
    "totalDebit": 100000000,
    "totalCredit": 0
  },
  "fileADVControl": {
    "id": "",
    "batchCount": 0,
    "entryAddendaCount": 0,
    "entryHash": 0,
    "totalDebit": 0,
    "totalCredit": 0
  },
  "NotificationOfChange": null,
  "ReturnEntries": null,
  "validateOpts": null
}

[yordis]

It would work for us, we are leveraging the ACH from Retool App and other systems that don't have access to the CLI