Paywizard Semi-integration
  • Intro - Choose Your Best Practice
  • Cloud API
    • Quick Start - Cloud API
    • POS & Payment Terminal Binding Process
      • API 1: [Deprecated]Get Access Tokens
      • API 2: Bind POS & Payment Terminal
      • API 3: Get POS & Terminal Binding List
      • API : Unbind Terminal with POS
    • Do Transactions
      • API 4: POS Initiate Transaction
      • API 5: POS System Query Transaction Results
      • Transaction Result Callback Interface
      • Transaction Type
      • Terminal API: Subscribe Transaction Results
  • HOST TO HOST INTEGRATION
    • Quick Start - Host to Host Integration
    • API: Transaction Result Push
    • API: Get Transaction Result
  • LOCAL integration
    • Payment App Integration Protocol
    • Payment App AIDL Integration
  • e-Receipt
    • e-Receipt Interface Intro
    • Terminal API : Upload Transaction Info
    • Terminal API : Upload Settlement Info
  • ONLINE PAYMENT INTEGRATION
    • Coming Soon
Powered by GitBook
On this page
  • 1. Cloud API:
  • 2. Local Integration:
  • 3. Internal Integration:
  • In summary:

Intro - Choose Your Best Practice

NextQuick Start - Cloud API

Last updated 10 days ago

We offer three integration methods:

1. Cloud API:

The Point of Sale (POS) system and the payment terminal are connected indirectly via a cloud API, with no direct physical link or requirement for the same network segment. This enables flexible integration and secure data transmission.

Advantages:

  1. Flexibility and Scalability: Easily add or remove terminals and POS systems to accommodate business growth. Cloud-based solutions scale seamlessly, minimizing hardware upgrade needs.

  2. Centralized Data Management: Transaction data is stored centrally, simplifying report generation, sales trend analysis, and inventory management for efficient decision-making.

  3. Location Independence: Supports multi-location deployments, making it ideal for businesses with multiple branches, while maintaining a unified system without local configurations.

  4. Reduced Physical Dependency: Eliminates reliance on cables and local wiring, lowering maintenance costs and enhancing system reliability.

2. Local Integration:

The Point of Sale (POS) system and the payment terminal are connected directly via USB, WIFI, Bluetooth, or a wired network to initiate transactions quickly and reliably.

Advantages:

  1. Faster Transaction Speeds: Direct local connections enable quicker processing, outperforming cloud-based options in areas with unstable internet.

  2. Enhanced Security: Data is transmitted locally, reducing exposure to online threats, but requires strong security measures (e.g., encryption) to address potential local vulnerabilities.

3. Internal Integration:

In the payment terminal, the business application directly invokes the AIDL interface provided by the OPC to process transactions internally on the same device, eliminating the need for external connections.

Advantages:

  1. Ultra-Fast Processing: Internal calls reduce latency, enabling near-instant transaction handling without network delays.

  2. Efficient Resource Use: Leverages local device resources, minimizing overhead and optimizing battery life and performance.

  3. Heightened Security: Limits data exposure by keeping operations within the device, reducing risks associated with external data transmission.

  4. Simplified Development: Streamlines integration for developers, as AIDL facilitates easy inter-app communication without complex setups.

In summary:

  1. Local Network Connection

    • Pros:

      • Faster transaction speeds due to direct communication, ideal for environments with unstable internet.

      • Enhanced security by keeping data local, reducing exposure to external threats.

    • Cons:

      • Relies on stable local hardware (e.g., WIFI or Bluetooth signals), which can fail in interference-prone areas.

      • Potential security vulnerabilities if local connections aren't properly encrypted or managed.

  2. Internal Invocation (via AIDL)

    • Pros:

      • Ultra-fast processing with minimal latency, as everything happens on-device.

      • Efficient resource use, improving battery life and performance while maintaining high security through localized operations.

      • Simplified development and integration for teams.

    • Cons:

      • Limited to a single device, making it inflexible for multi-device or scalable setups.

      • Requires advanced technical expertise to implement and troubleshoot.

  3. Cloud-Based API

    • Pros:

      • Highly scalable and accessible, allowing remote management, real-time updates, and integration across multiple locations.

      • Easier to maintain and update software centrally.

    • Cons:

      • Slower processing times in areas with poor internet, potentially disrupting transactions.

      • Higher security risks due to data transmission over the internet, increasing exposure to breaches.

Notice:

If you use WizarPOS ECR or self-service machine, we provide an more easy way to integrate

Embedded Integration (WizarPOS D22/D3) is ideal for businesses seeking a compact, all-in-one solution with a streamlined user experience.

Quick Start - Cloud API
Payment App Integration Protocol
Payment App AIDL Integration
Accessory Agent Service D22/Q3