feat: TLS payment bridge pattern + ZKP2P vendor card #88
Description
Context
Fiat onboarding is a major friction point for institutional and retail onchain adoption — users must send cash to an intermediary and trust they'll receive a digital asset in return.
Some markets already have instant payment rails (PIX in Brazil, UPI in India, Venmo/Zelle in the US, Revolut in the EU). These rails can serve as trust-minimized fiat onramps when combined with zk-TLS proofs that cryptographically attest a payment was made.
Deliverables
1. New pattern: pattern-tls-payment-bridge.md
A pattern card for TLS Payment Bridges — using zk-TLS (TLSNotary) proofs over instant payment confirmations to enable trust-minimized fiat ↔ onchain onramping.
Key points to cover:
- Intent: prove a fiat payment happened without revealing full bank/payment details
- Ingredients: zk-TLS / TLSNotary, instant payment rail APIs (PIX, UPI, Venmo, Revolut…), onchain escrow contract
- Protocol: escrow lock → fiat payment → TLS proof of payment confirmation → onchain verification → release
- Guarantees: no custodial intermediary for the swap, payment privacy preserved
- Trade-offs: reliance on TLS session notarization, payment rail availability, latency
Should reference the existing Pattern: zk-TLS as a building block.
2. New vendor: vendors/zkp2p.md
Vendor card for ZKP2P — a protocol that uses TLSNotary proofs to build peer-to-peer fiat ↔ crypto onramps.
- Core tech: TLSNotary for generating proofs on TLS API responses from payment providers
- Supports multiple payment rails (Venmo, Revolut, others)
- Peer-to-peer orderbook model with onchain escrow
3. Update CHANGELOG.md
Add entries for both new files under [Unreleased].