Results for “payments”

Use to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal. Triggers: "add memory", "remember across sessions", "call agent from app", "invoke agent from code", "agent auth", "streaming", "VPC", "VPC connectivity", "can't reach from VPC", "multi-agent", "A2A", "A2A auth", "orchestrator not delegating", "specialist not called", "migrate Bedrock Agent", "migration issue", "change model", "browser tool", "code interpreter", "delete agent", "tear down", "agentcore remove", "cross-account memory", "add payments capability to my agent", "wire payments plugin", "integrate x402 payments with the agent I'm building", "add MPP payments", "Machine Payments Protocol". External APIs via Gateway: use agents-connect. New project: use agents-get-started. CLI/dev-server errors: use agents-debug. Runtime x402/MPP payments: use agents-pay. Migration-specific Strands vs LangGraph routes here.

The English summary is being prepared. Showing the original description.

Integrate USDC payments into AI agents on Base L2. Guides setup for earning or paying, generates tailored code, and verifies configuration, covering escrow that holds funds until delivery and instant payments for HTTP requests.

• Building an agent that charges USDC for services
• Paying another agent for a specific service
• Trying payment flows in a local simulation

Access paid APIs using Machine Payments Protocol (MPP), a protocol for request payments. The skill checks payment requirements, selects a compatible wallet or client, submits payment, and helps inspect the API response and receipt.

• Paying for an API request that returns HTTP 402
• Choosing a client for a payment method
• Finding paid services and setting spending controls

Manage payment permissions for AI agents with spending caps, expiration dates, and merchant rules. Use cryptographic signatures to verify authorization, coordinate approval from multiple agents for high-value purchases, and track or revoke payment permissions.

• Set shopping budgets and permitted merchants for AI agents
• Require multiple agents to approve high-value purchases
• Manage subscription renewals with spending caps

Send crypto payments through Binance Pay using QR codes or payment links, then check payment status. Generate links and QR codes to receive payments, with support for C2C payments and automatic detection of PIX QR codes.

• Pay using a Binance Pay QR code
• Pay using a PIX QR code
• Generate a link to receive crypto

Choose Stripe APIs and payment interfaces for one-time payments, subscriptions, marketplaces, and financial accounts. Helps plan, modify, or review integrations, including connected account setup, payment method storage, and migration from deprecated APIs.

• Choose an API and interface for one-time payments
• Plan subscriptions and recurring billing
• Design connected accounts for a marketplace

Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.

The English summary is being prepared. Showing the original description.

Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.

The English summary is being prepared. Showing the original description.

Add Stripe payments to a web app — Checkout Sessions, Payment Intents, subscriptions, webhooks, customer portal, and pricing pages. Covers the decision of which Stripe API to use, produces working integration code, and handles webhook verification. No MCP server needed — uses Stripe npm package directly. Triggers: 'add payments', 'stripe', 'checkout', 'subscription', 'payment form', 'pricing page', 'billing', 'accept payments', 'stripe webhook', 'customer portal'.

The English summary is being prepared. Showing the original description.

Integrate x402, an HTTP payment protocol, so agents can pay for APIs or services. Configure task and session budgets, approved recipients, and wallets with privately managed keys, using integration paths for Base, X Layer, or Solana.

• Enable an agent to pay for a paid API
• Set task and session spending limits
• Restrict payment recipients, networks, and assets

Guides setup for paying for Browser Use Cloud tasks with USDC on Base, a blockchain network. Covers wallet preparation, private key storage, a paid test, and SDK integration, including use without signup or an API key.

• Use Browser Use Cloud without an API key
• Prepare and fund a wallet for automation
• Add wallet payments to an app

Manage credits and billing in Flow Nexus by checking balances and usage history, creating payment links, configuring automatic refills, and changing subscription tiers. Analyze spending patterns to support budget decisions and choose plans suited to usage.

• Checking credit balances and usage history
• Creating payment links for credit purchases
• Configuring automatic credit refills

Build Stripe payment flows for one-time purchases and subscriptions. The skill covers checkout options, customer payment methods, refunds, and webhooks, which notify an application about payment events, with examples for testing payment behavior.

• Adding one-time payments to an application
• Building subscription billing
• Handling payment events through webhooks

Help implement automated subscription billing, invoice generation and delivery, and recovery of failed payments. Cover subscription states, renewals, usage-based charges, prorated plan changes, and tax calculations as parts of the billing workflow.

• Implementing recurring billing for a SaaS product
• Automating invoice generation and delivery
• Designing retries and notices for failed payments

Access external APIs for email, calendars, GitHub, and payments through OneCLI Gateway. The proxy adds stored credentials to outgoing HTTPS requests, letting agents use connected services without handling secret values directly.

• Read email through the Gmail API
• Check Google Calendar events
• View GitHub repositories or create issues

Recover failed Stripe subscription payments through a charge retry and three timed reminder emails. Track each subscription’s progress in a ledger, stop reminders after payment, and hand unresolved cases to a person after the final notice.

• Follow up on failed subscription payments
• Space reminder emails and prevent repeat sends
• Check a subscription’s recovery progress

An end-to-end method for drafting and finalising a complex, multi-pillar regulated fintech agreement — from intake to signature. Authored from a senior fintech lawyer's manual: a licensed payment-services provider engaging a counterparty across agent cash-in/cash-out, QR payments, wallet e-payments, and a marketplace, each with its own regulatory profile. Runs five phases and fourteen steps: regulatory mapping (activity-to-licence matrix, grey-zone classification gates), architecture (framework-plus-sub-agreement structure, ring-fenced marketplace), the regulatory–commercial balance (what flexes vs what cannot), core drafting (authority, float mechanics, hard-coded regulator caps, liability — all tracking control), execution-blocker triage, and a pre-signature check closing open blockers as conditions precedent. It refuses to invent licence-specific values or draft a representation as true without executed evidence. Use it to structure, draft, negotiate, or review any regulated payments contract.

The English summary is being prepared. Showing the original description.

Apto Payments integration. Manage data, records, and automate workflows. Use when the user wants to interact with Apto Payments data.

The English summary is being prepared. Showing the original description.

Alternative Payments integration. Manage data, records, and automate workflows. Use when the user wants to interact with Alternative Payments data.

The English summary is being prepared. Showing the original description.

Agent skill for payments - invoke with $agent-payments

The English summary is being prepared. Showing the original description.

Agent skill for agentic-payments - invoke with $agent-agentic-payments

The English summary is being prepared. Showing the original description.

Frappe Payments and ERPNext payment workflow guidance for payment gateways, payment requests, subscriptions, invoices, reconciliation, webhooks, and secure checkout flows. Use when work touches payments in Frappe or ERPNext.

The English summary is being prepared. Showing the original description.

Agentic and machine-to-machine payments on Stellar. Covers x402 (HTTP 402 paid APIs via OZ Channels facilitator, fee-sponsored clients) and MPP (Machine Payments Protocol) in both Charge mode (per-request SAC) and Channel mode (off-chain commits, high-frequency). Defaults to USDC (SEP-41 SAC) on `stellar:testnet`/`stellar:pubnet` (CAIP-2). Use when selling a paid API to AI agents, building an x402 client, or designing a payment-channel architecture for high-frequency agent traffic.

The English summary is being prepared. Showing the original description.

Read balances, transactions, recurring payments, loan details, and investment holdings from financial accounts linked through Plaid. Review multiple institutions together or focus on selected accounts and dates to understand recorded spending and financial activity.

• Checking balances across linked accounts
• Reviewing spending over a chosen period
• Listing active subscriptions and recurring bills