The entirety of this Web site is copyright © 2007, ACI
Worldwide, Inc.
|
|
Transaction Switching and Routing
|
The channels in to and out of ASx are configured dynamically using
the ASx user interface. Channels can be added, deleted and modified by a suitably
qualified user, without directly effecting the existing processing of the system.
In addition, the routing decisions are configured in a similar way. Routing from
one channel to another is based upon:
|
|
The Primary Account Number (PAN) or Bank Identification Number
(BIN) (track 2, track 3 and ICC).
|
|
|
The transaction type.
|
|
|
The terminal or merchant identifier.
|
Transaction messages can be automatically reformatted and re-encrypted
as they flow through ASx.
Should the selected route not be available, ASx permits multiple permutations of
actions, which include:
|
|
Secondary and tertiary destination routing.
|
|
|
Stand-in authorization against specially defined rules (only applied
if the route is not available).
|
|
|
Notification options allowing the route to be subsequently notified
at a later date by an advice transaction issued by a Store And Forward mechanism.
|
To ensure transaction delivery, ASx will select the interface that
is available at the moment of routing. This means that, if due to a software failure
or maintenance activities, the interface configured in the selected node is not
active, the transaction monitor will look in the network for the next interface
available in other node and re-route the transaction to this one.
ASx Store-and-forward supports a message driven interface to the target host system.
The forwarding of stored transaction data can commence when the host connection
re-establishes and the host notifies ASx of its availability or when ASx successfully
polls the host. The resynchronization can be further controlled by time and frequency
of activities.
|
|
|
