Ping

The orchestration layer for payments

Programs · 24h on-chain

On-chain activity

All programs →

Ping

Ping is a payments infrastructure platform providing unified APIs, hosted checkout sessions, embeddable payment widgets, and a fiat-to-crypto on-ramp SDK for multi-chain cryptocurrency acceptance. The system uses NEAR Intents for cross-chain routing, enabling payers to pay in any currency while payees receive their preferred asset across multiple blockchains. Offerings include payment links, a RESTful payments API, and a CLI tool designed for agent-to-agent payment flows.

Visit
About

Ping

Ping is a cross-chain payment orchestration platform that positions itself as a unified layer between fiat systems and multiple blockchains. Founded in August 2024, it enables payers to transact in their preferred currency while payees receive in theirs, with [[PROJECT:2112]] handling the cross-chain routing that makes this possible without requiring either party to manually bridge or swap assets.

How the Intent-Based Model Works

Ping's architecture is built around an intent-based payment model. Rather than asking users to coordinate wallets, bridge assets, or manage gas on individual chains, Ping accepts a payment intent — specifying who pays what and in which currency — and resolves the cross-chain path through NEAR Intents. The payer's funds move through the NEAR Intents network, which routes them to the recipient's preferred asset and chain.

This design is most visible in Ping's onramp product. A user deposits fiat currency, which is converted to native USDC on Base via Coinbase's onramp API, then routed through the NEAR Intents network to arrive in the user's wallet on their chosen chain. According to Ping's documentation, this full flow completes in approximately 30 seconds. Solana is among the supported destination chains, with SOL, USDC, and USDT all deliverable this way.

Core Products

Ping's documentation describes six main offerings.

Payment Links and Embeddable Widgets allow merchants and developers to create shareable payment requests that work across chains and currencies without requiring recipients to hold specific tokens.

Intent-Based Payments form the underlying mechanism described above: the platform resolves currency and chain differences so neither party needs to think about the path between them.

The Chain-Abstracted Onramp (Ping Onramp) is an SDK developers can embed in any application to offer fiat-to-crypto entry. It accepts Apple Pay, debit and credit cards, ACH bank transfers, fiat wallets, and crypto accounts depending on region. Coverage spans 90-plus countries across Europe, North America, South America, Africa, Asia, and Oceania.

Automated Subscriptions use NEAR's signed intents system to handle recurring payments without repeated wallet approvals. Subscribers sign all future payment authorizations upfront; Ping releases them on the defined schedule. Version 1 supports USDC on NEAR only, with configurable billing intervals and up to 12 payment periods per subscription. Merchants must hold assets in intents.near before receiving payments — a setup requirement the documentation flags explicitly, as payments fail silently if this prior interaction has not occurred.

Swaps and Multi-chain Asset Management enable basic asset movement across supported networks. The PingPay API and Ping CLI give developers programmatic access to payment sessions, hosted checkout flows, headless payment submission, and webhook callbacks for payment tracking.

Supported Networks and Assets

Ping's onramp lists explicit destination support for:

  • Solana: SOL, USDC, USDT
  • NEAR: NEAR, USDC, USDT, and several NEAR-native tokens
  • Ethereum: ETH, USDC, USDT
  • XRP, ZCash (ZEC), and Tron (TRX, USDT)

The documentation notes that the supported asset list is growing. The full PingPay API asset coverage is defined in an OpenAPI specification at pay.pingpay.io/api.

Security and Audits

No security audits or formal security reviews are documented in Ping's public materials. The subscription product carries a known operational constraint: the intents.near pre-interaction requirement. Its absence causes silent payment failure. The documentation describes this explicitly, noting it as a required integration step before merchants can receive payments.

Team and Background

Ping does not publicly document its team or founding personnel. The company was registered with a founding date of August 2024. Its GitHub organization (Pingpayio) hosts six public repositories written primarily in TypeScript, including the subscription service, a point-of-sale demo application (pizza.pingpay.io), and checkout and onramp integration examples. The most recent repository update was May 2026.

Solana Ecosystem Fit

Ping is not a Solana-native protocol. Its cross-chain routing runs through NEAR Intents, and its onramp settlement layer uses Base for the initial USDC leg. Solana is one of several supported destination chains alongside NEAR and Ethereum.

The practical relevance to Solana is in the onramp: Ping gives developers a single SDK that can land SOL, USDC, or USDT in a user's Solana wallet starting from a fiat payment, with no requirement for the user to first hold crypto. For Solana applications serving users without existing crypto holdings, this represents a concrete fiat entry path. The subscription product's current NEAR-only limitation means recurring payment use cases are not yet available for Solana recipients.

Contents

Note: inclusion in Solana Compass directory does not indicate a recommendation or endorsement of this project, its token(s) or its products. Data sourced with thanks from The Grid to aid in building these pages.

Reviews

0.0
0 reviews
Please login to write a review.
Solana tokens

Solana Token Markets

Explore all tokens →