UNRELEASED DOCUMENT - TEST DATA
</tbody>
| Area | Feature | Function | Benefit |
| Administration | Self-provisioning | Data maintenance is distributed across Network, Merchants and Fleet Companies administrators, based on data ownership and roles | |
| Identifications | Type and Models | Define specialized behavior for each type of Identification technology | |
| Identifications | Attributes | Specify whether an Identification is Reusable, Personalized, Installable | |
| Identifications | Programs | Define a set of restrictions and/or exceptions to apply to a set of identifiers | |
| Organization | Fleet Attribute | Allows to group the vehicles in large hierarchical groups | |
| Organization | User-defined classifications | Allows to group the vehicles by different (up-to 4) criteria defined by the user | |
| Organization | Vehicles and Drivers | Cardholders can be Drivers (persons) or Vehicles (any kind of unit) | |
| Organization | Vehicle classes | User-defined types of units (brand/models) with mileage and product restrictions attributes | |
| Restrictions | Rules - Timing | Allows restriction of When a cardholder can purchase | |
| Restrictions | Rules - Product | Allows restriction of the Product(s) allowed for a given cardholder | |
| Restrictions | Rules - Location | Allows restriction of on what sites a cardholder can run a transaction | |
| Restrictions | Rules - Quotas | Allows to limit the amount or volume that a cardholder can consume during a certain time (fixed or periodic) | |
| Restrictions | Contingency limits | Special limits may be configured to be applied on contingency transactions | |
| Restrictions | Offline limits | Special limits may be configured to be applied to transactions authorized offline | |
| Restrictions | Multiple inheritance | A transaction may apply to restrictions set on different entities of the system, for example: applied directly to the cardholder, inherited from the Fleet and from the Contract | |
| Security | Job roles | Assign function-oriented set of attributions to users | |
| Security | SSL | Encripted access to WEB portals and interfaces | |
| Transaction Processing | Vehicles and Accounts | A given vehicle may have many accounts with different contracts or subscribers | |
| Transaction Processing | Most restrictive condition | Restricts the authorization to the minimum value resulting from all applicable restrictions | |
| Transaction Processing | Dual Identification | Based on configuration, a transaction may require Driver and Vehicle identification | |
| Transaction Processing | Re-prompting | A transaction with missing required fields may trigger a special Decline response code instructing the Terminal to retry the transaction after collecting missing data | |
| Transaction Processing | Exceptions | Transaction are automatically flagged as Unlawful, Invalid, Suspicious, Declined and Observed, depending a set of business rules. | |
| Transaction Processing | Exceptions - To-be-reviewed | Some non-critical exception conditions may flag the transaction as To-be-reviewed. TBR transactions are approved but not considered | |
| Transaction Processing | Splitted processing | A transaction is processed by two separate engines, the Rules engine and the Accounts engine, which could be a third-party remote service | |
| Transaction Processing | Multiple FEPs | Each Terminal protocol is accepted via a specific Front-end Processor | |
| Transaction Processing | Multi-instance FEPs | Automatic load manager starts and stops instances of Front-end Processors according to system load | |
| Transaction Processing | Low-level logging | A messaging-level can be activated dinamically to diagnose problems with a site or Terminal type | |
| Transaction Processing | Automatic tax disaggregation | Extract included taxes on payment transaction to display tax totals in Statements | |
| Transaction Processing | Terminal independent rules engine | Rules, restrictions and statistics enforced and tracked across different types or Terminals (restrictions may apply) | |
| Transaction Processing | Explicit detailed tax data | Native protocol supports detailed tax information for proper presentation on Statements | |
| Transaction Processing |