Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Introduction

aplonHUB™ is a fast and simple way for banks to add financial messages routing functionality, to existing legacy systems. Its light footprint and extensibility make it ideal hub for banks of any size to manage and route messages such as SWIFT, ISO20022, SEPA, TARGET2 or local.

It can function either as a standalone solution or as a fully integrated with the existing core systems. The interfaces provided can be used directly by core systems to manage and route Credit transfers, Instant credit transfers and Direct Debits, with minimal impact on the back-office system, since you will not need to implement complex logic directly in the legacy system. Its routing and scheduling features will simplify your operations and will add the necessary control to your payments process.

aplonHUB transacts with the core banking or legacy payment systems in a number of methods to handle all the advanced routing and message transformation needs.

  • It performs all the needed transformation and validation of your SWIFT, ISO20022, SEPA, TARGET2 or local messages before and after the connection with the Swift Alliance or Service bureau.

  • It integrates seamlessly with external AML systems to guarantee compliance.

aplonHUB™ Features

Functional

  • Parse and store incoming and outgoing MT, ISO20022, TARGET2 and SEPA messages

  • Handles Credit transfers, Instant Credit transfers, Direct Debits.

  • Checks and validates all messages and generate alerts where appropriate

  • Alerts on erroneous messages are highlighted in separate views where operator can review

  • Supports reach search capabilities on archived.  Search is done on dates, status or message contents.

  • Ability to display all SWIFT MT messages parsed.

  • MT messages can also be exported as well defined and user-friendly PDFs.

  • It correlates related messages (e.g. MT19x, MT9x against payment messages) and displays side by side for easy of reconciliation.

  • Incoming MT300 and MT320 are compared with equivalent outgoing messages. The differences between the two will be highlighted.

  • Ability to automatically generate reply/request for cancelation/returns/Rejects for SEPA or ISO20022 messages

  • Integrates with SWIFT ACKs/NACKs

  • Connects with external AML systems and bypasses messages according to rules

  • Generates the Universal Confirmations via MT199 for incoming MT payments

Security & Auditing

  • Role based access control (maker, authorizer, viewer, administrator, AML officer)

  • Audit log availability with extensive search on date, object, action or user.

  • Local Authentication (LAU) is implemented as recommended by SWIFT in order to provide integrity and authentication and to protect files in transit between the application and the AutoClient.

Non-functional

  • Modern and user friendly UX/UI

  • Secured by design (three tier)

  • API architecture by design

  • High availability by design

Components & subsystems

Basic ingredient of aplonHUB are the SWIFT MT, ISO20022, CBPR+, TARGET2 and SEPA libraries of PaymentComponents. These libraries are updated annually as the new rules and validations are published by the controlling authorities every year. At these times, a newer release of aplonHUB is published and distributed.

aplonHUB depending on the functionalities supported, includes the relevant subsystems and components. See below the list of the subsystems available.

  • SWIFT MT payments

  • SEPA credit transfers

  • SEPA Direct Debits

  • SEPA Instant payments

  • ISO20022 TARGET2 payments

  • ISO20022 CBPR+ migration of MT payments

Technical specifications

  • aplonHUB™ is a Java based web application, which can be deployed using any J2EE compliant application server or servlet container (e.g.: JBoss, Tomcat, Websphere).

  • It supports all leading RDBMSs, including MySQL, Oracle, and SQL Server (preferred).

  • Requires Java 8 and above.

  • Clients can access the application from any web browser

aplonHUB User Manual

aplonHUB provide a variety of distinct roles. Each role has specific permissions in the platform. This way actions can be distributed to various users with different levels of access.

These roles are:

  • Admin

  • AMLOfficer

  • Authorizer

  • Maker

  • Viewer

  • Start/Stop Scheduler

  • Direct Debits Config

Admin:

The administrator of the system has access to the configuration of the system. He/she is provided with access to the system properties which can be edited. Through the basic system properties for example the global configuration is available ( interconnections with  SFTP, FTP, MQ, BICs, password policies).   Through the custom system properties the option of customized configuration for different clients is given.

From the schedulers and their settings the user can configure:

  • The input/ouput folder

  • Emails to notify on process end

  • Fle pattern for the files to read (i.e *.csv)

  • Configure the scheduler execution

  • The AML status and its name can be edited

The user also has access at the users of the system. From this menu he/she can:

  • view the users

  • edit roles

  • enable/disable user

AML Officer:

The AML Officer has access to both incoming and outgoing messages (SEPA and MT).

From the Incoming and Outgoing menus the following actions are available:

  • View SEPA messages and their details, view files and change the AML status

  • View MT messages and their details, view files and change the AML status

  • Search messages

  • View File logs

  • Change the AML status 

Authorizer:

The Authorizer Officer has access to both incoming and outgoing messages (SEPA and MT).

From the Incoming and Outgoing menus the following actions are available:

  • View SEPA messages and their details, view files and change the AML status

  • View MT messages and their details, view files and change the AML status

  • Search messages

  • View File logs

  • View all the pending transactions waiting for authorization. Note that the user who authorize it should be different from the user that initiate the action

  • Use the Custom Notification setup events to send notifications from the schedulers, like when a rejection received send an email

  • Add rules to be handled by the schedulers. For example when the amount is greater than 100 then do a specific action

  • Add holidays so that to avoid scheduled runs

  • Use Audit Trail  to watch  for actions that happened on a transaction. For example bulked, debulked, authorized, etc

  • Can pause or resume a pending outgoing transaction, from the Pending → Outgoing menu

Maker:

The Maker role has access to the:

  • View SEPA messages and their details, view files and change the AML status

  • View MT messages and their details, view files and change the AML status

  • Search messages

  • Recall outgoing payments (requires authorization)

  • Return incoming payments (requires authorization)

  • View File logs

  • View alerts

  • View all the pending transactions waiting for authorization. Note that the user who authorize it should be different from the user that initiate the action

  • Create payment

  • Use Audit Trail  to watch  for actions that happened on a transaction. For example bulked, debulked, authorized, etc

Viewer:

The viewer role has access to the:

  • Outgoing/incoming menus

  • Pending

  • Security

From the Incoming and Outgoing menus the following actions are available:

  • View SEPA messages and their details, view files and change the AML status

  • View MT messages and their details, view files and change the AML status

  • Search messages

  • View File logs

  • View at the outgoing messages all pending transactions that will be picked up by the next outgoing scheduled run

  • Use Audit Trail  to watch  for actions that happened on a transaction. For example bulked, debulked, authorized, etc

Start/Stop Scheduler:

The Start/Stop scheduler role has access to:

  • Outgoing/incoming menus

  • Pending

  • Configuration

  • Security

From the Incoming and Outgoing menus the following actions are available:

  • View SEPA messages and their details, view files, and change the AML status

  • View MT messages and their details, view files, and change the AML status

  • Search messages

  • View File logs

  • View alerts

  • View at the outgoing messages all pending transactions that will be picked up by the next outgoing scheduled run

  • Can configure the scheduler executions

  • Use Audit Trail to watch for actions that happened on a transaction. For example, bulked, debulked, authorized, etc

Direct Debits Config:

The Direct Debits Config role has access only to the "SEPA DD Config" menu.

From this menu the user can:

  • Perform all the operations of the Creditors List, whose content is necessary for setting up SEPA Direct Debits.

  • Can whitelist Creditors for SEPA Direct Debits configuration.

See below sample screens and explanations on their functionality.

Incoming/Outgoing menus.

SEPA tab:

The user in this tab has access to the list of the incoming SEPA messages, the file log and alerts.

Using criteria such as date, tags and other searching messages is made simple.

Files are expandable to display the messages they contain and their details (the same apply to outgoing too).

At SEPA by selecting a file the user can view detailed information

Details like:

  • Bulk SN

  • Message Name ID (i.e camt.027)

  • Settlement Date

  • Message ID

  • Total amount

For each message available details can also be viewed. Details like:

  • Transaction SN

  • Transaction Id

  • Transaction status

  • Amount

  • The creditor's account

The user has the option to export the files, bulks and transactions in PDF or excel report.

Example of SEPA tab usage:

SEPA payments list and details

This is a list of outgoing payment files (similar for incoming).

A payment file (outgoing or incoming) can contain more than one messages.

Any message can also contain more than one transaction

In each of the transactions the user can view its detailed information.

 

Outgoing payment is returned

An outgoing pacs.004 that has been returned with a reason code.

By opening the details of the transaction, we can also view the incoming message related to the original transaction.

Return of incoming payment

An incoming pacs.008 that can be returned with a reason code.

We can select a reason code from the dropdown menu.

Click on the "Return payment"

Select a return code in order to send it back to the sender. The payment is marked as “To Be returned” until the action is approved and executed.

These actions that require authorization by another user appear in Pending > Authorizations

After the return action has been authorized by another user, a task scheduler will take action and create an outgoing file (in this case a pacs.004) related to the original message (pacs.008).

MT tab:

Expanded SWIFT MT messages with user friendly tag names. Audit trail of all actions performed by users on the message is always available.

If the message has a reply message, then this will be displayed side by side.

Search tab:

At the search messages tab the user can search messages using the following criteria:

  • Date

  • Transactions status (received, settled etc)

  • Debtor IBAN

  • Creditor IBAN

Alerts tab:

Alerted messages are displayed in a separate view for better handling. The user can export the alerts in PDF or excel format.

Pending tab:

The Pending menu organizes the payments in two categories. Outgoing that are payments which are ready to be sent and Authorisation that contains payments which a user must manually check and approve before they are sent.

The outgoing tab provides the user with the option to export the file in pdf or ecxel format. 

An authoriser can also PAUSE a ready to go transaction for later. By selecting the Paused option in the dropdown above the list you will be able to see the paused transactions. Those transactions will be ignored by all schedulers until an authoriser choose to RESUME this transaction (see the bellow screenshot)

Create Payment

If necessary, a payment can be manually created by a user (with a role that allows him this action) from the Create payment menu.

The user will have to enter the necessary information.

  • For payment information:

  • Transaction ID

  • End to End ID

  • Settlement Account

  • Settlement Date

For Debtor information:

  • Name

  • Adress

  • Country code

  • IBAN

For Creditor Information:

  • Name

  • Adress

  • Country code

  • IBAN

  • BIC

  • Remittance Information (Unstr)

Configuration Tab

Configuration menu provides options for the setup of system settings (basic and custom that increase the user experience), AML statuses, scheduled tasks, notifications, rules regarding actions depending on custom conditions and holidays are configurable by the administrator.

Security Tab:

Audit Trail Tab:

User roles with access at audit trail screen have the ability to search using criteria. For every action, the actor the time and the context are recorded.

Users Tab:

Users with access at the users tab can enable/disable a user and search for a user using criteria such as:

  • E-mail

  • First Name

  • Last Name

  • Role

  • No labels