Technical Reference

TradeSyncEngine

Architecture, integration specs, security model, and configuration reference

3–4 hrs

Daily ops time eliminated

5 min

Sync cycle frequency

8

Trade products supported

100%

Immutable audit coverage

Live Product

The bridge between Finacle and FCC your operations team has been waiting for

TradeSyncEngine is an enterprise-grade synchronisation platform purpose-built for banks running Infosys Finacle as their core banking system and Finastra FCC as their trade finance platform.

It eliminates the manual re-keying that occurs between the two systems every day — the spreadsheets, the emails, the missed entries, the failed audits — and replaces all of it with a fully automated, 5-minute sync cycle with intelligent retry, zero-code field mapping, and an immutable audit trail baked in from day one.

What it does

Fetches trade data from Finacle every 5 minutes via REST API

Transforms payloads using a zero-code field mapping engine per product and event type

Pushes to FCC via REST API or XML file drop — your environment, your choice

Retries failed syncs automatically with product-specific policies (up to 5× for LC)

Writes every action to an immutable audit log — who, what, when, outcome, IP address

Auto-emails a formatted PDF report to the operations team every morning at 08:00

ROI in days

The operational shift is immediate

Metric
Before
After TradeSyncEngine
Daily operations time
3–4 hours of manual re-keying
<15 minutes monitoring
Failed sync detection
Hours or days after the fact
Immediate dashboard alert
Duplicate submissions
Possible with manual process
Impossible — idempotency keys
Audit trail preparation
Days of research across emails
On-demand filtered export
Time to go live
6–12 months custom build
Days — product, not project

How it works

The 6-step sync lifecycle

Every trade follows the same deterministic path — from Finacle fetch to FCC confirmation, with retry and audit handled automatically.

01

Fetch

Query Finacle by CIF, reference, product, date range

02

Queue

Maker selects trades + idempotency key generated

03

Transform

Field Mapping Engine applies product/event rules

04

Sync

REST API or XML file drop to FCC every 5 minutes

05

Retry

Intelligent retry: up to 5× for LC/EL, 3× others

06

Audit

Immutable log + auto-emailed PDF report at 08:00

Coverage

8 trade finance products

Out-of-the-box support for the full range of trade finance instruments. High-value LC products get extended retry policies — because they need it.

LC5× retries

Import Letter of Credit

High-value, time-critical LC imports

EL5× retries

Export Letter of Credit

Export LC with full lifecycle tracking

IC3× retries

Import Collection

Documentary import collections

EC3× retries

Export Collection

Documentary export collections

TF3× retries

Trade Financing

Short-term trade finance facilities

SG3× retries

Shipping Guarantee

Shipping and delivery guarantees

UI3× retries

Undertaking Issued

Bank guarantee undertakings issued

UA3× retries

Undertaking Advised

Bank guarantee undertakings advised

Pink badge = high-value products with 5-retry policy · Grey badge = standard 3-retry policy

Queue Intelligence

Retry that actually thinks

Not all failures are equal. TradeSyncEngine classifies every error and responds accordingly — retrying what can recover, stopping what can't.

Queue status lifecycle

PENDINGQueued by maker, awaiting next cycle
PROCESSINGActive in current sync cycle
SUCCESSFCC confirmed — done
FAILEDError — evaluating retry eligibility
RETRYScheduled for next retry at nextRetryTime
EXHAUSTEDMax retries reached — human review needed

Error classification & retry policy

NETWORK
Transient outage

Always retry

FCC_FUNCTIONAL
FCC-side issue

Retry (may recover)

VALIDATION
Bad payload

No retry — fix data

DUPLICATE
Idempotency match

No retry — already sent

Additional controls

  • Batch size: 100 items per 5-minute cycle
  • Idempotency keys — duplicates impossible in FCC
  • nextRetryTime scheduling — no constant polling overhead
  • License quota gate checked before every cycle
  • 365-day payload archive for all Finacle payloads
  • Individual reprocess or process-all-now override

Field Mapping Engine

Zero custom code for new products

Every Finacle field that needs to land in FCC goes through the mapping engine. Rules are configured per product code and event type — LC INITIATION has entirely different rules from LC AMENDMENT, which has different rules from IC INITIATION.

Adding a new trade product or changing a field mapping takes minutes in the admin UI. No code deploy. No downtime. Effective on the next sync cycle.

  • Per product + per event type rules (granular control)
  • Mandatory field validation — bad data blocked before FCC
  • Wildcard rules for cross-product defaults
  • Duplicate mapping detection
  • Priority ordering within a rule set
  • Soft delete — history always preserved
Mapping Rule — LC / INITIATION
productCode:"LC"
eventType:"INITIATION"
finacleFieldPath:"tradeRef.referenceNumber"
fccFieldName:"REFERENCE_NO"
transformRule:"UPPERCASE"
dataType:"STRING"
isMandatory:true
priority:1
Live update · No deploy required

Security & Compliance

5-tier RBAC + immutable audit

Maker-Checker isn't a workflow add-on. It's the system architecture. Every action is captured, attributed, and permanent.

Role hierarchy

RoleWhoCan do
VIEWERAuditors, managementRead-only access to trades and reports
MAKERTrade officersFetch from Finacle and queue trades
CHECKERSenior officersReview and approve queued trades
OPSIT operationsMonitor, retry, manage queue
ADMINSystem administratorFull access — users, config, all settings

Security & compliance features

JWT + BCrypt

Stateless JWT tokens, BCrypt hashing (strength 10), account locking on failed attempts

Immutable audit log

Every action recorded: who, what, when, IP address, outcome. No update or delete endpoints exist.

SSO — SAML 2.0 / OAuth 2.0 / OIDC

Federate with ADFS, Azure AD, Okta or any standard identity provider. Fallback to local login.

License-gated operations

RSA-signed license with quota tracking. Sync cycle blocked when quota or expiry is reached.

Integration Architecture

Two integration paths, one engine

Your network, your choice. Switch modes in the admin settings — no code change, no restart.

Mode 1

FCC REST API

Direct HTTP calls to FCC portal with Bearer token + API key authentication. Full response validation with FCC transaction ID tracking.

  • Direct HTTP to FCC portal
  • Bearer token + API key auth
  • Response validation
  • FCC transaction ID tracking

Best for: Direct FCC network access

Mode 2

XML File Drop

Transformed XML written to a shared folder path. FCC's standard file polling picks up automatically — no FCC API credentials required.

  • Transformed XML to shared folder
  • No FCC API credentials needed
  • Works in air-gapped environments
  • FCC polls at its own schedule

Best for: Air-gapped or restricted environments

Finacle integration

Finacle is queried via REST API + JSON payload using API Key authentication. A configurable base URL supports any Finacle deployment topology. Mock mode is available for testing and UAT environments with no external dependency required.

Technology

Built on the stack your enterprise already trusts

Spring Boot 3

Backend

Java 17

Backend

Angular 17

Frontend

Oracle 12c+

Database

Quartz JDBC

Scheduler

Spring Security + JWT

Security

Apache PDFBox

Reports

Spring WebClient

Integration

Spring Boot + Java 17 · Angular 17 standalone · Oracle 12c+ · Quartz JDBC scheduler · JWT stateless auth · Apache PDFBox for reports

Product Guide

16-page technical guide — all the detail you need

Architecture diagrams, field mapping examples, API surface, security model, licensing, and deployment guide. Everything a technical evaluation needs.

Ready to Build?

Let's architect something
worth shipping.

Start with a free 45-minute architecture review. We'll map out your technical challenges and propose a clear path forward — no sales pitch.