FINS SilverLake Accounts System API - Implementation Template

This API implementation template is a component of MuleSoft Accelerators, which accelerate the implementation of essential integration use cases.

The solution includes pre-built APIs, connectors, and integration templates that help unlock business-critical data from external systems and guide you in adopting best practices synthesized from thousands of customer implementations. Use these assets as is or extend them to meet your company’s unique needs.

---

Overview

This integration template implements the FINS Core Banking Accounts System API specification. This API is for working with the Jack Henry SilverLake provider.

The FINS Silverlake Accounts System API can be used to manage financial accounts, cards, and transactions in a Jack Henry SilverLake instance.

Getting started

The Getting Started with MuleSoft Accelerators guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications.

Once your workstation has been set up and the application template imported into Anypoint Studio, proceed with the Prerequisites section.

Prerequisites

This implementation template has the following dependencies:

• Jack Henry SilverLake instance

Please review the use cases described on the MuleSoft Accelerator for Financial Services solution pages for more information about dependencies on other APIs and services.

jXchange Web Services

The following table lists the jXchange SilverLake services used by this implementation:

Deployment

Each Accelerator implementation template in Exchange includes Bash and Windows scripts for building and deploying the APIs to CloudHub. These scripts depend on repositories, global settings, deployment profiles, and associated properties configured in the Maven settings.xml file.

For additional details, please refer to the Application Deployment section of the Getting Started Guide.

Preparation

Ensure the Maven profile CloudHub-FINS-DEV has been properly configured in your settings.xml file. In particular, make sure the common properties for your environment have been provided (e.g., Anypoint Platform client ID and secret).

Required property overrides

At a minimum, the following properties must be customized for this application to reflect the target deployment environment.

Testing

Use Advanced Rest Client or Postman to send a request over HTTPS. The template includes a Postman collection in the src/test/resources folder. Update the collection variable(s) after successful import.

Implementation notes

1. This version of the template uses the Jack Henry jXchange Connector instead of using the Web Service Consumer Connector as implemented in prior versions.
2. Creation of Financial Accounts with Account Type BlockchainAccount, GeneralLedgerAccount, and CreditCardAccount are not supported by SilverLake.
3. The implementation always populates the SilverLake Financial Account id for accountNumber field. An id or accountNumber cannot be changed.
4. SilverLake System requires Financial Accounts, Financial Transactions to be created/updated with few mandatory parameters (example - BrCode, ProdCode, AcctType, TranCode, and others). These parameters have been set with default values and can be amended through the config files.
5. Account ID returned by the implementation for Financial Account is of - format as Jack Henry SilverLake System mandates passing of Account Type along with Account ID for all operations that are related to the Financial Account.
6. Only the Account Status (OPEN, ON_HOLD, CLOSED, and DORMANT) of the Financial Account can be changed using the patch:/account/{accountId} endpoint.
7. Currency is always defaulted to USD.
8. There is no appropriate field to store GlobalIDs in the SilverLake System.
9. Retrieval and Search of Financial Accounts, Financial Transactions, and Financial Cards does not support retrieval of all balances and auditInfo fields: the results returned will contained configured default values.
10. Search results for Financial Accounts do not return any Secondary Owners, even if they are associated with the Financial Account. Only retrieval of a specific Financial Account returns the Secondary Owners.
11. Customer ID or Account ID is needed to perform Search of Financial Accounts. If either of them are not provided in the input it is treated as a Bad Request by the implementation.
12. Account ID is needed to fetch Financial Transactions. If Account ID is not provided in the input it is treated as a Bad Request by the implementation.
13. Account ID or Card ID is needed to perform Search of Financial Cards. If either of them are not provided in the input it is treated as a Bad Request by the implementation.
14. Search for Financial Accounts, Financial Transactions and Financial Cards by External Id returns no results.
15. Search for Financial Accounts, and Financial Cards with fromDate and toDate is not supported.
16. Financial Transaction of type PaymentTransaction is not supported by the implementation.
17. SilverLake System runs nightly jobs to post Financial Transactions. Balances are only rightly reflected after the jobs are completed.
18. Creation of a Financial Transaction with type TransferTransaction in Jack Henry SilverLake System returns XferKey. This key is returned as Transaction ID by the implementation. Search using the Transaction ID (XferKey) may not return accurate results until the transaction is Posted in SilverLake System.
19. Filtering of records is done by the Implementation as Jack Henry SilverLake System always returns a superset of records that meet the input criteria.
20. This implementation does not support cards with Card Type as CreditCard.
21. Financial Cards can only be created for Financial Accounts with Status as Open in SilverLake System.
22. For Fee Reversal transaction value of transactionType should be CreditTransaction and transactionSubType should be FEE.
23. Stop Check and Stop ACH functionality is supported by POST: transaction.
24. For Stop Check transaction value of transactionType should be Misc and transactionSubType should be CHECK.
25. For Stop ACH transaction value of transactionType should be Transfer.
26. Update of transfer transaction is not supported.

Additional resources

• The Data mappings tab describes how the request and response data structures are mapped between the API interface and the Jack Henry SilverLake provider.
• Refer to the Accelerators documentation home for more information about the MuleSoft Accelerators.