Skip to Content

POS Clover Mock

by
Odoo

$ 499.99

v 17.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Point of Sale (point_of_sale)
• Discuss (mail)
• Inventory (stock)
Community Apps Dependencies
Lines of code 2231
Technical Name pos_clover_mock
LicenseOPL-1
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies • Invoicing (account)
• Point of Sale (point_of_sale)
• Discuss (mail)
• Inventory (stock)
Community Apps Dependencies
Lines of code 2231
Technical Name pos_clover_mock
LicenseOPL-1

POS Clover Mock - Test & Demo Without Hardware

POS Clover Mock is a companion module to POS Clover that enables testing and demonstrating Clover payment flows without requiring a physical Clover terminal. Perfect for QA testing, client demos, development environments, and training scenarios.

Pricing note: This module is $89.99. The listing can show a combined price because it depends on POS Clover. Example: 410 + 89.99 = 499.99 (rounded to 500).

Test Every Scenario

Success • Partial Payment • Declined • Timeout • Refund • Void • Network Error

Supported Editions

  • Odoo 17 Community
  • Odoo 17 Enterprise (On-Premises)
  • Odoo.sh
  • Odoo Online (SaaS)

Why Use POS Clover Mock?

QA & Testing
Test all payment scenarios without costly API calls or real transactions. Simulate edge cases and error conditions.

Client Demos
Demonstrate POS + Clover integration to clients who don't have Clover hardware yet. Close deals faster!

Training
Train cashiers on payment flows without risk. Practice handling declines, timeouts, and refunds safely.

Development
Develop and debug payment integrations locally without needing a sandbox Clover account.

Instant Feedback
No waiting for API responses. Get immediate feedback on payment flows during development.

Safe Testing
Visual indicator prevents accidental use in production. Clear mock mode banner on screen.

How It Works

Select a mock scenario from the popup and the system returns a realistic Clover response instantly. This lets you test success, error, and refund flows without real hardware.

Mock Scenario Popup

Available Mock Scenarios

Scenario Description Use Case
Success Payment approved with realistic fake card details (VISA, Mastercard, AMEX, Discover) Happy path testing
Partial Payment Only 50% of the requested amount is approved. Creates remaining balance line. Split payment testing
Declined Card declined by issuer with proper error message Error handling testing
Timeout (30s) Simulates a 30-second delay followed by timeout error Network issue testing
Refund Success Successful refund transaction with proper response Refund flow testing
Refund Failed Refund rejected - original transaction not found Refund error handling
Void Transaction voided before settlement Cancellation testing
Network Error Unable to connect to Clover API Connection failure testing

Quick Setup (3 Steps)

Step 1: Install the Module

Install POS Clover Mock from the Apps menu. The POS Clover module will be installed as a dependency.

Step 2: Enable Mock Mode

  • Go to Point of Sale → Configuration → Settings
  • Find your POS configuration
  • Enable "Clover Mock Mode" in the Payment section
  • Optionally enable "Show Mock Mode Indicator" to display a warning banner
POS Mock Settings

Step 3: Test in POS

  • Open a POS session
  • Add products to cart and click "Pay"
  • Select your Clover payment method
  • A popup will appear to select your mock scenario
  • Click a scenario to simulate that payment outcome!

Mock Response Example

// Success Response (what your POS receives)

{
  "payment": {
    "id": "MOCK-PAY-A1B2C3D4E5F6",
    "result": "SUCCESS",
    "amount": 5000,  // $50.00 in cents
    "externalPaymentId": "123-order-uid-456",
    "cardTransaction": {
      "authCode": "MOCK42",
      "cardType": "VISA",
      "last4": "4242",
      "referenceId": "MOCKREF12345",
      "type": "AUTH"
    },
    "createdTime": 1706700000000
  },
  "paymentId": "MOCK-PAY-A1B2C3D4E5F6",
  "mock_mode": true
}
Mock Payment Result

Payment Flow Comparison

Real Mode

  1. Cashier clicks Pay
  2. API call to Clover
  3. Customer swipes card on terminal
  4. Wait for authorization
  5. Receive response
  6. Complete sale

Duration: 30-60 seconds

Mock Mode

  1. Cashier clicks Pay
  2. Select mock scenario
  3. Instant mock response
  4. Complete sale

Duration: 1-2 seconds

Key Features

Feature Description
8 Mock Scenarios Cover all common payment outcomes including success, partial, declined, timeout, refund, void, and errors
Realistic Responses Mock responses include fake card details (last4, card type), auth codes, and proper timestamps
Per-POS Configuration Enable mock mode per POS config - perfect for having test and production terminals side by side
Visual Indicator Optional warning banner prevents accidental production use
No API Required Works completely offline without any Clover API credentials
Simulated Delays Realistic timing for each scenario (e.g., timeout waits 30 seconds)
Full Integration Works with all POS Clover features: payments, refunds, reversals, partial payments

Dependency

This module requires POS Clover to be installed. When you install POS Clover Mock, the POS Clover module will be automatically installed as a dependency.

Pricing note: If your store shows a combined price, it includes POS Clover (parent module) plus POS Clover Mock. Example: 410 + 90 = 500.
Note: You DO NOT need to configure Clover credentials to use mock mode. Mock mode works completely independently without any API setup.

Need Help?

For support, customizations, or technical assistance, please contact:

Need help with the demo or setup instructions? Please reach out via email.

IMPORTANT: If support or enhancements take significant time, an extra fee may be required.

Email: duongquoctran13062001@gmail.com

Developer: Duong Tran

Odoo Proprietary License v1.0

This software and associated files (the "Software") may only be used (executed,
modified, executed after modifications) if you have purchased a valid license
from the authors, typically via Odoo Apps, or if you have received a written
agreement from the authors of the Software (see the COPYRIGHT file).

You may develop Odoo modules that use the Software as a library (typically
by depending on it, importing it and using its resources), but without copying
any source code or material from the Software. You may distribute those
modules under the license of your choice, provided that this license is
compatible with the terms of the Odoo Proprietary License (For example:
LGPL, MIT, or proprietary licenses similar to this one).

It is forbidden to publish, distribute, sublicense, or sell copies of the Software
or modified copies of the Software.

The above copyright notice and this permission notice must be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.