OwnPay Logo OwnPay
Settlement Rails 2 LIVE IN BETA
AI Agent OS
Session keys & policy engine for autonomous agents
x402 Machine Paywalls
RFC 9110 HTTP 402 instant API micropayments
Model Context Protocol (MCP)
Native payment tools for Claude, Cursor & AI agents
Hosted Checkout & Pay Links
Dynamic USDC payment links & web checkout
B2B Smart Invoicing
On-chain recurring billing & instant settlement
Settlement Explorer
On-chain transaction verification & block receipts
Developers Merchants Docs About us
Talk to Team Merchant Console →
OwnPay Logo OwnPay
Base 8453 · Live Settlement
Merchant Console → Talk to Team
Products & Functions
AI Agent OS x402 Machine Paywalls Model Context Protocol (MCP) Hosted Checkout Smart Invoicing Settlement Explorer
Solutions
AI Agents & APIs SaaS Billing Global E-Commerce Enterprise Settlement
Platform & Showcase
Developers Hub Merchants Portal Documentation
Company
About us Vision Roadmap Team Contact
Legal & Social
Terms of Service Privacy Policy Security Architecture Compliance
LinkedIn X GitHub
Support: support@ownpay.tech
© 2026 Team OwnPay. Non-custodial protocol.
Compliance Framework
  • 1. Our Approach
  • 2. Onboarding & KYB
  • 3. AML & Sanctions
  • 4. Risk Controls
  • 5. Geographic Scope
  • 6. Third-Party Rails
  • 7. Digital Assets
  • 8. AI Agent Payments
  • 9. Records & Cooperation
  • 10. Reporting Violations
  • 11. Policy Updates
  • 12. Important Notice
Institutional Framework

OwnPay Compliance

OwnPay operates technology services responsibly, addressing legal, regulatory, contractual, and risk-management requirements for Web3 and autonomous AI-agent payments.

Last Updated: October 2026
Legal & Compliance Contact: legal@ownpay.tech
Architecture: Non-Custodial Base L2 & Solana

1. Our Approach

OwnPay is committed to operating its technology services responsibly and addressing applicable legal, regulatory, contractual, and risk-management requirements.

The compliance requirements for a transaction may depend on the user's location, the merchant's business, the asset and blockchain involved, the transaction flow, and the third-party providers used.

Non-Custodial Boundary: This framework describes OwnPay's compliance approach. It does not claim that OwnPay holds a particular financial licence, regulatory approval, certification, or registration unless that status is specifically identified and independently verified for a given jurisdiction.

2. Identity Verification and Business Onboarding

Depending on the product, jurisdiction, transaction risk, and provider requirements, users may be required to complete:

  • Individual identity verification (KYC).
  • Business verification (KYB).
  • Beneficial ownership and authorized representative checks.
  • Business activity and source-of-funds information, where applicable.
  • Additional verification or periodic information updates.

Verification requirements differ across account types and service tiers (Starter 0.25%, Verified 0.10%, Enterprise 0.05%). Passing an onboarding check does not guarantee approval for every transaction or service.

3. Anti-Money Laundering and Sanctions

Where applicable to OwnPay's role and the services provided, OwnPay implements risk-based controls to identify, prevent, investigate, and respond to suspected unlawful activity.

These controls include sanctions screening against international watchlists (OFAC, UN, EU), transaction monitoring, risk assessment, suspicious-activity escalation, and cooperation with authorized providers or competent authorities.

4. Risk-Based Transaction Controls

OwnPay may restrict, delay, reject, or suspend an account or transaction when required by law, a provider, or reasonable fraud, security, or compliance controls.

Risk factors include unusual transaction patterns, suspected credential compromise, inconsistent identity information, prohibited business activity, sanctions exposure, or attempts to circumvent established velocity limits. Where legally permitted, users may be asked for additional information to resolve a review.

5. Supported Countries and Restricted Activities

Availability depends on the specific service, provider, and applicable jurisdiction. Some products or transaction types are not available in sanctioned or restricted locations.

Users must not use OwnPay to evade sanctions or other legal restrictions, facilitate prohibited transactions, or provide false information during verification.

6. Fiat Services and Third-Party Providers

Fiat transfers, currency conversion, on-ramps, off-ramps, and regulated banking activities are provided by independent third parties under their own regulatory licenses.

Those services are subject to separate eligibility requirements, agreements, fees, transaction limits, and regulatory conditions. Integration with a provider does not establish that OwnPay itself is licensed as a money transmitter or depository institution.

7. Digital Assets and Blockchain Transactions

Digital asset transactions are subject to blockchain network rules, wallet permissions, smart-contract behavior, market volatility, and legal restrictions.

Blockchain transactions are irreversible and publicly auditable. Users are responsible for ensuring that their activity is lawful and that transaction details are correct. OwnPay does not guarantee asset value, liquidity, or recovery of assets sent incorrectly.

8. AI Agents and Automated Payments

Businesses and developers deploying AI agents for payment execution must ensure that their systems operate within authorized permissions and legal boundaries.

Users must configure spending limits, recipient restrictions, session key expiries, transaction approval thresholds, and emergency killswitches where supported. Automated capabilities do not exempt users from applicable AML, sanctions, or financial laws.

9. Records and Cooperation

OwnPay maintains account, transaction, verification, and security audit records for service delivery, fraud prevention, dispute handling, and legal compliance.

Where required by law, OwnPay may provide information to regulators, law enforcement, courts, or authorized authorities in accordance with applicable legal procedure.

10. Reporting Suspected Violations

To report suspected fraud, sanctions evasion, platform misuse, or compliance concerns:

Compliance Team: compliance@ownpay.tech
Please include a clear description of the concern and relevant transaction hashes or merchant identifiers. Do not send private keys, passwords, or full API secrets.

11. Policy Updates

Our compliance practices evolve as our products, provider relationships, jurisdictions, and legal obligations change. We update this page accordingly to maintain institutional clarity.

12. Important Notice

This page describes OwnPay's intended compliance approach. It is not a statement that OwnPay is licensed or authorized in every jurisdiction, nor a guarantee that every control described is currently active for every product tier.

Architecture: Non-Custodial Decentralized Settlement Protocol
Legal & Compliance Inquiries: legal@ownpay.tech
OwnPay Logo OwnPay

Universal payment rails for businesses and autonomous AI agents. Built natively on Base L2 and Solana for direct non-custodial settlement.

Support: support@ownpay.tech
Products
  • AI Agent OS
  • x402 Machine Paywalls
  • MCP Server Tools
  • Hosted Checkout
  • Smart Invoicing
  • Settlement Explorer
Solutions
  • AI Agents & APIs
  • SaaS & Subscription Billing
  • Global E-Commerce
  • Enterprise Settlement
  • merchant@ownpay.tech
Company
  • About us
  • Vision
  • Roadmap
  • Team
  • Contact
Legal & Social
  • Terms of Service
  • Privacy Policy
  • Security Architecture
  • Compliance
  • X (Twitter)
  • GitHub
  • LinkedIn
Settlement Engine Active • Base Mainnet (8453)
© 2026 Team OwnPay. All rights reserved.
Terms · Privacy · Security