POS terminals
A payment kernel inside an application for contact and contactless card acceptance.
JoinCORE · Payment EMV kernelAt the heart of payments.
At the heart of payments.
Inside your
product.
A payment kernel developed by MST Company for POS terminals, SoftPOS, validators and ATMs. Embed EMV logic in your application and build on your own platform.
Modular architectureC++ + Lua
Payment applicationRuns on Android
EMV 4.4 supportCard payment logic
C++ / Java integrationA component for your application
Dynamic kernel loadingUpdate without rebuilding the application
Where JoinCORE worksDifferent devices.
Different devices.
One payment foundation.
EMV logic is separate from hardware. Hardware interfaces are implemented during integration with your platform.
SoftPOS
Contactless payment acceptance in an Android mobile app.
Validators
A component for integrating card payments into transport equipment.
ATMs
EMV logic integrated with the device application and hardware.
Product architectureThe kernel changes.
The kernel changes.
App
keeps running.
The main JoinCORE layer is written in C++, while payment scheme kernels use Lua. This modular approach allows kernels to be loaded and updated without rebuilding the client application.
- A separate payment logic component
- Interfaces for the reader, PIN pad and cryptographic system
- Dynamic loading of additional kernels
Your application
C++ / JavaLogic and interface
EquipmentReader · PIN pad · Cryptographic system
↕ Integration interfaces
JoinCOREC++
Modular layerLua
ContactMasterCardVISAMIRJCB…
Kernel capabilitiesAll the logic.
All the logic.
Controlled by your application.
From card communication to processing results, with parameters for your payment workflow.
Payment acceptanceContact. Contactless.
Contact. Contactless.
Tokenised cards.
Work with cards and tokenised payment data within your application.
- Contact and contactless interfaces
- Tokenised cards on devices
- PIN-free payments within payment scheme rules
EMVCard interface
Contact / Contactless
Authentication and CVMFlexible verification.
Flexible verification.
For your use case.
Kernel features let you configure authentication and cardholder verification for your terminal and payment scheme requirements.
- Online issuer authentication and online PIN
- Offline SDA / DDA / CDA authentication
- Offline PIN and consumer device cardholder verification (CDCVM)
CVMCardholder verification
Online / Offline
Parameters and resultsControlled parameters.
Controlled parameters.
Clear results.
Amount, currency, transaction type and kernel settings define processing. The application receives the result and data for further operations.
- Verification limits and settings for the selected kernel
- Transaction result and EMV data for authorisation
- Interface messages and logging
DATAData for the application
Settings → Result
Features depend on the payment scheme kernel, hardware and agreed configuration. Support for tokenised cards does not imply that every payment wallet is available in every country.
Payment kernelsMajor and regional schemes.
Major and regional schemes.
One architecture.
Select the kernels for your countries of operation, payment schemes and target devices.
EMVCo Contact
Contact interfaceMasterCard Contactless
Major scheme kernelVISA Contactless
Major scheme kernelAMEX Expresspay
Major scheme kernelJCB J/Speedy CTL
Major scheme kernelDiscover D-PAS
Major scheme kernelUnionPay QuickPass
Major scheme kernelMIR
Major scheme kernelClever
Regional scheme kernelBancomat (Italy)
Regional scheme kernelCPACE (Europe)
Regional scheme kernelEftpos (Australia)
Regional scheme kernelGiroCard (Germany)
Regional scheme kernelIdemia WISE
Regional scheme kernelInterac Flash (Canada)
Regional scheme kernelMADA (Saudi Arabia)
Regional scheme kernelNPCI RuPay (India)
Regional scheme kernelThales PURE
Regional scheme kernelThis kernel is not in the published list. Let’s discuss your project requirements.
Showing all 18 kernels
Discuss delivery scope →The catalogue reflects the published JoinCORE list. Certification status for a specific kernel and hardware combination is confirmed for each project.
Platforms and portingYour hardware.
Your hardware.
Your environment.
JoinCORE is used within an Android payment application. Its C++ architecture allows the component to be adapted to other target platforms.
Check your platform →
Current deployment scenario
In useAndroid · ARM
Within a payment application
Windows / Linux
x86-64Elbrus
E2KBaikal
ARMTarget platforms from the published description. Porting requires a compiler with C++11 support (ISO/IEC 14882:2011) and adaptation to the project's hardware and environment.
For your development teamEmbedded in your solution.
Embedded in your solution.
Under your control.
Integration components are available for C++ and Java. We will agree the delivery format and interfaces for your platform.
Implement the interfaces
Create classes inheriting the library interfaces to communicate with the reader, PIN pad and cryptographic system.
Configure the kernel
Define the payment kernel set, terminal parameters and transaction workflows.
Process the result
Call kernel methods at the appropriate stage of card interaction and use the result in your payment application.
Component / Library
Embed JoinCORE in your application. Additional kernels can be loaded dynamically.
Standalone application
By agreement: a target platform application exchanging asynchronous messages, including through sockets.
APIs for your project.
API and protocol documentation is provided in an agreed format.
Request the integration package
Documents you can verifyCredentials.
Credentials.
With verifiable details.
Mir payment system documents and state software registration.
Open document ↗
MIR · Contactless kernel
Certification testing
MIR1023-S230-TP231JoinCORE 1.1 · WIZARPOS Q2.
Identifier valid until 13 February 2027.
Open document ↗
MIR · SoftPOS / TapOnPhone
Certification testing
MIR1048-S230-TP232-SPJoinCORE 1.1.
Identifier valid until 7 March 2027.
Open document ↗
State registration
Software registration certificate
№2023619580JoinCORE computer program registration.
View original ↗
The MST Company ecosystemThe foundation of our
The foundation of our
payment solutions.
JoinCORE runs within MST Company payment products. Start with the kernel or discuss a complete application.
Product resources
JoinCORE documentation.
Features, installation and operation. Ask our team for the current package for your platform.
Before integrationPractical
Practical
questions.
We will discuss the technical requirements and solution scope with your team.
Is JoinCORE a complete payment acceptance application?+
JoinCORE is an embedded payment component. It handles EMV logic; the user interface, hardware integration and subsequent data processing are implemented as part of the solution. Consider JoinPOS for a complete application.
Can kernels be updated without rebuilding the application?+
The modular C++/Lua architecture supports dynamic loading of payment scheme kernels and updates without rebuilding the client application.
How do we choose the platform and delivery format?+
JoinCORE is currently used in an Android payment application. Other environments require agreement on porting, hardware interfaces and delivery format: a library or a standalone application with message exchange.
How is pricing calculated?+
Pricing depends on the configuration and is calculated individually. We will need to discuss the target platform, hardware and payment kernel set.
Let’s start with your payment solutionIntegrate the kernel.
Integrate the kernel.
For your needs.
Tell us about your application, hardware and payment workflows. We will discuss the architecture, integration package and JoinCORE delivery scope.
01 Platform and hardware02 Payment schemes and workflows03 Integration and configuration
This email address is being protected from spambots. You need JavaScript enabled to view it.
Loading the contact form…