Building Bridges One Connection at a Time
CardExchange® Bridge is used with CardExchange® Controller as an additional service to enhance the capabilities for data synchronization. With the Bridge we offer three different products. CardExchange® Bridge Local, CardExchange® Bridge Connect, and CardExchange® Bridge API. You can simplify and automate your enrollment and card issuance processes by adding the Bridge automation features for data management. Depending on how you configure your business rules and schedules, the Bridge eliminates the need to manually import data or any unnecessary work to update your data in multiple systems.
Data from your source database(s) can be automatically synchronized with the Cloud Suite applications. Card production data such as card number and status can be automatically sent to connected systems for access control, print & copy, time & attendance, cashless catering, and more.
The cloud database strictly follows the Transport Layer Security (TLS) protocol to protect data when it is traveling between the cloud services and customers. It provides strong authentication, message privacy and integrity, and interoperability, which ensures that your data is protected in transit.
The Bridge and its related services provide you with the highest data integrity and automated data synchronization for a seamless process of creating and managing ID and Card.
Having live connectors between your datasource and our cloud products is essential for keeping all systems up to date. Eliminate errors in having too many manual entries. Aside from manual work, it protects the database record integrity by making sure all system record data matches automatically without manually entering it in multiple systems.
Bridge API refers to a REST API that allows your existing systems to integrate and communicate directly with the CardExchange® Cloud applications. With the applications databases connected, you can utilize all functionalities that come with the CardExchange® Cloud Suite. The service includes access to the API, its documentation, and the professional API integration support.
Bridge Local is a local Windows service that runs on a set synchronization schedule to import data from one or more source databases into CardExchange® Controller.
It runs as an automated service on a local PC or server synchronizing data between multiple host databases and CardExchange® Cloud. Its step-by-step wizard allows you to define what data you want to synchronize and how often. This is often used for smaller synchronization jobs for only updated or newly inserted records.
Bridge Connect is a connector professional service which can be tailored for your organizations existing database(s) connectivity needs. If you have an existing back office data source you need to synchronize data to and from, we off design and development services to build connectors that meet your needs.
Bridge API refers to a REST API that allows your existing systems to integrate and communicate directly with the CardExchange® Cloud applications. With the applications databases connected, you can utilize all functionalities that come with the CardExchange® Cloud Suite. The service includes access to the API, its documentation, and the professional API integration support. Bridge API is recommended when synchronizing large amounts of data.
Our CardExchange® Cloud Suite can communicate with any database system you have available in your organization. Easy scheduling importing information into our suite back office, as well as reporting information back to connected databases including defined business logic.
The incoming connector can communicate directly with other systems using their API, preferably this would be a REST API made available by the system vendor. Incoming connectors can also communicate directly with a database hosted in the cloud, or local databases.
The incoming connector initiates the communication and reads from the source system, it then adds new insertions or updates from the data source to the records in Controller based on the business logic defined.
All communication with the incoming connector goes through the Web Application Firewall.
Our outgoing connectors are connections between the back end and external systems that send data to those systems in reaction on actions performed by the end user. Outgoing connectors should preferably use web hooks, these can be configured based on a change to the persons ID card status in Controller CMS. This means that the webhook can be sent, for example, when a ID or card is activated or blocked. The connector can then send a request via the API to get the full data for that specific record or action which greatly reduces network traffic and offers a real-time experience.
If you are interested to see how this all works, our Cloud team is happy to schedule a demo and take you to all the options, features, and possibilities of our CardExchange® Cloud Suite solution.
Provide your information in the form and we will get in touch a.s.a.p. to schedule a demo!