Skip to content
CUNICULA

Payy

Stablecoin wallet and verified-user card on a privacy-focused network.

payy.network

Stablecoin wallet and verified-user card on a privacy-focused network.

Common useStablecoin CardStablecoin Card / Private PaymentsOperator dataUnknown
Identity checksfull KYCDocument check: full · identity exposure level 4/4
Evidence and riskLimited evidenceCautionCurrent source coverage is limited.; those sources show trade-offs worth reading.
Last reviewedReviewed 5 Sep 2026KYC checked 5 Sep 2026 · inferred jurisdiction · Source → official siteHow to cite this pageSource coverageLimited evidenceRecorded riskCaution
Evidence and facts

Evidence and facts

CUNICULA SCORE 4.0
44/100Limited evidencePrivacy 0/25 · Control 15/20 · Transparency 8/20 · Security 14/25 · Accountability 7/10 · Cap 79 · Method
JURISDICTIONUS
CAUTIONWallet policy covers public keys, diagnostics, push tokens, last-seen, support and ramp data, with IP sanctions checks. Card identity and payment information is shared with Rain and its verification/service partners. The linked Third National GLBA notice lists SSN, balance/payment and credit data, with business, own-marketing, joint-marketing and affiliate transaction/experience sharing; it says no affiliate creditworthiness or affiliate/nonaffiliate marketing sharing. The US card agreement permits collateral liquidation without prior notice and requires three business days notice to withdraw collateral. The International agreement references collateral without defining equivalent rights; it allows dynamic spending limits, transaction refusals and suspension, and directs issuer sharing of transaction/receipt and personal data. These linked documents retain dated/template wording; current-account applicability is unconfirmed. Rain discloses possible biometric verification, blockchain-analytics sharing and regulated identity/transaction retention for five years or longer after closure where legally required; biometric retention follows applicable shorter-law limits. Network docs allow exceptional encrypted-lineage decryption through an on-chain proposal; approval controls remain unverified. A June 10, 2026 advisory rates a circuit vulnerability Critical and names payy v1.3.0 as patched. May 15 chain transactions and a pinned November 8 registry/code check establish deployment of the published fix for that flaw; they do not establish absence of historical exploitation or whole-product security. Older scoped audits are not proof of whole-product security.
INCIDENTAggregate-circuit message-tail vulnerability rated Critical by Payy; fixed verifier deployed
resolved · potential critical · published 2026-06-10
Project advisory names zk-circuits-v1.1.12 affected, payy v1.3.0 patched. Unconstrained message tail can forge burns through authorized prover path; published deployment was allowlisted. No actual theft established. Payy aggregate-circuit vulnerability advisory, published 10 June 2026, Payy circuit fix: constrained message tail, bound keys and regenerated verifier artifacts, Ethereum transaction registering the fixed verifier, 15 May 2026 16:22:47 UTC, Ethereum transaction removing the affected verifier key, 15 May 2026 14:58:35 UTC, Verified deployed HonkVerifier code; compared with live runtime at Ethereum block 26373524, Verified deployed ZKTranscriptLib code; compared with live runtime at Ethereum block 26373524, Payy rollup proxy and verifier registry; read at Ethereum block 26373524
AUDITED BYNo audit listed
OPERATOR DATAUnknown
SOURCE COVERAGE
Limited evidenceTHIRD-PARTY REPORTED8/9Reviewed 5 Sep 2026 · Source → official site
LAST CHECKED2026-06-24
LAST UPDATED2026-09-05

Specs

DOCUMENT CHECKfull
IDENTITY EXPOSURELevel 4/4
KYC TRIGGERSPayy Card requires identity verification. Card docs generally list name, birth date, address, government ID number and ID photo. The US agreement additionally permits employment/income and SSN or other government ID collection, credit inquiries and account restrictions; this conflicts with the card page’s no-credit-check claim. The International agreement requires a non-US-citizen attestation for a card intended outside the US. Its linked account exclusions go beyond the wallet FAQ’s OFAC wording; wallet app availability is not card eligibility. Payy, Rain and other partners process identity data, but the International agreement does not specify Rain’s role. Protocol privacy is not a no-KYC guarantee.
FEEProtocol docs advertise $0 ERC-20 transfers; other operations have gas. The linked US card agreement (2/12/2024) lists 0% purchase APR, no annual fee, 1% international transactions and a 2% outstanding-balance late fee. The International agreement (February 2025) lists up to 3% non-USD FX and up to 3% cross-border fees, while its fee section states one up-to-3% foreign fee; whether they combine is unclear. It lists late fees up to $40 and returned-payment fees up to $29, subject to conditions. Card-page no-fee/1% FX wording differs from these agreements. Dated/template documents do not establish the terms of a current account.
NETWORKSEVM, ERC-20
CATEGORIESStablecoin Card, Private Payments
FEATURESEthereum layer 2, Private stablecoin transfers, Zero-knowledge proofs, Payy wallet, Card and business infrastructure
TORNot listed
Review analysis, source material, related services, and history

About

Payy combines a self-custodial stablecoin wallet, a verified-user Visa card through Rain and partners, and a privacy-focused Ethereum L2. Product identity checks and hosted controls are separate from transaction privacy.

Analysis

OVERVIEW

Payy combines a self-custodial stablecoin wallet, a verified-user card and network infrastructure. Its card docs link separate US and International agreements naming Third National; the International terms also allow the issuer to be identified in other card materials. Both retain dated/template wording, so current-account applicability is unconfirmed. Payy reports a $6M FirstMark-led seed round.

LIMITS

US and International card contracts have different fee and control terms. The US agreement lists 1% international transactions, a 2% balance late fee and collateral-liquidation/withdrawal controls. International terms list up-to-3% FX and up-to-3% cross-border fees with unclear combination, late fees up to $40 and returned-payment fees up to $29. Card-page no-fee/no-credit-check claims conflict with contract wording. The International agreement’s linked account-exclusion list includes Croatia, Cyprus and Vietnam, beyond a simple OFAC-only rule; it also contains malformed or ambiguous entries, so it is an exclusion list, not a list of eligible countries. Current-account applicability remains unverified. The affected rollup’s live verifier and library match published circuit-fix artifacts; this does not establish whole-product security.

USEFUL FOR

Comparing verified-user stablecoin card and wallet products, not seeking a no-KYC card.

Corporate identity

Other cited research; Provider statements. Not audited. Each claim links its own source.

LEGAL ENTITY
Zeplo, Inc. d/b/a PAYYother research ↗
Corporate identity research · reviewed 2026-09-05

Frequently Asked Questions

Is identity verification required?

The recorded KYC level is "full". Payy Card requires identity verification. Card docs generally list name, birth date, address, government ID number and ID photo. The US agreement additionally permits employment/income and SSN or other government ID collection, credit inquiries and account restrictions; this conflicts with the card page’s no-credit-check claim. The International agreement requires a non-US-citizen attestation for a card intended outside the US. Its linked account exclusions go beyond the wallet FAQ’s OFAC wording; wallet app availability is not card eligibility. Payy, Rain and other partners process identity data, but the International agreement does not specify Rain’s role. Protocol privacy is not a no-KYC guarantee.

Where is it available?

Please check the provider site for availability by country.

Is the operator based in a Five Eyes country?

Yes. The recorded jurisdiction is US, a Five Eyes country (US, UK, CA, AU, NZ). This is jurisdiction context and does not by itself establish that a service is safer or less safe.

How are identity, operator, and evidence fields reported?

Identity exposure is level 4 of 4. Hosted operator data has not been established. Jurisdiction is shown as context, not a safety verdict. Source coverage is limited evidence, last reviewed 2026-09-05, and recorded risk is caution.

Related Services

Compare

Sources and history

Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.