fins-reconciliation-prc-api
home
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 Reconciliation Process API specification.
FINS Reconciliation Process API supports posting the payments information required for reconciling a payment.
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:
- Anypoint MQ Destinations
- FINS Core Banking Accounts System API
- FINS Core Banking Customers System API
- Accelerator Notifications Process API
- FINS Foreign Exchange System API
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.
Anypoint MQ destinations
The following Anypoint MQ destinations must be created and accessible for this API:
- fins-reconciliation-queue
- fins-reconciliation-dl-queue
The FINS Common Resources asset contains a Postman collection, which can be used to create the destinations and client application required for use by accelerator applications.
API dependencies
The following table lists all endpoints used by this API.
| API name | Endpoint | Action |
|---|---|---|
| FINS Corebanking Accounts System API | get:/accounts | Search Account using AccountId |
| FINS Corebanking Accounts System API | get:/transactions | Search Transaction by OriginatorId |
| FINS Corebanking Accounts System API | patch:/transactions/{transactionId} | Update Transaction By TransactionId |
| FINS Corebanking Customers System API | get:/customers/{customerId} | Get Customers By CustomerId |
| FINS Foreign Exchange System API | get:/rate | Get Exchange Rate |
| Accelerator Notifications Process API | post:/notifications | Send Notifications |
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 to reflect the target deployment environment.
| Property Name | Description |
|---|---|
| api.autodiscoveryID | Required if using API Manager to secure this API |
| address-validation-sys-api.host | Address Validation System API HostName |
| address-validation-sys-api.port | Address Validation System API Port |
| address-validation-sys-api.ping-path | Address Validation System API Ping path |
| global-party-sys-api.host | Accelerator MariaDB Global Party System API HostName |
| global-party-sys-api.port | Accelerator MariaDB Global Party System API Port |
| global-party-sys-api.ping-path | Accelerator MariaDB Global Party System API Ping path |
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.
Additional resources
- The Data mappings tab describes how the request and response data structures are mapped between the API interfaces.
- Refer to the Accelerators documentation home for more information about the MuleSoft Accelerators.