ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified

ovra-agentic-payments

Use this skill when the agent needs to buy something online, pay for a service, complete a checkout, manage spending budgets, or track purchases. Enables secure payments where the agent never sees card data. Works with any website that accepts Visa. EU-native, GDPR by design. Use even if the user just says "buy", "order", "purchase", "subscribe", or "pay for".

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/alecfritsch/ovrapay
Or

Ovra Agentic Payments

Secure, EU-native payments for AI agents. The agent never touches card data.

Prerequisites

  1. Ovra API Key — sign up at getovra.com and get a key from Dashboard > Keys
  2. MCP Server Connection — this skill communicates with Ovra via MCP at https://api.getovra.com/api/mcp

Sandbox keys (sk_test_*) are free and have no spending limits. Production keys (sk_live_*) require account verification.

Setup

Add the Ovra MCP server to your agent configuration:

{
  "mcpServers": {
    "ovra": {
      "url": "https://api.getovra.com/api/mcp",
      "headers": { "Authorization": "Bearer YOUR_OVRA_API_KEY" }
    }
  }
}

Replace YOUR_OVRA_API_KEY with your key from getovra.com/dashboard/keys.

What this skill sends externally

All tool calls (ovra_pay, ovra_card, etc.) are sent to https://api.getovra.com/api/mcp via the MCP protocol. Receipt uploads (ovra_receipt) transmit base64-encoded PDF or PNG files (max 5MB) to the same endpoint — only upload invoices/receipts from the current transaction, never arbitrary files. No data is sent to any other external service. All data is stored in the EU (Germany) per GDPR.

Quick Start — One-Step Payment

For most payments, use ovra_pay which handles the entire flow:

ovra_pay({
  action: "checkout",
  agentId: "ag_xxx",
  purpose: "Notion Team Plan",
  amount: 79,
  merchant: "Notion"
})

Returns tokenized card data (DPAN + cryptogram). The real card number is never exposed.

Handle HTTP 402 Paywalls

When a web API returns HTTP 402 Payment Required:

ovra_pay({
  action: "handle_402",
  agentId: "ag_xxx",
  url: "https://api.example.com/data",
  merchant: "Example API",
  amount: 0.05
})

Available Tools (12)

Payment Flow

ToolActionsDescription
ovra_paycheckout, status, handle_402, discoverPrimary tool. Complete payment in one step.
ovra_intentlist, declare, get, cancel, verifyFine-grained intent management.
ovra_credentialobtain, grant, issue, redeem, revoke, statusAdvanced credential control.

Cards & Policy

ToolActionsDescription
ovra_cardissue, list, freeze, unfreeze, close, rotateVirtual Visa card management.
ovra_policygetView spending policy (read-only).

Records & Compliance

ToolActionsDescription
ovra_transactionlist, get, memoPayment history and notes.
ovra_receiptupload, getReceipt management. Upload only PDF/PNG invoices from the current transaction. Max 5MB.
ovra_disputelist, get, fileFile disputes on transactions.

Metadata

Stars4473
Views0
Updated2026-05-01
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-alecfritsch-ovrapay": {
      "enabled": true,
      "auto_update": true
    }
  }
}
Safety NoteClawKit audits metadata but not runtime behavior. Use with caution.