Mojave is now Paying.co — same team and expertise, now with a name that reflects our core mission. Learn more →
Clover Custom Development

Custom apps, certified for the Clover ecosystem.
Built your way.

Clover by Fiserv is the world's largest cloud-based POS ecosystem for small and medium businesses — 4 million+ devices, 700K+ merchants, and nearly $300 billion in annual payment volume. Paying.co builds custom Android applications for the entire Clover lineup — Station Duo, Flex 4, Mini, Kiosk, Go — with deep Clover SDK experience, full payment integration, and App Market publishing handled end to end.

verified 10+ years of Android payment development · Clover SDK · App Market publishing experience.
paying.co · clover · CustomPOSActivity.java
// Custom Clover Android app
import com.clover.sdk.v3.payments.*;
import com.clover.sdk.v1.merchant.*;

public class CustomPOSActivity {
  private PaymentConnector connector;

  void processPayment(long amount) {
    SaleRequest req = new SaleRequest(
      amount, "order_12345"
    );
    connector.sale(req);
  }
}
store
Clover App Market
CustomPOSActivity · v1.0.0
check_circle Published · Station, Flex, Mini, Kiosk
4M+
Clover Devices Sold
700K+
Businesses on Clover
$300B
Annual Payment Volume
10+
Years Android Payments
Clover Hardware We Build On

Nine form factors. One Android platform.

Clover's hardware lineup spans countertop POS, mobile and compact terminals, and self-service kiosks — all running on the same Clover Android platform with the same payment connector, merchant API, and App Market. Paying.co builds custom applications across the full range, with deep Clover SDK experience and direct access to the merchant data model.

♦ Family 01
point_of_sale

Countertop POS

Station Duo · Station Solo · Mini

Full-featured POS for retail counters, restaurants, and service businesses. Station Duo, Station Solo, Clover Mini, and Mini 3 — the workhorses of the Clover lineup. Paying.co builds custom POS workflows, loyalty programs, inventory managers, and tipping and split-payment screens, all running native on Clover Android.

♦ Station Duo ♦ Mini ♦ Custom POS
Talk to our team arrow_forward
♦ Family 02
smartphone

Mobile & Compact

Flex 4 · Go · Pocket

Mobile-friendly terminals for pay-at-table, line-busting, and field service. The new Flex 4, the ultra-portable Clover Go, and the Pocket reader. Paying.co builds custom Android apps with tipping, split flows, on-terminal forms, and connection back to Clover's cloud merchant services.

♦ Flex 4 ♦ Mobile ♦ Pay-at-Table
Mobile Development arrow_forward
♦ Family 03
storefront

Self-Service Kiosk

Clover Kiosk · Station Duo Kiosk Mode

Self-ordering for QSR, fast casual, and retail self-checkout. Clover's new dedicated Kiosk and the Station Duo running in kiosk mode. Paying.co builds full-screen ordering interfaces, customizer flows, payment screens, and real-time kitchen ticket delivery via the Clover order and payment APIs.

♦ Self-Order ♦ KDS Integration ♦ Full-Screen UX
Talk to our team arrow_forward
What We Actually Build

From concept to App Market.

Clover builds the hardware, the payment connector, and the ecosystem. Paying.co builds the custom Android applications that turn those into your product — whether you're deploying inside your own merchant fleet or publishing to the Clover App Market for hundreds of thousands of active merchants.

♦ 01
architecture

App architecture & UX

We design the application from the ground up — data models, API integrations, payment flows, and device-specific UI tailored to Station, Flex, Mini, Kiosk, and Go. Native Android, built around the Clover form factors your merchants actually use.

♦ 02
payments

Payment integration

Full integration with the Clover Payments API and PaymentConnector — card-present, card-not-present, refunds, tips, split payments, pre-auth and capture, and tip adjustments. EMV chip, contactless, NFC, swipe, and PIN-on-glass all handled natively.

♦ 03
store

App Market publishing

If your app is going to the Clover App Market, we handle the full submission process — sandbox testing on the Dev Kit, approval requirements, listing copy, screenshots, and post-launch iteration. Reach hundreds of thousands of active merchants.

♦ 04
cloud_sync

Cloud & backend

Backend services for multi-location syncing, analytics dashboards, remote device management, and real-time reporting connected to your Clover fleet via the Clover REST API and webhooks. We build the cloud side, not just the device app.

close With a generic Android developer
  • cancelTreats Clover as just another Android tablet
  • cancelLimited or no PaymentConnector experience
  • cancelApp Market submission is a learning curve
  • cancelDoesn't know the merchant data model or Order API
  • cancelPCI compliance handled as an afterthought
check With Paying.co on Clover
  • check_circleDeep Clover SDK and PaymentConnector experience
  • check_circleApp Market submission process handled end to end
  • check_circleNative understanding of merchant, order, and inventory APIs
  • check_circlePCI DSS compliance built in from day one
  • check_circle10+ years of Android payment development behind every project

Clover leads the SMB POS space. Build like you belong there.

With over 4 million devices sold, 700,000+ active merchants, and gross payment volume approaching $300 billion annually, Clover is the platform of choice for small and medium businesses across retail, restaurants, services, and healthcare. Roughly 20% of the U.S. small restaurant POS market runs on Clover, with revenue growing 27% year-over-year and Fiserv targeting $3.5 billion in Clover-specific revenue.

That's where Paying.co fits. We've been building custom Android payment applications for over a decade — long before Clover existed — and were among the first development teams on the platform when it launched. We've built self-order kiosk apps for QSR, points-based loyalty programs hooked into the Clover customer database, real-time inventory managers synced across multi-location fleets, custom tipping and checkout flows, and unattended deployments on Clover Flex for parking, EV charging, and laundromats.

The point is simple: Clover is the right platform to build on. We make sure your app feels native to it, not bolted onto it — with full SDK fluency, App Market experience, and PCI-compliant architecture from day one.

Talk to our Clover team arrow_forward
Under the Hood

Native to Clover Android. Built on the SDK.

We build directly against the Clover SDK, the PaymentConnector, and the merchant/order/inventory APIs — the way Clover's engineers expect applications to be built. No middleware, no wrappers, no payment workarounds. The application is yours, the source is documented, and it lives where your merchants actually use it — on the device, in the App Market, or both.

  • code

    Clover SDK fluency

    Direct integration with the Clover Android SDK — PaymentConnector, MerchantConnector, OrderConnector, InventoryConnector. Card-present and card-not-present transactions, refunds, voids, pre-auth, tip adjustments, and listener callbacks all handled the Clover-native way.

  • hub

    REST API & webhooks

    Backend services that connect to the Clover REST API and subscribe to webhooks for orders, payments, inventory changes, and customer updates. Multi-location syncing, analytics, and remote management built on top of Clover's cloud merchant services.

  • store

    App Market ready

    Sandbox testing with Clover Dev Kits, listing copy and screenshots that pass approval, and post-launch iteration. We've taken apps through the App Market submission process and know the gotchas before you hit them.

  • shield

    PCI DSS compliant by design

    Every Clover application we build follows PCI DSS principles from day one — secure card data handling, tokenization through Clover's payment connector, encrypted communication, and audit-grade transaction logging. Compliance is the foundation, not a checklist at the end.

CustomPOSActivity.java · Clover SDK integration
// Custom Clover Android app using PaymentConnector
import com.clover.sdk.v3.payments.*;
import com.clover.sdk.v1.merchant.*;
import com.clover.sdk.v3.order.OrderConnector;

public class CustomPOSActivity extends Activity {
  private PaymentConnector connector;
  private OrderConnector orders;

  void processSale(long amount, String orderId) {
    // Build the sale, route through Clover's payment stack
    SaleRequest req = new SaleRequest(amount, orderId);
    req.setTipMode(TipMode.ON_SCREEN_BEFORE_PAYMENT);
    connector.sale(req);
  }
}
// Approved · payment captured · order updated · receipt printed
Why Build on Clover

The dominant SMB payment platform.

Clover by Fiserv is the world's largest cloud-based POS ecosystem for small and medium businesses. Building custom apps on Clover means your software reaches a massive, growing installed base — with payment processing, hardware, merchant tools, and an established app distribution channel already in place.

Hardware breadth
devices

9 device form factors

From the ultra-portable Clover Go and Pocket to the full-featured Station Duo and the new self-service Kiosk — one Android codebase, one SDK, every form factor your merchants need.

Open platform
android

Android-based platform

Clover runs on Android, giving developers full access to the Android SDK alongside Clover's own payment APIs, merchant services, and peripheral integrations — modern UX on certified payment hardware.

Distribution
store

Clover App Market

Publish to the Clover App Market and reach hundreds of thousands of active merchants. Monetize with subscriptions, per-transaction fees, or one-time purchases — distribution that's already built and waiting.

Native payments
credit_card

Integrated payments

Accept EMV chip, contactless, NFC, swipe, and PIN-on-glass payments natively through Clover's payment connector — no separate gateway required, no extra certification path to manage.

Market leader
trending_up

~20% SMB restaurant POS share

Clover leads the U.S. small restaurant POS space at roughly 20% market share, ahead of Toast (~17%) and Square (~13%). 175K+ restaurant locations and a growing footprint across retail and services.

Growing fast
rocket_launch

27% YoY revenue growth

Clover revenue grew 27% year-over-year in 2025, with Fiserv targeting $3.5 billion in Clover-specific revenue. Live in 13 countries, with accelerating adoption driven by Flex 4 and the new Kiosk.

Proven Clover Use Cases

Applications we've built on Clover.

From restaurant ordering to fleet-wide device management, here's a sampling of the custom Clover applications Paying.co has built — running on Station Duo, Flex 4, Mini, Kiosk, and Go across our clients' deployments.

restaurant

Self-Order Kiosk App

Full-screen ordering for the Clover Kiosk and Station Duo. Visual menu, item customization, payment — all without staff interaction, with real-time kitchen ticket delivery via the order API.

loyalty

Custom Loyalty & Rewards

Points-based loyalty programs hooked into the Clover customer database. Reward tiers, promotional offers, and automated notifications — redeemed directly at the terminal.

inventory_2

Advanced Inventory Manager

Real-time inventory tracking synced across multiple Clover devices and locations. Auto-reorder thresholds, barcode scanning via built-in camera, and variance reporting native on the device.

receipt_long

Custom Tipping & Checkout

Tailored checkout with branded tip screens, split-payment flows, and custom receipt layouts — designed to lift tip percentages and accelerate payment at high-volume locations.

local_parking

Unattended Payment Terminal

Clover Flex deployed in unattended environments — parking garages, EV charging, and laundromat kiosks. Custom app handles payment, session tracking, and remote monitoring.

health_and_safety

Healthcare Check-in & Payment

Patient check-in flows on Clover devices for medical offices. Copay collection, appointment confirmation, and digital form signing — integrated with practice management systems via custom middleware.

storefront

Retail POS Extensions

Custom POS extensions for retail merchants — specialized workflows for liquor, cannabis, gift cards, age verification, and category-specific compliance built on top of Clover's base POS.

groups

Multi-Location Management

Fleet dashboards and admin tools for multi-location operators — real-time reporting across stores, device-level health monitoring, and remote configuration for franchise networks.

How We Deliver

From concept to App Market launch.

Every Paying.co Clover engagement runs against a documented Statement of Work, with named owners on both sides, defined milestones, and a deployment plan. Simple Clover apps land in 6–10 weeks. Full custom POS applications with backend integration and App Market publishing typically run 4–6 months. You always know where the project stands.

forum
♦ Step 01

Discovery & architecture

We start with your business needs, target merchants, and existing systems. Our team scopes the right Clover device families — Station, Flex, Mini, Kiosk — and maps the application architecture: data model, payment flows, API integrations, and UI tailored to each form factor.

brush
♦ Step 02

Design & prototyping

Custom forms, multi-step workflows, and Android UI optimized for Clover screens. Interactive prototypes run on actual Dev Kits to validate the user journey, the payment flow, and the merchant experience before we commit to full development.

build
♦ Step 03

Development & integration

Our engineers build native Android apps against the Clover SDK — PaymentConnector, MerchantConnector, OrderConnector, InventoryConnector. Backend services connect to the Clover REST API and webhooks. PCI-compliant architecture from day one.

science
♦ Step 04

Sandbox testing

Comprehensive testing on Clover Dev Kits across the full device range — transaction flows, error handling, receipt formatting, peripheral integrations, and edge cases. We catch issues before they hit a merchant device or the App Market review team.

store
♦ Step 05

App Market submission

When the app is going to the Clover App Market, we handle the full submission process — approval requirements, listing copy, screenshots, pricing model, and any back-and-forth with the Clover review team. Then post-launch iteration based on merchant feedback.

support_agent
♦ Step 06

Deployment & support

Continuous maintenance, SDK version updates, bug fixes, and feature enhancements to keep your Clover app current as the platform evolves. Same engineers, same project manager — for the life of the application.

Ready to Get Started?

Talk to our team.

Tell us what you're building on Clover — an internal app for your own merchant fleet, or a product for the Clover App Market. We'll tell you what it takes to get it scoped, built, and launched — and you'll hear back from a payments engineer, not a sales rep.

schedule
Response within one business day Most projects start with a 30-minute scoping call
engineering
You'll talk to an experienced sales engineer The person you brief is the person who scopes your build
handshake
No-obligation feasibility review We'll help you scope it and determine the best path forward that matches your budget and timeline
language
We speak your language English, Spanish, and Polish — fluent across our team and project leads
groups
Partners power our growth Much of our success comes from strong partnerships — if you're exploring one, we'd love to talk