01

Production & integrations

Powered by Fermah

Who runs on Fermah in production, what the current docs list separately, and what has been announced but is not currently listed as production. Nothing is here without a link and a date.

—ENTRIES
—LIVE / NAMED
—TESTNET / OTHER
2LIVE ON KERNEL

EVERY ENTRY CARRIES A SOURCE AND CHECK DATE · PAY TESTNET SOURCES CHECKED 2026-10-26

Product update · October 26, 2026

Fermah Pay on Stellar testnet.

Prepaid USDC accounts and seller billing, with sponsored transaction submission, replay protection, recurring mandates and an x402 facilitator interface. The October 26 announcement reports Tranche 1 on Stellar testnet; the public repository provides implementation and testnet evidence.

  1. Deposit once

    For the prepaid-ledger flow, the buyer signs a deposit authorization. USDC moves to a separate treasury and the contract credits the buyer’s ledger balance.

  2. Charge the ledger

    A charge moves credit from the buyer’s balance to seller revenue in the contract’s accounting. It does not transfer USDC between wallets on each charge.

  3. Sponsor submission

    A submitter signs the transaction and a separate fee account pays through Stellar fee bumps. Zero buyer fees means the buyer pays no network fee; the transaction still has a fee.

98 replays, no second debit

The published testnet record replays a previously settled batch of 98 charge IDs. All 98 return Duplicate and nothing is debited again. This is a recorded test case, not a guarantee against every failure mode.

September 29 testnet record ↗

Retries retain their identity

An API retry returns the original charge with created: false. The separate single-charge replay case is refused during pre-submission simulation as DuplicateCharge (error 110). The 98-entry batch replay is a distinct case that was included onchain.

Replay and API evidence ↗

Recurring mandates

The buyer authorizes a mandate once; billing follows its periods and limits. The recorded two-minute-period test checks an early second charge (not_due), a later valid charge, an expired mandate (mandate_expired), and revocation with allowance zero. The testnet CI workflow also exercises recurring billing.

Recurring testnet record ↗

A concrete x402 binding

The gateway documents /supported, /verify and /settle for x402 v2 batch-settlement on Stellar. Authenticated verification and settlement use buyer-signed commitments against prepaid funds. Admission and later onchain batch inclusion are separate steps.

x402 facilitator reference ↗

This record concerns Stellar testnet. It does not establish a production Mainnet release, an independent security audit or universal fee-free operation. The prepaid-ledger flow uses treasury custody and treasury-authorized withdrawals; the repository also describes a distinct vault flow, which should not be conflated with it.

What the announcement lists next

The October 26 thread names onchain risk monitoring/alerts and an ecosystem-partner testnet integration as work being closed out. That announcement does not establish completion of either item or identify the partner.

October 26 thread ↗

Sources checked 2026-10-26. Testnet evidence records retain their own dates; the September 29 replay record was discussed in the October 26 announcement.

Ecosystem graph

Who runs on what.

Solid lines show live relationships and docs-listed products. Dashed lines show testnet, announced, historical or open entries.

stated on official Fermah sources today testnet / announced / historical