> ## Documentation Index
> Fetch the complete documentation index at: https://olanas.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Content payments

> How Olanas protects content and verifies direct onchain payments.

The current Olanas application is a non-custodial-style content paywall: buyers transfer funds directly to the creator address specified by the listing, and the server verifies the transaction before delivering content.

## Payment lifecycle

```mermaid theme={null}
sequenceDiagram
  participant C as Creator
  participant O as Olanas
  participant B as Buyer
  participant R as Robinhood Chain
  C->>O: Upload content and sign listing
  O->>O: Encrypt and store content
  B->>O: Request protected download
  O-->>B: HTTP 402 payment requirement
  B->>R: Send exact onchain transfer
  B->>O: Submit transaction hash and payer
  O->>R: Verify recipient, asset, amount, and success
  O-->>B: Deliver decrypted content
```

## Verification rules

* The network must match the listing requirement.
* The transaction must be successfully mined.
* Native transfers are checked against the recipient and value.
* ERC-20 transfers are checked through the configured token contract's `Transfer` event.
* The payer, recipient, currency, and exact amount must match.
* A payment proof cannot purchase a different requirement.

## Custody and fees

The current implementation sends payments directly to creators. It reports a facilitator fee of zero and does not submit transfers for buyers.

<Info>
  This application uses a custom payment proof around HTTP status `402`. Compatibility with another x402 implementation should not be assumed.
</Info>

## Content storage

Uploaded content is encrypted before local persistence. Optional IPFS pinning uploads ciphertext, not plaintext. Operators must back up the encrypted data and the configured vault secret together.