Tieto Card Suite integration with Core Banking platform

High Level Solution Design

Financial Services
Cards

Tieto Card Suite integration with Core Banking platform

This document describes high-level proposed integrations approach and involved solutions
responsibilities.
Picture below denotes involved solutions/parties and interfacing between them. Current
document just describes the interfaces associated with Card Suite.

1 Short interfaces description

Id

Type

Description/comment

Real-time

Web-services based interface according to Tieto Card Suite specifications

that would ensure card account agreement creation/update and all associated
information(including approved/declined authorizations, etc) inquiry

Real-time

On-line interface to pass authorization from Card Suite to Core Banking

platform to perform balance check e.g., availability of funds.

Real-time

Online interface to international card organization(-s) or local

schemas/processors to receive card authorizations requests in accordance to
particular card organization specification.

Batch file

Card transactions data passed from card organizations to the issuer in

accordance to particular card organization specification.

Batch file

Card transactions data passed to core banking platform with details enough
for statement printing, etc

Batch file

Card personalization data for personalization bureau

page 1/3

2015
Tieto Corporation

Tieto could offer native transactions export specifications

V1.0d
Confidential
2015-06-22

Tieto Card Suite integration with Core Banking platform

High Level Solution Design
Financial Services
Cards

2 Debit card solution

2.1 Card creation, maintenance, closing
Core banking platform (CBP) would maintain customer data and its accounts including current
account and its balance.
To open card(-s) for account CBP would use Tieto Card Suite (TCS) web services passing
information about customer, card delivery address etc and would receive unique id(token) that
corresponds to generated card number. This token further could be used to suspend/block card,
update card related information etc.

2.2 Authorisation processing

TCS would be primary system that would receive authorization initiated by card via VISA or
MasterCard.
Card Suite would be responsible to execute technical authorisation e.g.,

Checking of: PIN, CVV, CVV2, Cryptogram verification

Execution of Post-issuance scripts

Validation against stop-list

Fraud prevention checking

In case of successful technical authorization TCS would pass authorization to CBP that would
perform financial authorization e.g., availability of funds and control of spending limitations (per
week, month, day etc).
In case of positive response from CBP there would be lock id returned that would identify hold
associated with this authorization within CBP.

2.3 Transaction processing

TCS would be primary source that receives card transactions from networks. Upon transaction
processing TCS would perform transaction matching with previously captured authorizations to
be able to find corresponding authorization lock id that would be passed along with basic
transaction data to CBP to ensure correct financial processing.

2.4 Statement generation

CBP would be responsible for statement generation towards customers.

2.5 Fees calculation

At this moment it is assumed that CBP should cover card lifecycle fees calculation and
transactions fees calculation. If required TCS also can ensure this functionality.

page 2/3
2015
Tieto Corporation

V1.0d
Confidential
2015-06-22

Tieto Card Suite integration with Core Banking platform

High Level Solution Design
Financial Services
Cards

2.6 User Interface to ensure debit card servicing

It is assumed that CBP using TCS web services would ensure all basic user interface operations
required to maintain/serve debit cards. For investigation etc TCS native web based UI will be
available.

page 3/3
2015
Tieto Corporation

V1.0d
Confidential
2015-06-22