attested.network
this repo has no description
attested.network/
1<!DOCTYPE html>
2<html lang="en">
3<head>
4 <meta charset="UTF-8">
5 <meta name="viewport" content="width=device-width, initial-scale=1.0">
6 <title>Payers — attested.network</title>
7 <meta name="description" content="Guide for making attested payments on ATProtocol.">
8 <link rel="preconnect" href="https://fonts.googleapis.com">
9 <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
10 <link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500&display=swap" rel="stylesheet">
11 <link rel="icon" type="image/svg+xml" href="logo.svg">
12 <link rel="stylesheet" href="styles.css">
13</head>
14<body>
15
16<div class="draft-banner">
17 <p><strong>Draft — Not yet published.</strong> This specification is in active development and is not ready for review or critique. Stay tuned for formal announcements.</p>
18</div>
19
20<div class="topnav">
21 <div class="topnav-inner">
22 <a class="topnav-logo" href="/"><img src="logo.svg" alt="" class="topnav-logo-img"><span><span>attested</span>.network</span></a>
23 <nav>
24 <ul class="topnav-links">
25 <li><a href="index.html">Spec</a></li>
26 <li><a href="brokers.html">Brokers</a></li>
27 <li><a href="app-developers.html">App Developers</a></li>
28 <li><a href="recipients.html">Recipients</a></li>
29 <li><a href="payers.html" class="active">Payers</a></li>
30 <li><a href="scenarios.html">Scenarios</a></li>
31 </ul>
32 </nav>
33 </div>
34</div>
35
36<div class="hero-sm">
37 <div class="hero-inner">
38 <div class="breadcrumb"><a href="index.html">Home</a> / Payers</div>
39 <h1>Making <span>Payments</span></h1>
40 <p class="subtitle">How your payments are recorded, verified, and portable across ATProtocol.</p>
41 </div>
42</div>
43
44<main class="container">
45
46 <!-- How Your Payments Work -->
47 <section>
48 <h2>How Your Payments Work</h2>
49 <p class="section-desc">A simple system with strong guarantees.</p>
50 <p>When you pay to support a creator, a payment record is written to your ATProtocol repository. This isn't just a receipt — it's a cryptographic proof that independent parties can verify.</p>
51 <p>The creator and a payment servicer (called a broker) both write their own confirmation records. The broker facilitates and witnesses the exchange—whether that’s a credit card transaction, a cash payment, or any other mechanism. Together, these three records form an unbreakable chain of proof.</p>
52 <p>Because all three records are independently signed and stored, no single party can falsify or revoke your payment history. Your proof stands on its own.</p>
53 </section>
54
55 <!-- The Payment Experience -->
56 <section>
57 <h2>The Payment Experience</h2>
58 <p class="section-desc">What you actually see when you make a payment.</p>
59 <ol class="steps">
60 <li>You find a creator you want to support.</li>
61 <li>Your app shows you the available payment methods — these are the creator's preferred servicers.</li>
62 <li>You choose a servicer and select your payment type: a one-time tip, a recurring subscription, or a scheduled series of payments.</li>
63 <li>You're directed to a payment page where you enter your details and confirm.</li>
64 <li>Once complete, the proof appears in your account — a verified record you own forever.</li>
65 </ol>
66 </section>
67
68 <!-- Payment Types -->
69 <section>
70 <h2>Payment Types</h2>
71 <p class="section-desc">Three ways to support the people you care about.</p>
72 <div class="card-grid">
73 <div class="card">
74 <h4>One-time</h4>
75 <p>A single tip or donation in any amount. Perfect for saying thanks, supporting a specific piece of work, or trying out a creator before committing to ongoing support.</p>
76 </div>
77 <div class="card">
78 <h4>Recurring</h4>
79 <p>An ongoing subscription that renews automatically. Choose monthly, quarterly, semi-annual, or yearly. Recurring payments are immutable — to change the amount, cancel the current one and start fresh.</p>
80 </div>
81 <div class="card">
82 <h4>Scheduled</h4>
83 <p>A fixed number of payments spread over time — for example, 6 monthly payments. The series ends automatically when all payments are complete. No need to remember to cancel.</p>
84 </div>
85 </div>
86 </section>
87
88 <!-- Your Data, Your Records -->
89 <section>
90 <h2>Your Data, Your Records</h2>
91 <p class="section-desc">You own your payment history. Always.</p>
92 <p>Payment records live in your repository, not in a company's database. You own them. They're signed with your identity and stored under your control.</p>
93 <p>If you switch apps or platforms, your payment history comes with you. No export needed, no data request forms, no waiting. Your records are already yours.</p>
94 <p>No platform can lock you out of your own payment records. Even if a service shuts down, your proof of payment remains intact and verifiable.</p>
95 </section>
96
97 <!-- Privacy Options -->
98 <section>
99 <h2>Privacy Options</h2>
100 <p class="section-desc">You decide who sees your payment activity.</p>
101 <div class="callout">
102 <p><strong>Public payments</strong> are visible in your repository for anyone to verify. This is great for transparency — creators can showcase their supporters, and you can show your support publicly.</p>
103 <p style="margin-top: 12px;"><strong>Private payments</strong> are stored in a Permissioned Data Space where only authorized parties can see them. The creator and broker can still verify the payment, but it won't appear in your public repository.</p>
104 <p style="margin-top: 12px;">Both options use the same verification mechanics. Private payments aren't less trustworthy — they're just less visible. Choose whichever feels right for you.</p>
105 </div>
106 </section>
107
108 <!-- Cancellation & Changes -->
109 <section>
110 <h2>Cancellation & Changes</h2>
111 <p class="section-desc">Simple, predictable rules for managing your payments.</p>
112 <p>When you cancel a recurring or scheduled payment, the cancellation is immediate and intentional. There's no ambiguity — a cancellation record is written to confirm it.</p>
113 <p>Active recurring payments complete the current period before ending. If you've already paid for this month, you keep your access through the end of that period.</p>
114 <p>Payment records are immutable — you can't edit one after it's created. If you want different terms, cancel the existing payment and start a new one. This keeps your payment history clean and auditable.</p>
115 <p>Pre-paid support (like a scheduled series you've already funded) continues through the funded period even after cancellation. You've already paid for it, so you keep it.</p>
116 </section>
117
118</main>
119
120<footer>
121 <div class="container">
122 <p>attested.network · Built on <a href="https://badge.blue">badge.blue</a> attestations · <a href="https://atproto.com">ATProtocol</a></p>
123 </div>
124</footer>
125</body>
126</html>