Crimson™ Issuer:

The Crimson™ Issuer enables a party/company managing funds to receive Acquiring parties’ transaction requests and manage the funds as the Issuing party owning the funds/account.

Crimson™ Acquirer:

The Crimson™ Acquirer enables bespoke applications of the ISO 8583 protocol in the financial context where the Acquiring party like a Merchant needs specific implementations around the protocol executed. As the Acquirer, Crimson™ will connect to the Issuing party and request transactability. Hence, Crimson facilitates both models required in the exchange of financial transactions.

Crimson™ Switched:

Crimson™ as a Switching service enables multiple parties connected to the switch to route their transactions across currencies and message formats enabling the implementation of different ISO 8583 protocols in one instance to effectively execute transactions.

Crimson™ also enables the conversion of currencies in international remittance and the exchange of Settlement messages to online messages and Batch files to ISO 8583 messages as an example.

Crimson™ is readily employed for last mile integrations

Crimson™ is a cost-effective and more agile alternative to last mile integrations to POS with large systems like Postilion. Crimson™ complements Postilion as it seamlessly integrates between Postilion and all POS systems to facilitate financial transactions.

Often times a company has an existing solution, having done the full Postilion journey, and in the diversification strategy needs to roll out to various Points Of Sale in (POS), adding time and cost to the process. PMT works with Postilion often and can facilitate this leg of the journey.

Translate Message formats in real-time.

Crimson™ has the means to translate transactions information from one format to another, in flight, in real-time. The benefit is to both switching parties, having the switch do the hard work, legacy systems do not need to alter their systems and formats to integrate to another party.

Translating between ISO 8583, JSON, XML, SOAP, and other formats can dynamically be mapped in the integration phase while keeping to the transactional best practice format of ISO 8583 to match expected standards and procedural requirements for transacting.