Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions docs/facilitator-readiness.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Mainnet facilitator compatibility

Checked **1 October 2026** with public documentation and unauthenticated `GET /supported` and `GET /pricing` requests only. No payment was signed, verified, submitted or settled. Nothing here selects a provider, enables either payment rail, or installs a trusted sponsor.

## Public exact-payment option: PayAI

The [official Solana mainnet guide](https://docs.payai.network/x402/solana-mainnet-express) documents `https://facilitator.payai.network` for x402 v2 exact native-USDC payments. Its current tested example uses `@x402/*` 2.27.0; Allowance pins 2.25.0. Their request envelopes match the installed SDK and Allowance's bounded adapter, but discovery compatibility does not establish funded interoperability.

At 06:20 UTC, [public discovery](https://facilitator.payai.network/supported) returned HTTP 200 with v2 `exact` for `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`, and `extra.feePayer` was `CjNFTjvBhbJJd2B5ePPMHRLx1ELZpa8dwQgGL727eKww`. This is dated observation, **not a permanent configuration value**. Obtain the response again through the same authentication lane used for settlement, review the sponsor, and explicitly configure `TRUSTED_FEE_PAYER`. A changed sponsor must fail closed until reviewed.

The response also included legacy v1 names such as `base-sepolia` and `solana`. Allowance now validates these separately and removes all v1 capabilities before exposing discovery to its v2 client. Malformed v2 identifiers still reject the entire response, and actual spending still requires the configured network, exact scheme and pinned sponsor.

The [authentication guide](https://docs.payai.network/x402/facilitators/authentication) permits ordinary exact payments without credentials within the public allowance. Authenticated service uses a short-lived Ed25519 JWT generated from a merchant key ID and secret; a raw API secret is not a bearer token. Authenticated discovery can return an account-specific sponsor. Allowance's current static `FACILITATOR_TOKEN` does not refresh these JWTs: sustained authenticated PayAI service needs an auth adapter or compatible gateway. Do not paste a private key into that setting.

The [pricing guide](https://docs.payai.network/x402/facilitators/pricing) gives new receiving wallets **1,000 lifetime free credits**, not a monthly allowance. Shared host/IP pools can exhaust access earlier. Beyond that allowance, credits cost $0.001 each and settlements are priced at measured network gas plus 30%. The [live rate table](https://facilitator.payai.network/pricing), read at 06:20 UTC, listed mainnet exact transfers at 1.62 credits ($0.00162) each, effective 27 September 2026. Rates can change. This service charge is separate from an API's USDC price.

The [capacity guide](https://docs.payai.network/x402/facilitators/capacity-and-limits) warns that a timeout or `settlement_pending` can leave the transaction unresolved, including an empty Solana transaction field. Allowance retains its original authorization and conservative hold; a read of `/supported` cannot validate that recovery against a real provider. Token-account initialization also requires separate funding; sponsorship of the purchase does not create the required merchant USDC account.

## Authenticated alternative: Coinbase CDP

The [CDP facilitator documentation](https://docs.cdp.coinbase.com/x402/seller/facilitator) lists v2 exact Solana mainnet and requires a CDP API key ID and secret. It advertises 1,000 free onchain transactions each month and $0.001 per additional transaction. The [production guide](https://docs.cdp.coinbase.com/x402/seller/production-configuration) uses `createCdpFacilitatorClient` for authentication; direct REST requests require signed bearer JWTs. Allowance needs a compatible authentication adapter or gateway before this is a durable alternative. The documented endpoint is `https://api.cdp.coinbase.com/platform/v2/x402`; no authenticated request was made.

The default public test endpoint, `https://x402.org/facilitator/supported`, returned HTTP 200 but **no v2 exact Solana mainnet capability** at this check. Its successful response is not evidence that it can settle mainnet purchases.

## Still required for a real payment

Provision the persistent backend and operator access, an explicit mainnet RPC, dedicated payer key, initialized and funded payer USDC account, separate initialized merchant USDC account, reviewed sponsor, and bounded spending authorization. Select a provider whose account or public allowance is available from the deployed host. Then run the documented preflight and one intended funded scenario, preserving uncertain outcomes and independently checking chain evidence. The absence of a facilitator API key alone is not necessarily a blocker for PayAI's public exact lane; absent payer funds, signing authority and merchant configuration remain blockers.
29 changes: 29 additions & 0 deletions docs/launch-film.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
# Allowance launch film

The landing page includes the supplied 30-second brand film under **Watch launch film**. It sits after the interactive allowance story and links separately to the recorded app walkthrough at `/demo#product-tour`.

The film uses the approved curved A mark and shows a policy plan: a 0.040000 USDC allowance, 0.030000 in planned tool costs, and an additional request blocked before signing. Its receipt is explicitly labeled **Policy outcome** and **Policy plan · No funds moved**. This is brand storytelling; actual settlement evidence remains in connected workspace receipts.

## Supplied delivery and published copies

The delivery project is `allowance-showreel/out/deliver`. Its master, web delivery, and cover were kept unchanged. The site uses the supplied web delivery byte for byte, including its original music and sound effects. No voice or other audio was generated or substituted.

| Supplied file | Published file | SHA-256 |
| ------------------------------- | ----------------------------------------------- | ------------------------------------------------------------------ |
| `allowance-showreel-master.mp4` | Not copied into the site | `7c2e83519a5a7439562432ec215e56b8f12d1e04c005e77abf0ef8cdec931ef6` |
| `allowance-showreel-web.mp4` | `public/media/allowance-launch-film.mp4` | `ed934c2d40235a40abfe2135d532081ce73d1a0173b0c74bd16217d83ac9ef64` |
| `allowance-showreel-cover.jpg` | `public/media/allowance-launch-film-poster.jpg` | `8a61fab658fe876c5c92b2aea88c35428cc96d85da6bd73c96035305e65c1814` |

Web delivery: 9,384,026 bytes; 30.000 seconds; H.264, 1920 × 1080, 60 frames per second; stereo AAC at 48 kHz. Its MP4 metadata precedes the media payload, so playback supports progressive loading. The 18,099,480-byte master remains in the supplied delivery folder.

The delivery project's README credits Tatamusic's **Stylish Fashion Show Music** from Pixabay and describes a music/SFX soundtrack. This attribution comes from the supplied project documentation. The integration does not add narration or claim that the footage verifies a payment.

## Playback and access

- The film waits for an explicit Play action, with `preload="none"` and native playback controls. It does not autoplay or change the existing decorative film preferences.
- The supplied cover stays visible before playback. The layout reserves its dimensions to prevent a page jump.
- **Read the visual story** provides an accurate text alternative for the on-screen scenes. There was no speech transcript or caption file in the delivery folder; no speech captions were invented.
- A readable failure message, the text alternative, and the actual app walkthrough remain available if media cannot load.
- **Save film** downloads the original web delivery.

Browser coverage is in `tests/browser/launch-film.spec.ts`: no initial MP4 fetch, user-initiated playback and metadata, exact download hash, phone layout, and failure recovery. The supplied footage was inspected using a contact sheet and full-resolution policy-outcome frames; this review found no claimed verified transaction or transaction signature.
2 changes: 2 additions & 0 deletions docs/live-setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,8 @@ Keep `LIVE_PAYMENTS_ENABLED=false` and `DIRECT_PAYMENTS_ENABLED=false` during in

Canonical network values are fixed in `shared/domain.ts`: mainnet `solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp`, native USDC `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v`, six decimals. These match the [official x402 exact SVM specification](https://github.com/x402-foundation/x402/blob/main/specs/schemes/exact/scheme_exact_svm.md) and [Circle USDC contract addresses](https://developers.circle.com/stablecoins/usdc-contract-addresses), checked 19 September 2026. A supported response is compatibility evidence, not payment proof.

See the [dated facilitator compatibility check](facilitator-readiness.md) for PayAI's public exact-payment allowance, current discovery evidence, and authentication limitations of this client.

## Mainnet direct-payment configuration

Direct transfers use the same dedicated payer, payment network/RPC and shared daily ceiling, with their own mandate limits. Explicitly set `PAYMENT_NETWORK=mainnet`, `PAYMENT_RPC_URL`, `MAINNET_PAYMENTS_ACKNOWLEDGED=true` and, only after reviewing the intended capability, `DIRECT_PAYMENTS_ENABLED=true`. This rail does not require `LIVE_PAYMENTS_ENABLED`, a merchant recipient, facilitator or sponsor. The network default remains mainnet; the [direct-payment guide](direct-payments.md) deliberately uses explicit devnet settings for its funded verification procedure.
Expand Down
1 change: 1 addition & 0 deletions playwright.hosted.config.ts
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ export default defineConfig({
'pwa.spec.ts',
'navigation.spec.ts',
'product-tour.spec.ts',
'launch-film.spec.ts',
],
timeout: 60000,
expect: { timeout: 15000 },
Expand Down
Binary file added public/media/allowance-launch-film-poster.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added public/media/allowance-launch-film.mp4
Binary file not shown.
24 changes: 17 additions & 7 deletions server/payments/facilitator.ts
Original file line number Diff line number Diff line change
Expand Up @@ -54,14 +54,24 @@ const verificationSchema = z.object({
const supportedSchema = z.object({
kinds: z
.array(
z.object({
x402Version: z.number().int().min(1).max(2),
scheme: z.string().max(64),
network,
extra,
})
z.discriminatedUnion('x402Version', [
z.object({
x402Version: z.literal(1),
scheme: z.string().max(64),
network: z.union([network, z.string().regex(/^[a-z0-9][a-z0-9-]{0,127}$/)]),
extra,
}),
z.object({
x402Version: z.literal(2),
scheme: z.string().max(64),
network,
extra,
}),
])
)
.max(128),
.max(128)
// Providers advertise legacy names alongside CAIP-2 kinds; this client only uses v2.
.transform((kinds) => kinds.filter((kind) => kind.x402Version === 2)),
extensions: z.array(z.string().max(128)).max(64).default([]),
signers: z.record(z.string(), z.array(z.string().max(128)).max(64)).default({}),
});
Expand Down
8 changes: 5 additions & 3 deletions src/App.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,7 @@ import LandingStory from './LandingStory';
import PolicyLab from './PolicyLab';
import WorkspaceShell, { getWorkspaceView } from './WorkspaceNav';
import ProductTour from './ProductTour';
import LaunchFilm from './LaunchFilm';

function Logo({ compact = false }: { compact?: boolean }) {
return (
Expand Down Expand Up @@ -475,9 +476,9 @@ function Landing() {
<Link to="/demo" className="text-link">
Open walkthrough <ArrowRight size={16} />
</Link>
<Link to="/developers" className="text-link">
See how it works <ArrowRight size={16} />
</Link>
<a href="#launch-film" className="text-link">
Watch launch film <ArrowRight size={16} />
</a>
</div>
<div className="hero-reassurance">
<span className="overlap-circles">
Expand Down Expand Up @@ -542,6 +543,7 @@ function Landing() {
/>
</section>
<LandingStory />
<LaunchFilm />
<section className="principles page-width" aria-label="How Allowance works">
<div className="section-label" data-reveal>
<span>Enough freedom to be useful.</span>
Expand Down
129 changes: 129 additions & 0 deletions src/LaunchFilm.tsx
Original file line number Diff line number Diff line change
@@ -0,0 +1,129 @@
import { useRef, useState } from 'react';
import { ArrowDownToLine, ArrowRight, Film, Play } from 'lucide-react';
import { Link } from 'react-router-dom';
import './launch-film.css';

export default function LaunchFilm() {
const video = useRef<HTMLVideoElement>(null);
const unavailable = useRef(false);
const [started, setStarted] = useState(false);
const [failed, setFailed] = useState(false);
const [message, setMessage] = useState('');
function playbackFailed() {
unavailable.current = true;
setFailed(true);
setMessage(
'The launch film could not load. Read the visual story below or open the app walkthrough.'
);
}
async function play() {
const player = video.current;
if (!player || failed) return;
setMessage('');
try {
await player.play();
} catch {
if (!unavailable.current && !player.error)
setMessage('Press play in the video controls to start the film.');
}
}
return (
<section
className="launch-film page-width"
id="launch-film"
aria-labelledby="launch-film-title"
>
<div className="launch-film-heading">
<div>
<div className="eyebrow">
<Film size={14} aria-hidden="true" />
The launch film / 00:30
</div>
<h2 id="launch-film-title">
A little independence.
<br />
<span>A clear limit.</span>
</h2>
</div>
<p id="launch-film-context">
A short brand story about useful agents and the boundaries you set. Planning scenes. No
funds moved.
</p>
</div>
<div className="launch-film-screen">
<video
ref={video}
controls
playsInline
preload="none"
poster="/media/allowance-launch-film-poster.jpg"
aria-label="Allowance launch film"
aria-describedby="launch-film-context"
onPlay={() => {
setStarted(true);
setMessage('');
}}
onError={playbackFailed}
>
<source
src="/media/allowance-launch-film.mp4"
type="video/mp4"
onError={playbackFailed}
/>
Your browser cannot play this film. Read the visual story below.
</video>
{!started && !failed && (
<button type="button" className="launch-film-play" onClick={() => void play()}>
<span>
<Play size={18} fill="currentColor" aria-hidden="true" />
</span>
Play launch film
</button>
)}
</div>
<p className="launch-film-status" role="status">
{message}
</p>
<div className="launch-film-footer">
<div>
<b>Behind the idea.</b>
<span>Budgets, useful work, and the decisions in between.</span>
</div>
<a href="/media/allowance-launch-film.mp4" download="allowance-launch-film.mp4">
<ArrowDownToLine size={15} aria-hidden="true" />
Save film
</a>
<Link to="/demo#product-tour">
Open the app walkthrough <ArrowRight size={16} aria-hidden="true" />
</Link>
</div>
<details className="launch-film-story">
<summary>Read the visual story</summary>
<p>This description follows the on-screen scenes in the supplied launch film.</p>
<ol>
<li>
<b>A little independence.</b> The red Allowance A takes shape, followed by “Give your
agent a budget.”
</li>
<li>
<b>You decide what’s enough.</b> A policy card sets a 0.040000 USDC allowance, a
0.020000 per-request cap, daily capacity, and permitted tools.
</li>
<li>
<b>Small purchases. A fuller picture.</b> A wallet snapshot and a transaction
explanation bring planned tool costs to 0.030000 USDC, leaving 0.010000.
</li>
<li>
<b>Blocked before signing.</b> Another 0.020000 request exceeds the remaining allowance.
The policy outcome keeps the permitted requests and the blocked decision together,
marked “No funds moved.”
</li>
<li>
<b>Find the right amount of freedom.</b> A sculptural red A stands above the water. The
film closes with the Allowance identity and an invitation to explore the policy lab.
</li>
</ol>
</details>
</section>
);
}
Loading
Loading