Skip to content
CUNICULA

Agent Money Providers

Providers with a documented payment path an AI agent can use now. The option-level matrix separates identity privacy from agent-spend controls.

2 zero KYC · 2 light KYC · 1 full KYC

5 services
Selected services0/4 selected · Select at least two services

Choose services from the results below.

5 providers found
ServiceCategoryScoreSource coverageKYCJurisdictionRiskSelectReviewed
Bitrefillbitrefill.com
Gift Cards
34
Source coverage: Verified
Light
SEHigh confidence
caution
2026-08-25
Gift cards, top-ups and eSIMs bought with crypto.
Gift Cards!
BTCPay Serverbtcpayserver.org
Merchants
HOLD
Source coverage: Partial
No KYC
UnknownOpaque basis
caution
2026-09-05
Self-hosted Bitcoin and Lightning payments.
Merchants!
Laso Financelaso.finance
Virtual Cards
29
Source coverage: Verified
Light
USOpaque basis
caution
2026-08-09
Stablecoin-funded virtual cards via vouchers.
Virtual Cards!
Privacy.comprivacy.com
Virtual Cards
25
Source coverage: Verified
Full
USHigh confidence
caution
2026-08-25
US virtual cards locked to a single merchant.
Virtual Cards!
SHOPINBITshopinbit.com
Merchants
HOLD
Source coverage: Verified
No KYC
PLHigh confidence
caution
2026-08-15
Crypto concierge for goods, travel and cars.
Merchants!

Privacy observations, source coverage, and risk are separate. See the published method.

Change ranking

Choose how to order services. Scores do not change.

How to choose

A provider can expose several payment paths with different identity and control requirements. Laso, for example, documents no-verification shopping routes alongside KYC-gated account payouts and an identity-bearing bank profile. The Agent Money matrix records those as separate options rather than turning one route into a provider-wide claim.

The privacy score and evidence confidence shown here are the existing provider scores. They are not replaced by a new agent score. Control quality is read separately: a verified account can still provide useful merchant locks and spend caps, while a lower-identity rail can remain unsafe for an agent with broad wallet authority.

Check first
  • Identity setup for the exact payment option, including any later verification trigger.
  • Recipient, merchant, issuer, and operator data created by that option.
  • Spend caps, per-transaction approval, and whether access can be paused or revoked.
  • Recovery after a wrong recipient, wrong amount, revealed gift code, or compromised agent credential.

Frequently Asked Questions

Does an agent-compatible payment service protect identity?

Not necessarily. Agent compatibility describes whether software can complete or prepare a payment. Identity privacy depends on the account, funding rail, issuer, recipient data, and verification requirements for the specific option.

Are spend controls the same as financial privacy?

No. Merchant locks, limits, approvals, and revocation reduce agent error and abuse. They do not remove identity or transaction records held by the provider, bank, card network, merchant, or recipient rail.

Why are some unknown fields published?

Unknown means the reviewed first-party material did not document the field. It is retained instead of inferring a favorable control or recovery path from provider-level marketing.