---
title: Payments Overview
description: How customers fund runs via wallet and bundles, how Stripe and Stripe Connect support checkout and creator payouts, and how legacy unlock purchases coexist with per-run billing.
source: https://www.edgaze.ai/docs/payments-overview
last_updated: 2026-03-15
section: legal
---
# Payments Overview

> How customers fund runs via wallet and bundles, how Stripe and Stripe Connect support checkout and creator payouts, and how legacy unlock purchases coexist with per-run billing.

## Overview

Edgaze uses **Stripe** for buyer checkout (wallet top-ups, locked bundles, and legacy unlock purchases) and **Stripe Connect** for creator payout onboarding and payout rails. Per-run workflow listings charge a single displayed price per successful run. Buyers fund runs through a **wallet**, a **locked bundle** (5 or 10 prepaid runs for one workflow version), or the **API** path, which draws from wallet balance.

Customers buy access to hosted Edgaze product experiences. They do not buy ownership of creator prompts, workflow logic, source code, model access, or Edgaze infrastructure. Read the [Billing guides](/docs/billing) for step-by-step funding and charge detail.

## Funding Doors

### Wallet

Buyers may top up a platform wallet (minimum top-up rules apply). Wallet balance works across workflows. At run trigger, if no eligible bundle applies, Edgaze debits wallet balance for the displayed per-run price.

### Locked bundles

Buyers may purchase a **5-run** or **10-run** bundle for a specific workflow version at the per-run displayed price times bundle size. Bundles require a minimum total charge. Draw order at trigger is **bundle first, then wallet**. Failed runs do not consume a bundle run.

### API runs

API-authenticated runs use the same billing path as wallet runs after API key auth and spend-cap checks.

## Per-Run vs Legacy Unlock

Edgaze supports two marketplace purchase models:

| Model                 | How it works                                                                                                                                               |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Per-run** (current) | Creator sets margin; buyer pays margin plus compute displayed per successful run via wallet, bundle, or API. Creator earns 80% of margin per run.          |
| **Legacy unlock**     | Older listings used a one-time checkout price before per-run pricing existed. Access follows unlock terms; earnings follow the split recorded at purchase. |

New paid workflow listings use the per-run model. Read [Legacy Unlock](/docs/billing/legacy-unlock) for identification rules and buyer behavior.

## What Customers Buy

### Workflow products

For per-run workflow products, buyers pay per successful hosted run (or prepay runs via bundle). Displayed price is fixed within the input envelope.

### Prompt products

For prompt products, a purchase provides access to the prompt product experience packaged and delivered through Edgaze at the listed unlock price.

### Access limitations

Access can be affected by payment status, refund status, dispute status, account status, wallet or bundle balance, BYOK requirements, product availability, safety review, version pinning, or policy enforcement.

## Money Flow (Per-Run)

| Step        | What Happens                                                                            |
| ----------- | --------------------------------------------------------------------------------------- |
| Funding     | Buyer tops up wallet or buys a bundle via Stripe checkout.                              |
| Trigger     | Edgaze reserves the run price from wallet or bundle.                                    |
| Success     | You are charged the displayed price; the creator earns 80% of margin.                   |
| Failure     | The margin charge is released; a bundle run is not used; Edgaze may cover compute used. |
| Payout path | Stripe Connect onboarding and eligibility control creator payout release.               |

## Creator Share

Unless a separate written agreement applies, the default split is **80% of creator margin** to the creator and **20% of creator margin** to Edgaze on each successful run. Compute is not part of creator earnings.

Stripe processing fees on checkout are handled from Edgaze's platform-side economics and are not deducted from the creator margin share.

## Stripe's Role

Stripe handles card processing, checkout sessions, payment intents, refunds, disputes, and parts of tax or payment compliance where configured. Stripe Connect handles creator onboarding, verification, and payout rails.

Stripe's availability, terms, fees, verification decisions, dispute process, account restrictions, and payout timing may affect transactions.

## Taxes

Taxes, VAT, GST, sales tax, and similar obligations may be calculated, collected, or displayed by Stripe where configured. Edgaze does not guarantee that every tax obligation is automatically handled for every transaction, creator, or jurisdiction.

Creators and customers remain responsible for their own tax obligations unless applicable law states otherwise.

## Refunds and Chargebacks

Refunds and disputes can reverse purchase status, revoke access, reduce creator net amounts, or adjust balances. Wallet refund requests follow the [Refund Policy](/docs/refund-policy). Chargebacks are handled through Stripe and card networks.

Read [Refund Policy](/docs/refund-policy) and [Chargeback Policy](/docs/chargeback-policy) before buying or selling.

## Related Policies

- [Funding Runs](/docs/billing/funding-runs)
- [Marketplace Fees](/docs/marketplace-fees)
- [Creator Earnings](/docs/creator-earnings)
- [Payout System](/docs/payout-system)
- [Pricing Limits](/docs/pricing-limits)