<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tolulope Johnson</title>
    <description>The latest articles on DEV Community by Tolulope Johnson (@tolulope_johnson_5c91cb0d).</description>
    <link>https://dev.to/tolulope_johnson_5c91cb0d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4181991%2Fcdec988e-16e1-47d9-a1e5-38c7420bcffa.png</url>
      <title>DEV Community: Tolulope Johnson</title>
      <link>https://dev.to/tolulope_johnson_5c91cb0d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tolulope_johnson_5c91cb0d"/>
    <language>en</language>
    <item>
      <title>Building Agentic Crypto Payments with FlowPay and Kimi</title>
      <dc:creator>Tolulope Johnson</dc:creator>
      <pubDate>Tue, 13 Oct 2026 11:02:50 +0000</pubDate>
      <link>https://dev.to/tolulope_johnson_5c91cb0d/building-agentic-crypto-payments-with-flowpay-and-kimi-44pd</link>
      <guid>https://dev.to/tolulope_johnson_5c91cb0d/building-agentic-crypto-payments-with-flowpay-and-kimi-44pd</guid>
      <description>&lt;h2&gt;
  
  
  Building Agentic Crypto Payments with FlowPay and Kimi
&lt;/h2&gt;

&lt;p&gt;The way software interacts with money is changing.&lt;/p&gt;

&lt;p&gt;Traditional payment infrastructure is designed primarily for humans. A customer opens a checkout page, selects a payment method, completes a transaction and waits for the application to confirm it.&lt;/p&gt;

&lt;p&gt;But a new generation of digital products is emerging.&lt;/p&gt;

&lt;p&gt;AI agents can now perform tasks, interact with APIs, operate software and coordinate workflows on behalf of users. As these systems become more autonomous, they also need a reliable way to interact with payments.&lt;/p&gt;

&lt;p&gt;That is what we are building with &lt;strong&gt;FlowPay&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;FlowPay is crypto payment infrastructure designed for businesses, developers, bots, applications and AI agents.&lt;/p&gt;

&lt;p&gt;Kimi provides an intelligence layer that helps FlowPay make complex payment information easier for both humans and autonomous agents to understand and act on.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is FlowPay?
&lt;/h2&gt;

&lt;p&gt;FlowPay provides a single payment layer that digital products can integrate through:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;API&lt;/li&gt;
&lt;li&gt;CLI&lt;/li&gt;
&lt;li&gt;MCP&lt;/li&gt;
&lt;li&gt;Checkout&lt;/li&gt;
&lt;li&gt;Webhooks&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Instead of designing payment infrastructure only around dashboards and traditional interfaces, FlowPay also supports workflows where there may be no user interface at all.&lt;/p&gt;

&lt;p&gt;For example, a developer can create and monitor payments directly from the command line.&lt;/p&gt;

&lt;p&gt;A Telegram bot can generate a payment request.&lt;/p&gt;

&lt;p&gt;An application can listen for payment events through webhooks.&lt;/p&gt;

&lt;p&gt;And an AI agent can interact with FlowPay through structured tools.&lt;/p&gt;

&lt;p&gt;This opens the door to agent-to-agent payment workflows.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why We Integrated Kimi
&lt;/h2&gt;

&lt;p&gt;Crypto payments generate a lot of technical information.&lt;/p&gt;

&lt;p&gt;A single payment can involve:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Blockchain networks&lt;/li&gt;
&lt;li&gt;Wallet addresses&lt;/li&gt;
&lt;li&gt;Transaction hashes&lt;/li&gt;
&lt;li&gt;Assets and token contracts&lt;/li&gt;
&lt;li&gt;Confirmation states&lt;/li&gt;
&lt;li&gt;Payment amounts&lt;/li&gt;
&lt;li&gt;Failed transactions&lt;/li&gt;
&lt;li&gt;Wrong assets&lt;/li&gt;
&lt;li&gt;Incorrect networks&lt;/li&gt;
&lt;li&gt;Recovery states&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;This information is useful to developers, but it can be difficult for normal users or autonomous agents to interpret correctly.&lt;/p&gt;

&lt;p&gt;We use &lt;strong&gt;Kimi in FlowPay's AI layer to reason over payment context and turn technical payment information into understandable responses and actions.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Instead of exposing raw blockchain data directly to a customer, FlowPay can provide structured payment information to the AI layer.&lt;/p&gt;

&lt;p&gt;Kimi can then help interpret that information and explain what is happening.&lt;/p&gt;

&lt;p&gt;For example, FlowPay may provide context such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The expected payment asset&lt;/li&gt;
&lt;li&gt;The asset that was actually received&lt;/li&gt;
&lt;li&gt;The selected blockchain&lt;/li&gt;
&lt;li&gt;The transaction status&lt;/li&gt;
&lt;li&gt;Confirmation progress&lt;/li&gt;
&lt;li&gt;Whether the payment has been completed&lt;/li&gt;
&lt;li&gt;Whether a supported recovery option exists&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Kimi helps transform this information into something that a user or AI agent can understand.&lt;/p&gt;




&lt;h2&gt;
  
  
  AI-Powered Payment Support
&lt;/h2&gt;

&lt;p&gt;One of the most important applications of Kimi inside FlowPay is payment support.&lt;/p&gt;

&lt;p&gt;Crypto payments do not always go perfectly.&lt;/p&gt;

&lt;p&gt;A customer may send the wrong supported asset.&lt;/p&gt;

&lt;p&gt;A transaction may still be confirming.&lt;/p&gt;

&lt;p&gt;A payment may be incomplete.&lt;/p&gt;

&lt;p&gt;Or funds may arrive in a way that requires additional handling.&lt;/p&gt;

&lt;p&gt;Normally, the user would need to copy a transaction hash, open a block explorer, understand what happened and potentially contact support.&lt;/p&gt;

&lt;p&gt;FlowPay is designed to make that experience much easier.&lt;/p&gt;

&lt;p&gt;Our payment system gathers the relevant transaction and payment context.&lt;/p&gt;

&lt;p&gt;Kimi can then help the FlowPay agent understand the situation and communicate it in natural language.&lt;/p&gt;

&lt;p&gt;Instead of presenting a technical state such as:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;WRONG_ASSET&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;the user can receive a clear explanation of what happened and what options are available.&lt;/p&gt;

&lt;p&gt;This allows us to bring intelligent support directly into the payment experience.&lt;/p&gt;




&lt;h2&gt;
  
  
  Keeping AI Separate From Fund Control
&lt;/h2&gt;

&lt;p&gt;Using AI around financial infrastructure requires strong boundaries.&lt;/p&gt;

&lt;p&gt;Kimi is used for reasoning and interaction, but it is &lt;strong&gt;not given unrestricted control over funds&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Kimi does not receive private keys.&lt;/p&gt;

&lt;p&gt;It does not directly sign blockchain transactions.&lt;/p&gt;

&lt;p&gt;It does not independently decide to move funds.&lt;/p&gt;

&lt;p&gt;Sensitive operations remain behind FlowPay's backend, policies and restricted transaction infrastructure.&lt;/p&gt;

&lt;p&gt;The architecture separates intelligence from execution.&lt;/p&gt;

&lt;p&gt;A simplified version looks like this:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;User or AI Agent&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Kimi reasoning layer&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;FlowPay tools and policies&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Payment infrastructure&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;↓&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Blockchain&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Kimi helps understand the request and payment context.&lt;/p&gt;

&lt;p&gt;FlowPay decides which structured operations are available.&lt;/p&gt;

&lt;p&gt;The backend enforces security and policy rules.&lt;/p&gt;

&lt;p&gt;The blockchain provides settlement.&lt;/p&gt;

&lt;p&gt;This allows us to use AI while maintaining strict control over payment execution.&lt;/p&gt;




&lt;h2&gt;
  
  
  Kimi and Agent-to-Agent Payments
&lt;/h2&gt;

&lt;p&gt;One of the most interesting areas we are exploring with FlowPay is agent-to-agent payments.&lt;/p&gt;

&lt;p&gt;Imagine an AI agent using a service provided by another software agent.&lt;/p&gt;

&lt;p&gt;The first agent needs to pay.&lt;/p&gt;

&lt;p&gt;Instead of asking a human to leave the workflow, open a dashboard and manually complete several steps, the payment request can become part of the software interaction itself.&lt;/p&gt;

&lt;p&gt;With FlowPay, an agent can initiate a payment workflow through our API, CLI or MCP tools.&lt;/p&gt;

&lt;p&gt;Another user, application or agent can then respond to that payment request.&lt;/p&gt;

&lt;p&gt;FlowPay handles the payment infrastructure while Kimi helps the agent reason about the payment state and interaction.&lt;/p&gt;

&lt;p&gt;A simplified flow looks like:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Business / Bot / Agent → FlowPay → Customer / Agent&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Underneath that FlowPay layer are:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;API | CLI | MCP | Checkout | Webhooks&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;This means the same infrastructure can support both traditional applications and autonomous software.&lt;/p&gt;




&lt;h2&gt;
  
  
  CLI-Native Payments
&lt;/h2&gt;

&lt;p&gt;FlowPay is also introducing CLI-native payments.&lt;/p&gt;

&lt;p&gt;This allows developers and software agents to interact with the payment system directly from a terminal.&lt;/p&gt;

&lt;p&gt;For example, a workflow can create a payment request, retrieve its status and react to payment events without requiring someone to open a dashboard.&lt;/p&gt;

&lt;p&gt;This is particularly useful for autonomous software.&lt;/p&gt;

&lt;p&gt;Kimi adds another layer to this experience by helping interpret natural-language intentions and payment context, while FlowPay translates authorized actions into structured payment operations.&lt;/p&gt;

&lt;p&gt;The goal is not to replace payment infrastructure with AI.&lt;/p&gt;

&lt;p&gt;The goal is to make reliable payment infrastructure accessible to AI.&lt;/p&gt;




&lt;h2&gt;
  
  
  Recoverable Crypto Payment Errors
&lt;/h2&gt;

&lt;p&gt;Another important part of FlowPay is payment recovery.&lt;/p&gt;

&lt;p&gt;In traditional crypto payments, sending an incorrect asset or making certain payment mistakes can result in funds becoming difficult to recover.&lt;/p&gt;

&lt;p&gt;FlowPay is designed so that supported payment errors can be identified and handled through controlled recovery workflows.&lt;/p&gt;

&lt;p&gt;Kimi helps make these situations understandable.&lt;/p&gt;

&lt;p&gt;Instead of expecting a customer to understand token contracts, networks and transaction traces, the AI layer can explain what happened using the payment context FlowPay has already collected.&lt;/p&gt;

&lt;p&gt;The actual recovery operation remains controlled by FlowPay's secure backend.&lt;/p&gt;

&lt;p&gt;This combination gives us both intelligent assistance and controlled financial execution.&lt;/p&gt;




&lt;h2&gt;
  
  
  What Value Does Kimi Bring to FlowPay?
&lt;/h2&gt;

&lt;p&gt;Kimi helps FlowPay in three major areas.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Understanding complex payment context
&lt;/h3&gt;

&lt;p&gt;Blockchain transactions contain technical information that is difficult for many users to understand.&lt;/p&gt;

&lt;p&gt;Kimi helps translate that context into natural language.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Intelligent payment support
&lt;/h3&gt;

&lt;p&gt;Kimi allows FlowPay to provide contextual assistance when a payment is pending, incorrect or requires attention.&lt;/p&gt;

&lt;p&gt;Instead of relying entirely on email-based support, intelligence can exist directly inside the payment experience.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Enabling autonomous payment workflows
&lt;/h3&gt;

&lt;p&gt;As AI agents become capable of using external tools, they need a way to understand financial actions.&lt;/p&gt;

&lt;p&gt;Kimi provides the reasoning layer while FlowPay provides the secure payment execution layer.&lt;/p&gt;

&lt;p&gt;Together, this makes agent-driven payment workflows possible without giving the language model unrestricted access to funds.&lt;/p&gt;




&lt;h2&gt;
  
  
  Building for the AI Economy
&lt;/h2&gt;

&lt;p&gt;We believe payments will increasingly happen between more than just people and websites.&lt;/p&gt;

&lt;p&gt;Payments will happen between:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Humans and applications&lt;/li&gt;
&lt;li&gt;Applications and applications&lt;/li&gt;
&lt;li&gt;Bots and businesses&lt;/li&gt;
&lt;li&gt;AI agents and services&lt;/li&gt;
&lt;li&gt;AI agents and other AI agents&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Payment infrastructure therefore needs to become programmable, interoperable and understandable by machines.&lt;/p&gt;

&lt;p&gt;FlowPay is building that payment layer.&lt;/p&gt;

&lt;p&gt;Kimi gives us the intelligence needed to make those interactions easier to understand and operate.&lt;/p&gt;

&lt;p&gt;Together, they allow us to explore what payments can look like when both humans and autonomous software can participate in the same financial infrastructure.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Bigger Vision
&lt;/h2&gt;

&lt;p&gt;Our goal is for FlowPay to become one payment layer for digital products.&lt;/p&gt;

&lt;p&gt;Whether someone is building a SaaS platform, marketplace, Telegram bot, mobile application, command-line application or autonomous AI agent, they should be able to use the same infrastructure to create, receive and manage payments.&lt;/p&gt;

&lt;p&gt;Kimi helps us extend that infrastructure with intelligence.&lt;/p&gt;

&lt;p&gt;Instead of AI simply talking about payments, we are building a system where AI can understand real payment context and interact with secure payment tools.&lt;/p&gt;

&lt;p&gt;That is the direction we believe digital payments are moving toward.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;FlowPay — a smarter way to move money across digital products.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>web3</category>
      <category>ai</category>
      <category>cryptocurrency</category>
      <category>hackathon</category>
    </item>
  </channel>
</rss>
