External Provider Integration

The Lotus platform requires some external services, and has the ability to work with multiple suppliers, giving the customer the possibility of choice. If the customer has a contract with a specific supplier not supported by the platform, it is possible to modularly implement support for a new service without affecting services already supported.

⚠️

Just a heads-up: To add support for new providers, Girasol's technical team will first need to check if the new provider meets the necessary requirements for smooth operation and then set up a development timeline.

⚠️

For any external provider, it is mandatory to provide two environments in the same versions, one for development and the other for production.

HSM Provider

By default, the platform supports MyHSM as a service provider for security operations. For the provider to be accepted, the operations listed below must be supported:

CVC Generation
CVC Validation
CSC/3/4/5 (amex) Generation
CSC/3/4/5 (amex) Validation
Key Exchange (TR-31)
PIN-Translate (Format 0)
ARQC Validation
ARPC Generation
ICC Issuer-Script Generation (PIN-change command)

Emboser Provider

By default, the platform supports Thales Europe and Thales Mexico. If a new integration is necessary, the embosser must inform the way it works (file or API) and provide a file model or API documentation.

Tokenization Provider

By default, the platform is integrated with the D1 tokenization service provided by Thales for Mastercard cards. If it is necessary to add another provider, it must be approved by Mastercard with a tokenizer/virtualizer.

Introduction API Integration