PaygasusPaygasus
Contact sales

Payments and connectivity for the physical economy.

Buses and parking decks. EV chargers and water utilities. Stadium concourses and unattended kiosks at the edge of the carrier network. We move the money and keep your network operational — on one platform, under one contract.

Volume processed
$100B+

Aggregate payment volume across the platform since June 2012.

Operating locations
3,400+

Across the United States, Canada, India, and Ireland.

US footprint
50 + DC

All fifty states plus the District of Columbia.

Countries
30

Networking products sold and supported across 30 countries; payment operations in the US, Canada, and Europe via agent settlement.

Currencies
140+

For presentment and settlement, via global acquiring rails.

3,400 locations, mapped.

Each dot represents a Paygasus city of presence — payment endpoints, connectivity, or both. Dot size reflects relative concentration. From Helena to Honolulu, Anchorage to Atlanta.

Paygasus locations across the United StatesA dot map showing Paygasus locations across the contiguous United States, Alaska, and Hawaii. Each dot represents one city of presence; dot size reflects the relative number of Paygasus locations in that city.ALASKAHAWAII
City of presence1,355 unique US cities · all 50 states + DCSource: Paygasus operating records, May 2026
Every name, by contract
PayFac · Registered ISO · US & Canada
Full Liability Submitter · US & Canada
Solutions Provider
Carrier Partner
Carrier Partner
StarlinkAuthorized Solution Provider
Platinum Service Provider
Solutions Provider · Ericsson
OEM · NA Exclusive · Since 2019
Platform Partner · Transit · Parking · EV
PCI DSS Level 1SOC 2P2PE-compatible tokenizationMulti-region data residency
— and growing.

Software companies built payments for the internet. We build them for everywhere else.

The first wave won the internet.

A generation of payments infrastructure built brilliantly for the connected merchant and the connected buyer. Trillions of dollars now move across SaaS billing, eCommerce checkout, and the API layer that connects them — instant, reliable, mature. That category is settled and that work is done.

The rest of the world is more complex.

Most commerce is not on the open web. It happens across physical infrastructure: EV chargers in parking lots with one bar of cellular service, transit fare gates without reliable Wi-Fi, unattended kiosks inside county courthouses before dawn, and stadium concourses where 60,000 people tap at once. The endpoint is often a piece of metal. The customer may be a city, county, or state. The contract is procurement, not a credit card form.

So we built one product, not three.

Those places need payments, connectivity, and devices delivered through a single operating layer. Not a payments company with a connectivity partner. Not a connectivity company with a payments partner. One platform, one operating model, one contract — built for the physical, connected, high-volume environments traditional payment stacks are not designed to support.

Paygasus is the payments and connectivity operating system for the physical economy. One platform, one ledger, one contract.

This is Paygasus.

One platform across every market Paygasus serves.

— and the markets that don't fit a single category, which is where most modern commerce operates.Explore every market →
A customer
Sector
EV charging
Flagship
Costa Mesa, CA
Status
Standard for new sites
Stack
Pay · Connect · Unattended

Every Paygasus rail, in one parking lot.

The Costa Mesa site was the first location where Paygasus delivered the full stack — not only the payment terminals, but the network beneath them. Earlier locations had run Payter Apollo readers on their own connectivity. Costa Mesa was the moment that changed.

The site uses AT&T fiber as its primary connection. T-Mobile T-Priority and Starlink each carry a small standing load underneath — tunnels live, sessions warm — so when fiber drops, the cellular and satellite paths can absorb full traffic without re-handshake delay. The entire system is bonded through a single Peplink Balance SDX Pro running SpeedFusion. Payter Apollo readers sit at the stalls.

The stack, by priority
PrimaryAT&T Fiber Wired90%
Backup · 1T-Mobile T-Priority Cellular5%
Backup · 2Starlink Performance Satellite5%
Bonded byPeplink Balance SDX Pro · SpeedFusion · weighted distribution with prioritized failover

The receipts under the receipts.

Certifications, residency, and continuity — the safeguards procurement expects before any contract moves forward.

i — Certifications

Audited annually, by name.

  • PCI DSS Level 1
  • SOC 2 Type II
  • P2PE-compatible tokenization
  • HIPAA-aligned data handling

Attestation reports available under MNDA at procurement.

ii — Residency

Where your data lives, named.

  • United States — primary
  • Canada — in-country
  • Ireland — EU / EEA
  • India — APAC partner region

Multi-region by architecture, not by re-export. Settlement, ledger, and PII residency configurable per merchant.

iii — Continuity

Built to ride through.

  • Active-active across regions
  • Store-and-forward at the edge
  • Bonded carrier failover
  • Published status page

The product is designed for endpoints where the network fails. SLA terms negotiated at contract.

An SDK that knows the merchant might be offline.

Most payment APIs assume the merchant is online and the network is stable. Ours is built for physical environments where uptime, failover, and continuity matter.

  • SDKsTypeScript · Python · Go · Ruby · Java
  • SandboxFree · mirrors production · no card required
  • WebhooksReplay tool with HMAC verification
  • SurfacesOnline · in-person · unattended · IVR
  • ProcurementSolutions engineer assigned at enterprise
charge.tsPaygasus SDK · v3
// A charge that survives a flaky
// network at the curb.

import { Paygasus } from "@paygasus/sdk";

const pg = new Paygasus({
  apiKey: process.env.PAYGASUS_KEY,
});

await pg.charges.create({
  amount:   2950,                       // $29.50
  currency: "USD",
  source:   "pg_tkn_01HQ7K",
  surface:  "unattended.ev_charger",
  network: {
    fallback:      "store_and_forward",
    settle_within: "24h",
  },
  metadata: { kiosk: "EV-204", lane: "B" },
});

The platform is built. The rails are named. The next contract is yours.

Two ways to start: procurement teams can speak with a solutions engineer, while engineering teams can access a sandbox in under five minutes.

— Paygasus, since 2012.30 countries · 140+ currencies · one contract