"When we had a payment gateway, every single checkout had its own unique deposit address that you can easily reconcile, that works across any chain, any EVM network." @TarunMangukiya, CEO at @koshmoney

Toss Payments joined the government's deposit token payment infrastructure project as preferred bidder for the PG (payment gateway) role, the same consortium NH and KB joined earlier this month, now with the full participant list clearer: 9 banks, 8 PG companies, and 2 large merchants, run by the Financial Telecommunications and Clearings Institute. Toss Payments' specific job is connecting the deposit token payment network to merchants as the PG, building the integration so existing merchant payment setups can accept deposit tokens without new terminals or system rebuilds, consumers pay through bank-issued deposit token wallet apps on their end. The pitch is the same one NH and KB made: deposit tokens settle simultaneously with payment, cutting merchant settlement time from the current 1-3 days down to near-instant, with participating institutions also validating potential fee reductions and improved merchant cash flow. Toss Payments completed the project kickoff briefing with the Ministry of Science and ICT and KISA in June, and joined the joint inter-agency launch ceremony on July 22, the same event KB referenced. Detailed development work and scheduling with other participants starts this half.

July marked another month of real-world product progress at PolyFlow: 1⃣Gift card redemption went live within the NeoBanking ecosystem 2⃣The Crypto Payment Gateway Partner Program officially launched 3⃣AI Token Settlement was integrated with cross-border crypto payments In July, our AI Token Settlement solution processed $8M in transaction volume—supporting automated payments, cross-border settlement, and global value flows across the AI Agent ecosystem. Real-world payments. AI-native settlement. #PolyFlow# #PayFi# #AIAgents# #CryptoPayments# #CrossBorderPayments#

🔓 Triple-A's client funds survived its breach untouched. Its own treasury didn't. That outcome was decided months before the incident, not during it. Triple-A, a Singapore-based stablecoin and fiat payment gateway, identified unauthorized access to its own wallets on 25 July. Client funds were unaffected. Triple-A doesn't hold client assets in custody, and MAS's user-protection regime for digital payment token service providers, in force since October 2024, requires client assets to be segregated and reconciled daily. Regulation drew that boundary. Nobody draws one around a company's own operating treasury, so most companies never do. That's where this incident played out. Onchain researchers put the loss at roughly $11.8 million; Triple-A hasn't confirmed a figure. Outflows spanned at least six blockchains for about 31 hours, each chain with its own keys and pause button. Detection wasn't the failure, containment across six simultaneous chains was. Range is the platform for companies operating across stablecoins and fiat. We don't prevent key compromise, our lane is giving finance, compliance and risk teams one view across every wallet and chain, so containment runs in minutes, not a day and a half. Where's your boundary between company and client assets, and how long would containment take you? Read the full breakdown 👇

# Practical and Useful Patterns with ADK ✋ "Are you sure you want to send this email?" — ADK's Action Confirmations add pre-execution user approval for irreversible operations, building safer agents. 📌 Title: Action Confirmations — Pre-Execution Approval for Irreversible Operations 🔗 URL: 🧩 Overview ADK's Action Confirmations require explicit user approval before executing hard-to-reverse operations like email sending, data deletion, and payment processing. The agent asks "Should I proceed?" and only executes upon user approval. This maintains human control at critical decision points while keeping agents autonomous for routine tasks. 🛠 Usage Defining tools with confirmation requirements. To define tools with confirmation, import `Agent` and `ToolContext` from `google.adk`. In `send_email(to: str, subject: str, body: str, tool_context: ToolContext)`, call `tool_context.actions.request_confirmation(message=...)` before the actual send, displaying a preview with recipient, subject, and body. The email is only sent if the user approves. Similarly, `delete_records(table: str, condition: str, tool_context: ToolContext)` counts records to be deleted first, then displays the count in a confirmation message for user approval. Pass both tools to an `Agent` with `name="admin_assistant"` and `model="gemini-2.5-flash"` via the `tools` parameter. 🏗 Practical Patterns **When to Require Confirmation**: Add confirmation for these categories: - External sends (email, messages, API calls) - Data modification or deletion - Operations that incur charges - Permission or access control changes For payment processing, define `process_payment(amount: float, currency: str, recipient: str, tool_context: ToolContext)`. This function calls `tool_context.actions.request_confirmation(message=...)` with the recipient, currency, and amount details. Only after user approval does it execute `payment_gateway.charge(amount=..., currency=..., recipient=...)` to process the transaction. **Confirmation Message Design**: Include the target, scope of impact, and irreversibility in confirmation messages. Provide exactly the information users need to make an informed decision. **Staged Confirmations**: For multi-step operations, decide whether to confirm at each step or summarize at the final step. Balance thoroughness with user experience. 💡 Use Cases 📧 Email and message send confirmation 🗑️ Database record deletion approval 💳 Payment and transfer execution confirmation 🔐 Permission and access control change approval ⚠️ Caveats - Too many confirmations degrade user experience. Limit confirmations to truly irreversible operations. - Insufficient confirmation messages prevent users from making informed decisions. Be specific about the operation's impact. - Confirmations become bottlenecks in batch processing and automation pipelines. Consider skippable confirmations for automated scenarios. ✨ Properly configured Action Confirmations balance agent autonomy with human safety oversight. The key is confirming only "can't-undo" operations! #ADK# #AIAgent#

Trade on AVE. Bank through PolyFlow. We're excited to announce our partnership with @AveaiGlobal — the leading on-chain trading gateway spanning 130+ chains, 300+ DEXes, and 7M+ users. What is PolyFlow? Built on 20+ years of cross-border payment infrastructure from HuionePayGroup + real-time stablecoin settlement via Circle Payments Network. PolyFlow delivers institutional-grade clearing & settlement with: - PID on-chain identity - PLP non-custodial settlement - Fiat payment gateway orchestration AVE brings the market to you. PolyFlow takes your funds beyond the trade — into accounts, merchants, cards, and cross-border rails. #PolyFlow# #AveAI# #TradeOnAVE# #BankThroughPolyFlow# #PayFi# #StablecoinPayments# #OnchainTrading# #CrossBorderPayments# #DeFi# #Web3Payments#