You are here

eRoute

presentation | white paper

The eRoute bundle is a lite but powerful on-line transformation and routing engine, born as a response to the French requirement to have a low-cost solution to talk to Visa and MasterCard networks while keeping the French native e-RSB protocol. Special thanks are to the SEPA initiative, for acting as a catalyst of the interest to low-cost but flexible on-line routing systems. e-Route is also able to transform on-line various POS protocols, as well as to act (in 'industrial' mode) as an engine for stand-alone CAT machines and kiosks

eRoute works with messages having ‘tree-structured’ architecture, i.e. where:

  • every message consists of one or more fields
  • every field has its own value
  • every field has its own unique identifier
  • every field could have one or more sub-fields
  • every sub-field could have one or more sub-sub-fields and so on, sub-field nesting depth is not limited
  • every sub-field has its own unique identifier on its nesting level

 

eRoute in banking

eRoute fits very well into the composition built around the request/response techniques, like bankcard authorization and single-message processing.
Most of bankcard-oriented messages have very similar logical datasets so they could be converted one into the other and vice versa, in quite a general manner.

eRoute adapters

We define two categories of eRoute adapters – incoming and outgoing.
Every adapter serves its own particular task and protocol, for example,

  • universal XML file adapter
  • Microsoft Queue Manager adapter
  • APACS family adapters
  • MasterCard V5 adapter
  • VISA BaseI / SMS adapter
  • BPEL Web Service

The collection of standard adapters is growing quite fast and we are ready to adapt the existing or develop a new one for individual client conditions.

 

The detailed information about the current adapters is available upon request. Contact info could be found at the end of this page.

eRoute technology.

eRoute is a pure Java application. It uses JMS as a transport with Sun Java System Message Queue.
We built our own macro language – MPL – to be flexible but simple in definition of any complex message routing and transformations.

The logical schema of how the system works is presented below:

base scheme

Where

  • IN Gate – a module to interface the source of ‘incoming’ messages – ATM or POS concentrator, for example
  • OUT Gate – a module to interface one of the target bankcard networks like Visa or MasterCard
  • SWITCH – a module, responsible for router logic

The system could have multiple IN and OUT gates, as well as the secondary switch set (in dashed rectangle) could also be attached to the system.