> For the complete documentation index, see [llms.txt](https://pingpay.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pingpay.gitbook.io/docs/ping-onramp/overview.md).

# Overview

***

<figure><picture><source srcset="/files/hUjC9yDbrt94mQq6Yhl3" media="(prefers-color-scheme: dark)"><img src="https://2412975227-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4y2jIy2xuLBz44dN9ue8%2Fuploads%2FVz8fIpJHoWjahvfBEiqx%2F7.png?alt=media&amp;token=377529e7-ba23-4a79-b273-c97346f6886b" alt=""></picture><figcaption></figcaption></figure>

### What is the Ping Onramp?

The Ping Onramp is a chain-abstracted onramp SDK designed to easily integrate a seamless fiat-to-crypto onramp experience directly within any application. Once integrated, it enables your users to purchase **any** NEAR Intents supported currencies directly with their Fiat, from a variety of different payment methods.

By leveraging NEAR Intents and the Coinbase Onramp API, users deposit fiat to receive native USDC on Base, which then gets routed to the NEAR Intents network - allowing users to receive their asset on their preferred blockchain and wallet in less than 30 seconds.

**Core features include:**

* Out-of-the-box support for Coinbase Onramp, allowing users to initiate fiat-to-crypto purchases directly inside their applications.
* Powered by NEAR Intents, allowing for fast, gas-efficient cross-chain delivery to the user's preferred wallet. Buy with Fiat, land anywhere via Intents.
* Developers can pass in pre-defined parameters such as wallet address, target token (e.g. NEAR, USDC), and support any blockchain NEAR, Ethereum, BTC, and more - enabling a simplistic user journey. It is easily extendable to support multiple tokens and networks as new providers are added.
* The onramp component can be embedded directly into any frontend. Supports full styling control, dynamic parameters, and both inline modal and full-page redirect flows.
* Developers can attach optional event handlers to each step of the Onramp flow, enabling tight UX feedback.

Ping will continue to add new onramp provider options, to expand the global coverage and maximise accessibility for users to have multiple options for payment.

**Get started with integration:**

{% content-ref url="/pages/KkYWyKDwOCLh8q25yDDM" %}
[SDK Integration Guide](/docs/ping-onramp/sdk.md)
{% endcontent-ref %}