PayStorm provides a complete fuel payment management solution supporting fuel station operators, payment acquirers and fuel card issuers.

PayStorm manages fuel cards within its standard financial instrument framework. The essential controls over product codes has been implemented generically, enabling each fuel scheme to use its own code set.

Full authorisation of fuel card transactions can be supported against PayStorm’s financial accounts or alternatively, transactions can be preprocessed and switched out for financial authorisation by the issuing scheme.

Multiple fuel related protocols are supported, such as IFSF and EP2 Fuel, enabling PayStorm to acquire, authorise, preauthorise and switch fuel based transactions regardless of the technologies involved.

Fuel stations can be managed individually or they may be grouped to form larger retail groups. Station onboarding and management can be controlled via PayStorm’s merchant dashboard, via API/network requests or via a batch load mechanisms. Station management options provide control over accepted cards types, financial limits, terminal configurations and cutover settings.

PayStorm fully supports the EP2 acquirer protocol, including COI for dynamic merchant and terminal configuration via the service centre.

PayStorm provides full authorisation against accounts and financial data held within its dynamic business objects. PayStorm manages individual accounts, joint accounts, family groups and corporate accounts, where the associated business rules used in managing card programs can vary from issuer to issuer.

Card products can be defined to meet the requirements of any program through PayStorm's product dashboard, where usage controls and limits may be set as product defaults. Cardholders may sometimes be permitted to change certain aspects of the default configuration using mobile apps or online banking portals. PayStorm supports this whenever required through exposed APIs which are made available to the appropriate systems.

PayStorm manages instruments over the full lifecycle, for example, card issuance, shipping, activation, blocking due to loss, theft or fraud, expiration, replacement cards and temporary card issuance are all supported lifecycle events.

Cards issuance can be managed via the customer dashboard, via a service request or via a batch load mechanism.

PayStorm's comprehensive customer support dashboard enables helpdesk operators to manage customer interactions.

PayStorm is PA-DSS certified and all PCI relevant data management complies with the stipulated PCI rules, including SAD storage and key management.

PayStorm fully supports issuance of Visa and Mastercard EMV card products, including Visa VTS and Mastercard MDES tokenisation. Step-up authentication is defined to meet the issuer’s requirements and options can include SMS messaging, email and call centre interaction using data held on PayStorm.

PayStorm processes all tokenised card channels including Apple Pay, Android Pay, Google Pay and Samsung Pay.

PayStorm simplifies the process of customer onboarding by providing APIs to support the direct signing-up of customers and KYC processing.

The customer onboarding workflow is defined to meet the program requirements using the PayStorm Instant dashboard and the program is then activated.

Customer data is simply added using mobile-first app solutions, where the necessary data is captured and verification processes are performed following the program workflow. PayStorm workflows support direct SMS and email generation, document uploading, online identity or address verification checks, video cross-referencing and the setting up OAuth delegated access.

With data entry and customer verification complete, PayStorm can now progress to automatically issue financial products to new customers. Issuance can involve loading tokens on to mobile devices and embossing standard plastic cards.

New customers can be provided with a digitised card within minutes of the KYC process completing and can start using it immediately.

Customers can check balances, view historic transactions, modify usage limits within the boundaries of the program and block cards via their mobile device.

Apps make use of these standard PayStorm features by consuming exposed APIs.

IQS puts an end to client-side test tool deployment and to decentralised management of QA.
All connections between IQS and the applications being tested are centralised and shared along with the storage of test configurations and test results.
Centralised access to IQS encourages collaboration amongst staff, helping to develop a more agile working culture covering both development and QA processes. The time taken to resolve problems can be significantly reduced when using IQS, as both development and QA staff will share test configurations and results while focusing on rapid fault resolution.

IQS is available as a fully managed on-demand service operated by Infraxis or as a deployment on customer’s own infrastructure. In either case the same powerful features are available to IQS users.

A dedicated IQS instance is made available for each IQS customer, which is then configured to meet that customer’s specific testing requirements.
Users access IQS through standard web browsers, so there is no client software to install and IQS access is immediate for all users that require it.
IQS options include LDAP support, enabling standard integration with enterprise-wide access management solutions.

Infraxis operates the IQS Asset Store, which is a dedicated one-stop online portal for IQS customers. IQS customers can securely download licenses and test packs for use with their IQS instance, request assistance from Infraxis experts and get access to IQS documentation when they need it - on demand.
Published test packs downloaded from the Asset Store are loaded in to an IQS instance and configured, simplifying the preparation process and minimising the time needed before testing can begin.

IQS release management enables test configurations to follow the development lifecycle of an application. By duplicating the current release’s IQS configuration to form the basis for the next release, a new IQS test configuration is immediately available for modification and testing of the latest application features as they are developed.
IQS supports testing for an unrestricted number of releases, with each release configuration managed independently from all others. Older configurations can be archived and deleted as and when required.

New tests are simply created using test templates that specifically match the purpose of the test pack in use.
Individual tests can be grouped in to test sets, so testing with IQS logically follows functional areas of an application. Tests can be executed individually or as a complete set.
Data sources are defined for specific purposes, which guarantees selected data elements are present for each test pack. Users choose and configure the data they wish to use for test execution by simply selecting data identities from within a data source.
Multiple data sources can be defined for a single purpose within a test pack, which is very useful for keeping data logically segmented, for example, keeping data for various card schemes separated.
Test data can be easily updated in a data source through a browser. Alternatively, data can be managed externally using a spreadsheet editor before importing into IQS.