Acutec Global

Services LLP
We make Technology work for you
 About Acutec Serving Customers across the Globe since 2005

50+ Solution
• Payment Hub RFMS
200+
Banks • Payment Application
Implementations
ACUTEC GLOBAL SERVICES LLP Support Services
(formerly Acumen Software Technologies)

A Great Place to Work – 2 Glorious

Wins in a Row Technology Awards

Global Award for

Award for India 500 Most
Golden preferred
Solution Promising IT
Business Solution
Provider of the Company for
Excellence Quality
Provider- 4
Award -2022 Year -2022 2021
Excellence -2021
 • RFMS Payment Hub- Comprehensive product

• Plug-n Play Components

Products  RFMS Payment Adapters  RFMS Liquidity Manager

 RFMS Message Broker  RFMS Rule Manager

 RFMS Web-portal  RFMS Notification Manager

( NEFT/RTGS/LC/BG/SWIFT
Message Creation/Bulk Uploads  RFMS Bulk Payment Manager
/IDL/MIS Reports)
(One-to-Many/Many-to-Many )

 RFMS Risk Manager  NPCI Integrator

(UPI/IMPS/NACH/MMS/AEPS/BBPS)
 RFMS Message Signer
 NG-RTGS/NEFT Integrator
 SWIFT Integrator

• Installation , Configuration and Annual Technical Support for

Services Payment and Settlement systems
 SFMS

 CCIL

 CIMS
Payment Hub RFMS

Functional Overview
RFMS ARCHITECTURE

8
 Interface with CBS

RFMS Integration Platforms Possible Channels Possible Message Formats

 RTGS/NEFT/SWIFT/ NPCI  IBM MQ  SWIFT MT

 LDAP/AD for role-based User  SFTP  SFMS (R-Series/N-Series )

Management and Access Control
 REST APIs  ISO 8583
 SMTP/SMS Gateway
 SOAP APIs  ISO 20022
 Finacle Integrator/Connect 24
 Folder-based  File-based (.csv or any other
supported format)

 Any other standard/non-standard

Message Formats
 Payment Hub: Key Benefits
Functional Benefits Technical Benefits

One Stop Solution for all Payment and Customizable, configurable Business Workflow
settlement systems Real-time transactions and Liquidity Management
And Configurable Rules

Supports Online payment entry facility for Support ISO 20022, ISO 8583 & other
bank’s internal backoffice systems Supports message interoperability
standard/non-standard message formats

AML screening based on multiple

Interface-RTGS, NEFT, NPCI, SWIFT, PFMS etc. threat-list/Integration with Bank’s own AML System Light –Weighted application

Capable of integrating with multiple Payment – NEFT/RTGS , LC/BG and SWIFT Message Creation
settlement systems & back-office systems Modules with Message templates for repetitive Plug and Play
messages

24/7 transaction processing capability with limit

management for corporates with various rules Bulk Upload in .xls/.ods/.csv file formats and Decoupled Payment Adapters
like Name-Matching/Threshold/customer-limit . Reconciliation for Parallel processing-to achieve high TPS.

Handling Future Value Date Transactions. Actions/Alerts /notification defined over

Handling of N04 & N03 Business/Technical rules Secured

Virtual Account management Supports multiple connectivity channels to connect

Auto-Return facility to various backoffice systems

Credit/Debit Posting in CBS on the basis of Standard & Customized downloadable MIS Reports- Robust Application developed using Java – J2EE over
different rules using Enquiry/Mapper in Excel/Pdf/.csv formats along with response Bulk Spring-Hibernate framework
files & reconciliation reports
NEFT /RTGS Dashboard
NEFT /RTGS Dashboard(contd.)
Status Monitor
Various IDL/MIS Reports

IDL Reports(Daily/Monthly) MIS Reports(Daily/Monthly)

• IDL Reports (Daily/Monthly) • NEFT/RTGS/NACH Inward/Outward
Transaction volume Reports
• Volume reports

• Payments Aggregate Report

• BLR-6 Reports (RBI Format)

NEFT/RTGS - Outward Message Flow
CBS RFMS USER Rejection Report Display Error Success Response
CBS Format
RFMS Maker Creates Message And
Submits The Transaction

Rejected With
Post Cr/Dr entry RFMS APP
valid reason
SERVER
code
RFMS
Authorized Checker
Authorize/Reject Sent back to
Processor
Transaction Request RFMS Processor
for Reversal

Posting No
Successful?
Generate Message,
Yes
append UMAC and
submit to SFMS

SFMS
Settlement at Proceed for Yes Is valid No
beneficiary end Settlement format?
NEFT/RTGS - Inward Message Flow
Hold/Rejection Success Response
CBS
Post Cr/Dr entry

RFMS APP
SERVER
Credit Entry is Yes
No N07 in case of posted in CBS for
Posting Appends inward
Successful? NEFT or Pacs.004 in UMAC and
case of RTGS Transaction
post in
SFMS MQ
Yes N10 in case of
No
NEFT or Camt.059 RFMS Is Valid?
in case of RTGS Processor

Receive Message from

SFMS MQ

Credit Proceed for SFMS

Other Bank confirmation/Returns Settlement at
initiates IDRBT/RBI
NEFT/RTGS All Inward
Transaction NEFT/RTGS
received from
SFMS HUB
 SWIFT Outward/Inward Message Flow
Futuristic approach
CBS
MESSAGE INITIATION
MT Messages

Tomcat Server
Conversion to MT RFMS
Message and pushed to
CBS WebRFMS APP
MIS SERVER
Inward Fresh Response
Message
RFMS DB Dashboard
ACK/NACK

Status Monitor

Received Message from Rule Engine

SWIFT Store in DB,
Conversion to Notification Success
Message Encryption
ISO20022
and submit to SWIFT Engine Response

Other Bank
All Inward messages
received

Settlement at SWIFT
Proceed for
beneficiary end. Settlement
Payment Hub RFMS

Technical Overview
Secured
≈ Data/File encryption / decryption capability (using PGP hybrid
encryption ), AES256, Digital Certificate /Signature or any other proposed
encryption methodology.

≈ MFA using OTP, Password, Token based

≈ RFMS Application meets the audit requirements by regulatories and is

successfully audited for vulnerabilities by Cert-in Empanelled auditor –
CyberQ Pvt. Ltd. And provided compliance certificate for :

- VAPT
- Source Code Review

20 - Role Based matrix for access and control and audit trails .

- Maker Checker for User –Administration as well as transaction creation &

authorization.

- Maintaining Audit trails for users as well as transaction life cycle.

- API integration support security standards , adhering to to Bank/RBI's

security guidelines/policy
Payment Hub RFMS

Support Model
Support Model - Offsite
 The support Engineer will raise
 All the support Calls will be logged
tickets in respective vendor
by raising requests through mail,
call on provided Support E-mail ids. .Ticketing Portal like IFTAS(if
required) , and the progress will be
and phone numbers respectively
tracked and updated till its closure.

 NEFT/RTGS is 24 3  The further escalation

x 7 so is our can be done as per the
support. 1
SLA/TAT & Escalation
matrix.

22
Support Model - Onsite
 All the support Calls will be logged  The support Engineers in shift will also
by raising requests through Bank’s monitor the system in scope
internal Ticketing Portal ( 24x7x365 ).
 Bank can contact Support on  They will raise incidents in Bank’s
provided Support E-mail ids and ticketing portal, align it to respective
phone numbers respectively. vendors on either mail/vendor ticketing
 The ticket Number needs to be portal (whatever medium is decided) ,
mentioned in the mail. and track progress, update tickets in
Bank’s Ticketing portal till its closure.
2
 NEFT/RTGS is 24
x 7 so is our 3  The further escalation
support. Our can be done as per the
1
onsite resources SLA/TAT & Escalation
will be deputed matrix.
in shifts.

23
Support Model – Severity Definition
Service Levels
Severity Definition Symptoms
Application Crash, Abnormal end to EOD
Show Business Impacted severely and NO transactions
processes, Server Crash, DB crash, Application
Stopper can be affected.
server stops responding.

A particular transaction in the application does

Business and /or financials are impacted, a given
not work which severely impacts business and
High functionality is NOT working as per
financials of the company & and impacts the
expectations, but the application functions
customer financially.

Business is not impacted; a given functionality

Medium on a screen or field does not work. But the A validation on the field does not work.
application functions

Aesthetic changes or Irritants which keep

Low popping up.
A report is misaligned, a screen is not aligned.

24
Support Model – Offsite SLA
Response SLA Update of Progress SLA
Type TAT Type TAT
Low 24 Hour Low 2 Day

Medium 8 Hour Medium 24 Hour

High 1 hour High Every One Hour

Show Stopper Immediate Show Stopper Every 30 Minute

Resolution SLA
Type TAT
Low 1-2 Day

Medium 0-1 Day

High 0-4 Hour

Show Stopper 0-2 Hour 25

Support Model – Onsite SLA
Response SLA Update of Progress SLA
Type TAT Type TAT
Low 4 Hour Low 2 Day

Medium 2 Hour Medium 24 Hour

High 1 hour High Every One Hour

Show Stopper Immediate(upto 15 minutes) Show Stopper Every 15 Minutes

Resolution SLA
Type TAT
Low 1-2 Day

Medium 0-1 Day

High 0-2 Hour

Show Stopper 0-1 Hour 26

Scope
Service Scope
Products/Services
• 24x7x365 offsite support for SFMS with high level
 Payment Hub- RFMS accountability and responsibility for SFMS/CCIL/CIMS
 Support Services for RBI Application: Application.
 
 SFMS
• Remote co-ordination with IT Service Desk and
 CCIL application testing related to incident/Problem fixing
 CIMS to ensure that the solution provided is in consonance
with the user requirements and it stands closed.

• Dealing with any failures, co-ordinating with

application vendors, and implementing any fixes, to
Product Scope the Application.

• Mailing/Logging all Application faults and

 Integration with CORE Banking API for push/pull of
transactions.
 Integration with payment adapters (NEFT/RTGS)
 Maintaining payment systems data locally
 Reporting / MIS Systems
 Any Further Customization with mutual discussion
2 • All communications regarding the status of a
communicating resolution status to IT Service Desk
via ticketing portal for RBI Application (SFMS).
•  
• Assisting Bank with the recovery of data and general
recovery after any failure of the Application.
•  
production support or problem would take place
according to the Priority Levels.
27
• Weekly/Monthly Health Checkups
Case Studies
RFMS
CASE STUDY – Private Scheduled Bank
01
Challenges
 Manual data punching for
NEFT/RTGS/IFT outward bulk
transactions in CBS was a huge
challenge.
 Possibility of manual errors while
data punching.
 Individual transaction
authorization in system was a
time-consuming task.
 Monitoring and managing the
entire life-cycle of the transactions
was cumbersome.
 Business requirement for handling
huge volume in specific hours (the
demand was to process
transactions @300 TPS) manually
02
Requirement
 A scalable middleware for:
 24 * 7 Automation of
NEFT/RTGS/IFT payment
messages.
 Stream-lining bulk-
transactions
 Monitoring entire life-cycle of
the transactions.
 Handling huge volume of bulk
transactions in specific hours
with a TPS of approx. 300 and
even more.
 Reducing operational
workload
03
Solution
 RFMS Helped to compile
NEFT/RTGS/IFT 24*7 at 99%
 User manual intervention was
removed
 RFMS facilitated alerts in form of
SMS/EMAILs
 RFMS enabled ease-of
incorporating any regulatory
requirement with minimal efforts
and TAT.
 Readily available customizable IDL
& MIS reports
 RFMS was provided as an
automated , scalable , Flexible and
customizable solution
 Flexibility of handling a high TPS
with its scalable property.
38
Payment Hub Implementation At Foreign Bank
Implemented a centralized payment hub interfaces with the Bank’s Core Banking System (CBS) at Dubai with India
specific Payment System Operators (IFTAS’ INFINET for NEFT and RTGS.). Helped Bank comply with data localization.
For outward domestic payment transaction
• FLEXCUBE does accounting and handovers the domestic
payment message details in a custom format
• This domestic payment message detail is converted to RBI
prescribed format(NEFT, RTGS) and handovers the same to
RBI network
• Handles the complete life cycle of the payment message
including ACK, NACK, etc. till the completion of the
transaction
• Handles the payment reconciliation aspects.
• Provides GUI for the Payment message query and
traceability.
• User access based on the access rights. Access rights
based on Channels(FinMechanics, Finastra, Flexcube, etc),
Department(Treasury, Trade Finance, Payment, etc) and
also based on the Domestic Message Type(NEFT, RTGS).
• Handles archival and purging of payment message. 10
years of payment message data storage requirement..
For inward domestic payment transaction
• Receives the messages from RBI network (for NEFT,
RTGS) and convert the same into FLEXCBUE required
formats
• FLEXCUBE will do the accounting
• Handles the complete life cycle of the payment
message including ACK, NACK, etc. till the completion
of the transaction
• Handles the payment reconciliation aspects.
• Provides GUI for the Payment message query and
traceability.
• User access based on the access rights. Access rights
based on Channels (FinMechanics, Finastra, Flexcube,
etc), Department (Treasury, Trade Finance, Payment,
etc) and also based on the Domestic Message Type
(NEFT, RTGS).
• Handles archival and purging of payment message. 10
years of payment message data storage requirement
ACUTEC GLOBAL
SERVICES LLP

Our Clientele
At the end of the day, customer-
centric solutions are the future
Testimonials

Global Services

For more testimonials visit our web-site : https://www.acutecglobal.com/

Testimonials

For more testimonials visit our web-site : https://www.acutecglobal.com/

Testimonials Testimonials

For more testimonials visit our web-site : https://www.acutecglobal.com/

Connect for any Noida Office Mumbai Office

Queries
Sharad Pandey Chandresh pathak Timir Shah
+91-8057138698 +91-9999974091 +91-9820409603

Acutec Global Services LLP

(Formerly Acumen Software Technologies)
www.acutecglobal.com