Ovra Paymentsv1.0.0

An AI shopping assistant uses ovra_pay to complete purchases for users, handling the entire checkout flow from selecting items to paying. The agent never sees the user's card details, ensuring security and GDPR compliance.

When an external API returns HTTP 402 Payment Required, the agent automatically uses ovra_pay with handle_402 action to pay the fee and continue accessing the data. This enables seamless integration with paid APIs.

An agent manages recurring subscriptions (e.g., software, media) by using ovra_intent to declare and pay for renewals, while staying within the spending policy set by the user. It can also handle approval workflows when human intervention is needed.

After each purchase, the agent uploads the receipt PDF or PNG using ovra_receipt, linking it to the payment intent. This automates expense tracking and compliance for business users.

Enterprises use ovra_agent to provision new agents and issue virtual Visa cards via ovra_card, enabling each agent to make purchases independently within predefined spending limits.

Ovra charges a small fee per successful payment transaction, similar to traditional payment processors. Revenue scales with transaction volume.

Offers tiered subscription plans (e.g., Starter, Business, Enterprise) with different monthly fees based on the number of agents, transactions, and features (e.g., advanced compliance reporting).

A free sandbox tier (using sk_test_* keys) with limited transactions to attract developers, then convert to paid plans for production use with higher limits and support.