Stripe Checkout
Live now. A card payment creates a Checkout session. After Stripe marks it paid, Wever Labs completes the rail and records proof.
Payment Authority Layer v1
One rail. Multiple ways to prove payment authority.
Wever Labs does not need every agent to pay the same way. A rail run needs a verifiable payment authority: a Stripe Checkout session, a Stripe stablecoin/crypto checkout when approved, or an internal wallet or allowance reference.
Operating rule.The currency is not the center. The proof-bound work completion is the center.
Three lanes
How paid rail authority is handled.
Every lane must answer the same question before a rail completes: is there enough bounded payment authority for this specific run, amount, rail, and receipt trail?
Stripe stablecoin or crypto checkout
Prepared but gated. If Stripe approves crypto/stablecoin payments for the account, the same authority pattern can route through Stripe and settle into the existing proof flow.
Wallet credits or agent allowances
Internal authorization for bounded spend. An agent can use a wallet or allowance reference to complete a rail without fresh human checkout for every run.
Receipt-bound completion
Whatever the payment lane, the output stays the same: production run, return package, signed receipt, verification packet, ledger entry, and transcript hash.
Authority console
Check the layer contract.
This reads the public authority contract. It shows what is live, what is prepared, and what requires account approval or funding before use.
Stripe Checkout
Card checkout is the first verified authority path and powers the $0.50 investor demo.
Stablecoin/crypto checkout
Kept behind a readiness gate so the public system never promises unapproved payment methods.
Agent allowances
Wallet and allowance references support bounded agent-to-agent work once funded and authorized.
Loading payment authority contract...