Route isolation
Public swaps, Aethra surfaces, partner embeds, and internal canaries are treated as separate route surfaces so experimental behavior does not quietly leak into buyer flows.
Can my pilot stay inside the route rules we approve?
Execution integrity
The trust layer behind a partner swap pilot.
Aethra is not just a branded swap page. It is a non-custodial execution layer that helps a buyer show what the user reviewed, what route was checked, what fees were disclosed, and what support can prove after the fact.
This page is written for product, security, support, and compliance teams reviewing a controlled pilot. It explains the checks without exposing raw transactions or turning the product into an operator console.
Buyer outcome
Aethra White-Label Swap Kit
Your team can test one controlled swap flow, see exactly what users review and sign, and receive support-safe evidence without taking custody.
Strongest demo line: route checked, fees shown before signing, wallet confirmation required, receipt generated after execution.
Selected route preservation
The route shown to the user is expected to remain the route used for build and wallet review. A stale or mismatched candidate should fail before signing.
Can support explain what route the user reviewed?
Fee truth
Known partner, platform, network, and route-fee context is surfaced before wallet confirmation and preserved for support review where available.
Can users see material fee context before signing?
Wallet-review safety
Aethra prepares transactions for user wallet review only after route, freshness, transaction shape, and policy checks pass for the configured flow.
Does the user still make the final wallet decision?
Receipt trail
Successful and failed attempts can produce support-safe evidence showing quote, build, wallet review, submit, and status context without exposing raw payloads.
Can support answer what happened without asking for secrets?
Partner policy controls
Partner pilots can start with approved assets, route posture, support links, proof delivery, and manual production review before broader rollout.
Can we start narrow and expand only after review?
Pilot review checklist
What a buyer should inspect before production review.
The point is not to claim perfect execution. The point is to prove the pilot is bounded, reviewable, non-custodial, and supportable before broader rollout.
Allowed surface and partner policy
Quote freshness and selected route identity
Fee disclosure posture
Wallet prompt readiness
Transaction fingerprint status
Receipt and proof availability
Support handoff path
Safe logging and data minimization
Non-custodial boundaries
Aethra does not custody user funds.
Users review and sign in their own wallet.
Aethra does not route through platform wallets.
Aethra does not trade on behalf of users.
Aethra does not provide financial advice.
Enterprise proof views exclude raw transactions, private keys, API keys, secrets, and unnecessary wallet data.
