Integration Levels

Amperry offers three distinct integration levels to accommodate different customer needs, from complete ecosystem integration to full hardware customization. Each level provides different degrees of flexibility, control, and complexity.

Integration Levels Overview

Level A – Complete Integration into Our Ecosystem

The customer's software runs within our kiosk app, which is already designed with available unlock and payment modes. This approach offers simplicity and security, but with limited versatility: it's not possible to go beyond the functions already provided by the Amperry system.

Additionally, only authorized accessories and hardware (POS, card readers, etc.) can be used to ensure compatibility and stability.

Example: Private University

Level B – Integration with Free Hardware, Independent Software

In this scenario, the customer manages the software independently: they can install and run any application compatible with the Linux environment provided by our machine.

Amperry is used only as a base system, both online (app, web app, POS) and offline (with direct serial access, without cloud).

The customer also has full freedom in choosing accessory hardware (POS, peripherals from different brands, etc.), managing the integration directly.

Example: Public Airport

Level C – Complete Hardware Customization

The customer installs and manages their own hardware and software, while Amperry is used only in its online component (app, web app, POS).

This level guarantees maximum freedom, giving the customer total control over the new hardware.

Example: Integration with Android box

Detailed Comparison

Technical Specifications Comparison

Feature	Level A	Level B	Level C
Software Control	Amperry-managed	Customer-managed	Customer-managed
Hardware Compatibility	Authorized only	Any compatible	Any hardware
Customization Level	Limited to Amperry features	Full software customization	Complete system control
Integration Complexity	Low	Medium	High
Maintenance Responsibility	Amperry	Shared	Customer
Cloud Dependency	Required	Optional	Optional
Serial Communication	Not available	Available	Available
Third-party Apps	Not supported	Supported	Supported

Cost and Resource Comparison

Aspect	Level A	Level B	Level C
Initial Setup Cost	Low	Medium	High
Ongoing Maintenance	Low	Medium	High
Technical Support	Full Amperry support	Partial support	Limited support
Hardware Investment	Standard Amperry hardware	Flexible hardware choice	Customer hardware
Development Time	Minimal	Moderate	Extensive
Scalability	Limited by Amperry features	High	Unlimited

Security and Compliance Comparison

Security Aspect	Level A	Level B	Level C
Payment Security	PCI DSS compliant	Customer responsibility	Customer responsibility
Data Protection	Amperry managed	Shared responsibility	Customer managed
Hardware Security	Certified components	Customer verification	Customer verification
Software Updates	Automatic	Manual/Customer	Manual/Customer
Audit Trail	Built-in	Custom implementation	Custom implementation

Practical Implementation Examples

Level A Example: Private University

Scenario: University campus charging stations

Implementation:

Amperry kiosk app handles all charging operations
Students use university ID cards for authentication
Payment processing through university payment system
Centralized monitoring and reporting

Benefits:

Quick deployment across multiple locations
Consistent user experience
Minimal technical maintenance required
Built-in reporting and analytics

Limitations:

Cannot integrate with custom university systems beyond available APIs
Limited to Amperry's payment methods
Hardware upgrades require Amperry approval

Level B Example: Public Airport

Scenario: Airport charging stations with custom flight information integration

Implementation:

Custom Linux application running on Amperry hardware
Integration with airport flight information systems
Custom payment methods (airport loyalty points, airline miles)
Direct serial communication for real-time data exchange

Benefits:

Full software customization for airport-specific needs
Integration with existing airport systems
Flexible hardware choices for specific requirements
Offline operation capability

Considerations:

Requires technical expertise for integration
Customer responsible for software maintenance
Hardware compatibility testing required

Level C Example: Android Box Integration

Scenario: Retail chain with existing Android-based POS systems

Implementation:

Customer's Android box replaces Amperry hardware
Amperry cloud services handle charging management
Integration with existing retail management systems
Custom UI matching brand identity

Benefits:

Complete hardware control
Seamless integration with existing systems
Maximum customization possibilities
Cost optimization through existing hardware

Requirements:

Significant development resources
Complete system integration responsibility
Custom security implementation

Choosing the Right Integration Level

When to Choose Level A

Quick deployment needed
Limited technical resources available
Standard charging operations sufficient
Compliance requirements are strict
Minimal customization needed

When to Choose Level B

Custom software requirements exist
Existing system integration needed
Hardware flexibility required
Offline operation necessary
Technical expertise available

When to Choose Level C

Complete system control desired
Existing hardware infrastructure available
Maximum customization required
Cost optimization through existing systems
Extensive technical resources available

Conclusion

Each integration level offers distinct advantages depending on your specific requirements. Level A provides the fastest path to deployment with maximum support, Level B offers flexibility while maintaining some support, and Level C provides complete control for organizations with extensive technical resources.

Consider your technical capabilities, customization needs, and long-term goals when selecting the appropriate integration level for your project.