EMB Switch



Some connected coorpoerations list ...

  • Isapre Colmena
  • Isapre Masvida
  • Banco Santander
  • Multicaja S.A.
  • Dicom
  • PreviRed
  • Autentia
  • Isapre Consalud
  • Isapre Cruz Blanca
  • Isapre Banmedica
  • Isapre Vida Tres
  • and others




  • Secure and real-time POS/ATM/EFT transactions processing.
  • Secure and real-time Bill Payments transactions processing.
  • Stand in supported
  • Standard ISO 8583 (87, 93, 03) supported. Also customized ISO 8583.
  • Integration with business partners
  • HSM Supported
  • Integration with different systems within an enterprise
  • Over 100 different endpoints which allow the switch to connect to almost any kind of connections: Queue, TCP-port, HTTP, HTTPS, SMTP, POP3, SFTP, WS-Soap, WS-REST etc.
  • Over 60 ready-to-use Enterprise Integration Patterns (EIP)
  • Fast implementation
  • XML-based route definition
  • Full level administration - dash board as high level monitoring
  • Drill down administration - each transaction can be viewed and analyzed, input, output, elapsed time etc.
  • Real-time notifications, including SNMP integration
  • Persistent or no persistent transaction registering - no transaction will be lost even crash the system.
  • Wiretap audit log - Asynchronous audit log database registering which prevents slow-down switch's performance
  • Together with EMBFileTransfer a full functional payment switching solution can be build in very short time.







EMBSwitch stands for Enterprise integration patterns Message Based Switch. So, just as its name implied, it's a message based switch. It is also could be used as a synchronized no messages switch.


The birth of EMBSwitch was a prototype payments switching system for a chilean POS based payments switching company, Multicaja S.A. to replace its old switch which had a lot of failures and lack of proper support.

EMBSwitch enables financial institutions and processors to realize on-line transactions validations and authorizations, just like Multicaja which has over 20,000 POS. EMBSwitch also allows an enterprise or middle size company to integrate with its partners and/or its different systems.

EMBSwitch is a key component to do any kind of integration. Click here to see EMB Switch usage examples.


Differences Between RPC (Stop and Wait) and EMB Switch


The big difference between a EMB (Enterprise integration patterns Messages Based) switch and a RPC (Remote Procedure Call which includes synchronous web service call) Switch is the EMB Switch is build with failure consideration in its design. And a RPC switch is generally with perfect condition in its design. Any transaction entered into the EMB Switch will be registered persistently and the RPC switch will generally not. So, for an EMB Switch, when a failure occurs, transaction can be reprocessed lately and a RPC switch will simply start everything from the beginning.

This feature allows the switch company to handle any customer complain in a much better way. Because an exact result of any transaction can be obtained from the switch, so the exact reason can be told.

For a RPC based switch, a failure of switch, or a network link failure, hundreds of transactions in the switch will be lost without knowing their status of process and obviously can not tell in which status they are on.


High Level Architecture of EMB Switch

Diagram 2 - High Level Architecture of EMB Switch - With StandIn Database


The basic role of a switch is to route transactions to their proper destinations. Diagram 2 shows there are three types of transactions, green, red and gray. Each of them will be processed by predefined path.


The EMB Switch Core is queue manager. Each transaction will be converted to a message and then enqueued into a queue. Then the message will be dequeued and then routed to its destination Transaction Authorization Company (TxA).

Another core components are Java Message Service (JMS) and Enterprise Integration Patterns (EIP) Implementation which allow higher level components to orchestrate different transactions in easy way.

Monitoring and Administration

For each process step of a specific transaction, an audit record will be registered into the Audit Database. The record is generated and save through an audit queue asynchronously. By this design, the perform of the core of switch will be not affected by the audit activities.

The audit database will not only be used by the auditor of switch but also used by monitoring team and help desk staffs. The user's role will be used to make decision which data will be retrieved to that role.

Just as shown in Diagram 1 and Diagram 2, the switch can be build easily to different usages. Diagram 1 shows a EFT switch without any local StandIn database, so each transaction will be handle 100% online. The switch shown in the Diagram 2 has a StandIn database which can process certain transactions locally.

Monitoring - Screenshot

Monitoring - Dashboard

Diagram 3 - EMBSwitch Monitoring Dashboard

EMBSwitch Monitoring Dashboard provides a high level overall view about the Switch. As shown in the Diagram, the TxO companies are located at top of screen, which are renamed as Service Payments Collection Companies. And in the middle, the overall status of EMBSwitch are displayed. And at the bottom, the TxA companies overall status are displayed.

Monitoring - Drill down Display

Diagram 4 - EMBSwitch Monitoring Drill down Display

For each TxO, TxA and EMB Switch, transactions can queried and to see what and how are handled by the EMB Switch. Just as shown in the Diagram, for a specific transaction at specific point of route, several critical information can be obtained: status, elapsed time of processing, returned data etc.

With help of these information, auditor can know what is exactly done. For the monitoring team, they see the performance of the switch. For the Help Desk staff, they can answer customer's complains about their specific transaction.

Questions, feedback, suggestions? We would love to hear from you!