IXOPAY Features

Protects data with within or as it leaves your secure or local network.

Provide a level of encryption of data in transit, protecting sensitive data while it lives in the backup application.

Provides a level of encryption for text documents.

Allows administrators to set multi-factor authentication requirements including tokens, keys, or sms messaging

Abilities to set standards for database security and risk management.

Allows administrators to set user access privileges to permit approved parties to access sensitive data.

Meets GDPR requirements for pseudonymisation under the Data Protection by Design and by Default requirements.

Meets de-identification requirements under the CCPA.

Stores data remotely, on-premise, or in cloud databases in case of recovery during disaster.

Decrypts datasets or files or allows users access to a backup database for reintegration.

Allows administrators to set levels of encryption for file types. Allows administrators to decide which files to encrypt.

Monitors activity within networks and alerts administrators when unusual activity occurs.

Logs and stores multiple copies and versions of master keys.

Implements a key hierarchy with a local data encryption key (DEK) and a key encryption key (KEK).

Allows administrative control over automated tasks related to key management, storage and distribution.

Offers traditional static de-identification (also known as consistent replacement), where the pseudonymized data uses the same pseudonyms across multiple data sets. For example, John Smith is replaced with Robert Fox and the Robert Fox name is used multiple times. This type of pseudonymization carries some risks of re-identification if paired with enough datasets.

Offers dynamic de-identification (also known as random replacement), where the pseudonymized data uses different pseudonyms across multiple data sets. For example, John Smith is replaced with Robert Fox once, and then the next time the data is used the name changes to Michael Jones. This type of pseudonymization carries lesser risk of re-identification if paired with many datasets.

Offers methods to de-identify large volumes of data using batch files.

Documents access and alterations of the database for analytics and reporting.

Supports compliance with PII, GDPR, HIPPA, PCI, and other regulatory standards.

Provides Administration tools/console that are easy to use and learn for routine maintenance tasks.

Reports and analytics created from payment data.

The ability to integrate directly with an e-commerce platform in order to create a seamless checkout experience.

Fees associated with processing individual transactions that may be based on a percentage of the purchase or a flat rate.

The ability to integrate with a POS system in order to allow the processing of credit card or mobile payments in a store setting.

Process payments from multiple channels such as ACH, mobile, or e-commerce.

Supports levels 1 and 2 for credit card payment processing.

Supports level 3 credit card processing which requires additional data for qualification.

Integrates with third-party software to provide other features and expand functionality.

Integrates with major cloud service provider offerings for simplified management and distribution.

Supports key distribution across multi-regions to increase availability.

Expands functionality while maintaining balanced loads. Serves growing demand without reducing functionality.

Built-in security to protect payment information in order to prevent fraud and hacking.

The ability to process credit card payments and receive approval or denial of funds from the customer's bank.

The ability to process mobile payments from a mobile wallet or other mobile phone payment app.

The ability to process payments from a digital wallet service or other digital payment method.

Connects to mobile platforms using a mobile SDK.

Offers APIs to connect products.

Allows users to process payments in multiple currencies.

Provides an online portal where customers can make payments.

Support cardholder verification methods for POS transactions.

Provide integration with accounting software and ERP systems.

Provide integration with B2B and B2C e-commerce platforms

Deliver application programming interfaces (APIs) to integrate payment solutions easily

Suppoprt payment orchestration layers (POL) to unify multiple types of payments from different providers

Provide built-in integrations with payment gateways and payment processing solutions

Validate payments before processing to determine the best routing options

Define and manage automated payment processing, from authorization to settlement

Support cross border and international payments for B2C and B2B

Include multiple routing options for payments that can be customized by users

Compare payment transactions with bank statements and financial records

Re-route failed payments to alternative payment processing options

Use tokens to protect payments data by replacing it with data generated by algorithms

Comply with privacy and security regulations such as PCI and PSD2

Centralize payments data from multiple sources such as gateways or payment service providers

Use payments data to improve processing and success rates, as well as reduce costs

Identify suspicious payers and analyze fraudulent transactions

Allows users to generate text based on a text prompt.

Utillizes AI to monitor and report on incidents in real-time.

Capability to perform complex tasks without constant human input

Ability to break down and plan multi-step processes

Capability to perform complex tasks without constant human input

Works across multiple software systems or databases