When debugging the Forte EFT transaction settlement process, it is not always possible (or convenient) to get the desired responses from Forte. Therefore, code has been added to the PaymentProcessing project to allow reading responses from Json files.
There are two methods by which transactions can be settled; by the nightly automatic settlement process that is performed by the SedonaEFTService service, and by the manually initiated settlement process.
The following Json files are used by the automatic settlement process.
- TestSettlements.json – Settled transactions
- TestFundings.json – Funding entries
- TestFundingSettlements.json – Funded transactions
An additional Json file is used by the manual settlement process.
- TestSettlements_<transaction_id>.json - Settled transactions
The location where these files need to be placed may vary depending on how the debugging is being done, but for the most part they need to be in the folder from which the SedonaOffice executable is being run.
You can find sample json files here, Forte Json files.
To see examples of the contents of these files, refer to the Forte REST API documentation that can be found here https://restdocs.forte.net/?version=latest.
TestSettlements.json
The TestSettlements.json file should contain entries for each transaction that you wish to settle.
A section for each transaction should be included in the "results" section. The entries that need to be modified for the specific transaction are:
- transaction_id – Forte Transaction ID
- reference_id – ACH_Id value from the transaction record in the AR_ACH table
- customer_id – SedonaOffice customer number
- settle_type – Type of settlement: deposit, withdrawal, reject
- settle_response_code – Forte response code (NOTE: for CC, don’t include this entry)
- settle_amount – Transaction amount
- method – Payment method: echeck, cc
TestFundings.json
The TestFundings.json file should contain entries for each funding that you wish to settle.
A section for each funding should be included in the "results" section. The entries that need to be modified for the specific funding are:
- funding_id – Forte Funding ID
- status – Funding status: completed, pending, failed, not_applicable
- effective_date – Funding date
- net_amount – Amount of all transactions in the funding
- funding_response_code – Reason code for funding failure
TestFundingSettlements.json
The TestFundingSettlements.json file should contain entries for each transaction in a funding, and the file should be named for the specific funding. The file name should follow this convention:
“TestFundingSettlements_<Funding ID>.json” – where <Funding ID> is the funding_id value from the TestFundings.json file.
A section for each transaction should be included in the "results" section. These entries should be similar to those in the TestSettlements.json file.
TestSettlements_<transaction_id>.json
This file is identical to the TestSettlements.json file, except that it will contain only a single transaction; the one identified by the transaction ID in the name of the file. There should be one of these files for each transaction that is to be settled by the manual settlement process.
