Skip to content
by Unity Nodes
NEAR Protocol

Anything to Anything Payments for Consumers and Agents

about 13:08 long

Nothing is loaded from YouTube until you press play, and then without tracking cookies.

About this video

As payments evolve beyond single chains and manual execution, consumers and AI agents need a unified way to transact across assets, applications, and intent-driven workflows. This session explores how Pingpay’s orchestration layer, powered by NEAR Intents, enables anything-to-anything payments.

NEAR is the unified commerce layer for assets and agents.

Website: near.org NEAR AI: near.ai Intents: near.org/intents Chain Abstraction: proximity.dev Sharding: nearone.org

For the devs GitHub: github.com/near Dev Docs: docs.near.org Devhub: devhub.near.page @NEARDevHub

Connect with socials Twitter:   / nearprotocol   Blog: near.org/blog Medium:   / nearprotocol   #NEAR #nearprotocol #NEARAI

Transcript

2,720 words

Captions as YouTube publishes them, usually machine-generated, so product and people names can be misheard.

  1. 0:10

    Hey everyone. Uh, this is great. Being honest, I did have a bit of a nightmare this week. There'd be like five people here. So, this is great. Just don't leave. Um, but yeah, in this session, um, I'm going to talk about how the problems that exist with payments right now and how we're building tools for you and your agents to use today. So payments currently live in silos.

  2. 0:31

    Every chain still runs on its own payment rails. New layer ones and layer 2s have started targeting the payment space, but they're just further isolating liquidity and users across different networks. Um, when it comes to fiat and crypto, they're still super disconnected, slow, expensive, full of friction. Um, and when funds do eventually move, payment settlement isn't really enough. Um, especially for agents, you need refunds, automation,

  3. 0:56

    compliance, dispute resolution, and a place to manage all of your assets and payments in one place across both fiat and crypto. Um, and commerce is shifting really quickly. Um, we're starting to see in real time how AI economies need crypto rails, which legacy systems just can't deliver.

  4. 1:13

    Um, so what's missing? What's missing is an orchestration layer to tie payments and settlement together. And that's what Ping is trying to do. Ping is the orchestration layer. It sits at the center layer as you can see above fiat and all blockchains um acting as one payment network to connect those blockchains and fiat systems into a range of different use cases whether that be SAS payments, e-commerce, donations, bill splitting with your

  5. 1:39

    friends at the bar, subscriptions, digital services or even agenda commerce. Um and this all started kind of the whole journey of ping was with the northstar of providing anything to anything payments. Um but what are anything to anything payments? They are at its core something that allows a user to pay in any asset on any chain even fiat and the receiver can choose the asset that they want to receive. Ping and intents handles everything else in the background. Um on

  6. 2:08

    this slide you can see all of the different screens from our ping checkout options um and the flows associated with them. So on the furthest side you can see the options that you've got. So pay with wallet, pay with card or pay with deposit. Um and then moving along to the next one that's pay with wallet. So that's paying directly from the wallet that you connect at checkout. Um we've also got the next screen along which is pay with deposit. That's if you don't necessarily want to connect your wallet

  7. 2:32

    to an application, you can sign on and do a manual deposit or scanning QR code to send the asset from whichever chain you want to pay with. And then the receiver or the merchant, they receive the asset that they want to sell in. And then the final one, which is pretty interesting as well, is pay with card.

  8. 2:48

    So that leverages our on-ramp solution, which I'll talk about later. Essentially, that allows people at your checkouts, if you're using Ping, to pay with fiat directly and you settle in crypto. And these tool this anything to anything payments is the foundation for the tools that we provide for consumers and agents. Um so we've taken a real focus on giving consumers all of the tools within the ping layer that they need to make payments as easy as possible across all

  9. 3:14

    chains and their own use cases. Um all of which these are all live today which you can use. This includes which we'll go through individually. Um ping links uh our checkout API. um both of which can be accessed via the merchant dashboard and our chain abstracted feed on-ramp but we'll go through each one individually. So starting with ping links and if you watch the screen the kind of I'll show you through each flow

  10. 3:37

    of the different steps. Um ping links are a no code solution for accepting anything to anything payments. You can create a hosted checkout in seconds with no code and experience whatsoever and let users pay their way and the asset that they want to pay with and you receive the asset that you want to settle in irrespective of the blockchain or fiat. The ping links dash dashboard section gives you like an overview of all the payment links that you created at a glance. things like their name,

  11. 4:02

    their description, uh the amount that you priced it in, and even the specific volume that's went through each payment. Um you can filter them, kind of make them active, inactive if you want to start accepting payment, but then don't over a certain period of time. And you can manage them really easily, whether it be sharing it, copying it, editing it if there's changes you want to make or deleting the link entirely. Um you can

  12. 4:23

    also go into the more detailed view, which you can see here, uh for a specific link. So, in this one, it's settling the Uber split with your friends. Um, this shows all of the specific volume and payments and their progress for a specific link that you've created. Um, all of the progress statuses are there. So, you can see there's a success. There's three successful, one pending. That's essentially currently going through on your intents. Um, obviously you can see

  13. 4:45

    here the statuses. Like I said, you can view the explorer for the specific transactions if you want to do that. And you can also select each one individually and export them to CSV for bootkeeping purposes as well. Um, in terms of creating a ping link, that's super easy, too. That can be done in seconds. Um, all you need to do is give it a title and description, set the price of the payment, uh, and leave it open for or leave it open for the user to decide. So, you can change you can

  14. 5:08

    toggle the button there that says let the user choose the payment amount. Essentially, what that does is that's good for like tipping um, if you wanted to do donations as well, where they come in, they just say, I want to tip $5 for this. I pay with whatever I want, and then you receive that payment. doesn't need to be a fixed amount every time.

  15. 5:26

    Um, and then at the bottom, you just need to select the asset that you want to receive and the wallet that you want that to sell to. Um, and then yeah, once it's created, it's really that easy. You've got then three options on how you can share it.

  16. 5:37

    Um, just sharing it via a standard link to people directly or you can share it via QR code, which I think is a great feature personally. Whether it be kind of you scan QR codes at these types of events, you could have those up for IRL IRL payments where it directs them to that ping link for that transaction. um kind of very much a in-person use case.

  17. 5:55

    Um and then you can also share it directly on Twitter as well. Um but moving on to the ping API which is the next consumer product that we um have live today. Um the ping checkout API is an API which teams can easily integrate into their applications and start accepting payments in any asset supported by near intense and fiat while settling in the to in the token they want to receive. So very similar to ping links but much more developer focused.

  18. 6:20

    This as well is super easy to integrate. That can be done in less than 10 minutes. All you've got to do to start is go to the ping dashboard, create an API key as a start. Then you just need to set the destination wallet address that you want those payments to go to.

  19. 6:33

    All of the payments made through the API irrespective of what asset that is. That'll go directly to that wallet without you needing to handle anything. It will just go direct there. No step to withdraw like there is with Stripe or other solutions. It just goes manually to that wallet that you want. Then in terms of um additional customization, you can add any web hooks um that you would like. So right now you can add them for successful payments or failed

  20. 6:56

    payments just so you can get a more bespoke solution for knowing what's happening with your payments end to end. Um and then as far as kind of what you see from the API, you can also view all of the payments that come through um in this tab here. So again with the statuses very similar to the ping links but successful, pending, failed, and then much more detailed information on which wallets they're coming through, what time it was, and the statuses.

  21. 7:18

    Um, and we're actually um also have the session information there as well, and customers. So the customers tab, which I don't show in the slides, essentially is um you can search specific users on your platform, see their habits, what types of payments they've made, and that sort of volume. um and gives this like kind of thing we can see here shows all of the session info for where people drop out of the funnel whether they connect their wallet but don't pay or they've just completely abandoned it once they've seen the checkout flow. So I

  22. 7:50

    think that kind of gives some nice insights for you as a merchant. Um and then in terms of um live things of the API right now it's currently used for payments in the near merch store. So, if you wanted to see it action kind of end to end in that payment or scoop some good merch, uh go to nearmerch.com. Uh little shill. Um but the last the last thing I want to talk about here is um what's for consumers anyway is the chain of strategy at on-ramp. Um you can

  23. 8:19

    on-ramp into any near intent supported asset directly from your card or Apple Pay in the US. Um you can use this today at onramp.pingay.io. Um, and super easy to get started. Just come in, start with, um, like I say, Apple Pay in the States or card. Um, but externally, if you are not a consumer that doesn't want to on-ramp, um, you can also add it to your app, add fear rails to your app, and you can integrate our SDK in minutes as well. So, it's

  24. 8:45

    really straightforward to use. Um, but why should consumers have all the fun? Um, I've mentioned agents a lot at the start of this presentation. they need payments as well, which is why I'm really excited to announce the launch of the Ping Pay CLI.

  25. 8:59

    Um, so what is that? The Pingpace CLI is our first step towards agentic payments. It allows you to create, execute, and monitor payments directly from your terminal. No dashboard like I've showed you before. No browser, just MPX ping- CLI, and you can move value programmatically. Um, we're entering an era of AI agents. Um, ironclaw enables autonomous agents to execute tasks, but agents also need to transact.

  26. 9:24

    Um, if an agent needs to pay for compute, um, settle an invoice or execute a cross execute a crosschain payment, it needs an execution layer which is ping and the ping CLI offers that layer. An agent can call it um, it can construct an intent um, and execute a payment. It can then also monitor that the status of that payment to know that it's coming through and that's been completed. Um this is programmable money

  27. 9:48

    for programmable agents. But let me show you a few demos. So the first demo which you'll see the video for here is using the ping CLI to create a ping link in claw directly. This is like the intermediary step for you to not need to create links manually via your agent like with the ping links. Um it will run the npx ping CLI skill.

  28. 10:09

    Um, it will then get the ping skill where it can create, list, get or delete ping links directly. Um, it will then create you an agent wallet using frames.gg currently. Um, and then you can also then set the desired receiving wallet address. So, if it creates that agent wallet, but you want to use a different external one, you can do that.

  29. 10:29

    In this example, it's an address. Um, it'll then go through all of the steps needed to create that payment link for you. And then it will output that link which you'll see in a second on the demo. It goes through the steps. It shows the details of that payment and that'll provide the custom checkout right there. And then that's the same as the ping link that's directly sharable.

  30. 10:48

    And that takes you to that exact checkout that the agent just created. And then anyone can make payments to that um to that link directly. Um but then I've also got another demo. Um this final demo moves the human element entirely. This is agent to agent making payments. Um here you can see the merchant agent and the uh the payer agent side by side communicating with each other to create to make a payment.

  31. 11:13

    Um the payer agent is waiting for the checkout session while um the merchant agent reads the skill file. This is all being done like right now on the screen. Um the payment the payer agent is waiting for this check out a um checkout session. you can still see. And then the merchant agent on the left is creating that checkout session to receive USDC on near.

  32. 11:34

    Um the payer agent is then going to be continuously pulling for that check checkout session as the communicating. Um as you can see right here, the agent's still creating that session, but on the right hand side it's checking for that solution. So you can see here the payment session's been created and the agent's going to go ahead and make that payment on the right hand side. So it's found the new session where it's paying

  33. 11:55

    0.1 USDC on base. The agent on the left is wanting to receive USDC on near. So that's using near intents in the background for the USDC on base to be routed to the near wallet address that the merchant agents want to receive. And you can see here that payment has been completed. So the a payer agent's done and the session is pending now because it's in progress on the uh on the merchant side. So that's pulling for payment and you'll see that it'll go

  34. 12:19

    through now and it will complete and then once that once that payment is complete we can then kind of view things as the human side of things to verify that those payments are going through correctly and you can see right now both sides are completed and the demo is complete that I'm showing but then there's next steps. So obviously as agents transact together um you want to have some sort of verifiability that

  35. 12:42

    that payment is correct and the right things you want to are happening. So you can see there you can then view it directly in your dashboard the same way as you would the API to track those payments specifically know that it's going through and that the agents are actually behaving how you want them to.

  36. 12:55

    Um but yeah that's kind of everything I really wanted to go through. Like I say everything I've showed today is live and ready to use if you want to get started in terms of the dashboard. Pay.pay.io. Our docs are available docs.pinkingpay.io.

  37. 13:08

    Um Ping's Twitter is Pingpay_io and my TGNX is Ju. But I'll be around all week if anyone wants to speak about me with anything. Um, yeah. And again, Telegram's on the ride. We just opened it if anyone wants to jump in and get involved. Yeah. Thanks so much for the time.