Mayan: swap routes, protocol fees, refund assets and deposit addresses

Mayan is a wallet-based token-swap service with several cross-chain execution methods. The application lets a user choose the source asset and network, the destination asset and network, and review the expected output before signing. Route selection matters: the fee, settlement mechanism and refundable asset can differ between transactions that appear similar in the interface.[8]

The quote interface can return two alternatives: the fastest route and the route with the best expected return. It returns one if the same route serves both purposes. An estimated arrival time is a quote field, not a contractual deadline for payment. Slippage settings and the quoted minimum receivable amount remain relevant when comparing the alternatives.[9]

The published network list includes EVM chains, Solana and Sui, among others. Direction flags identify whether a chain is active as an origin or destination. A listed network should therefore not be interpreted as proof that every token, direction and execution method is currently available.[10]

For an assumed 10,000-USDC fee base, 3 basis points equals 3 USDC and 10 basis points equals 10 USDC. These calculations isolate the published protocol component for the applicable route; they do not estimate price impact, gas, a partner charge or the net destination amount.[5][6]

The live quote’s protocolBps field is the relevant transaction-level check because rates can change. Integrators can add a referrer fee. Relayer fields cover different steps and can be denominated in different tokens; the aggregate clientRelayerFeeSuccess field should not be added again to the individual costs it already includes. A refund relayer charge applies to the refund path. Published maximum integrator fees are limits on configuration, not universal customer prices.[7]

An unfilled ordinary swap becomes refundable after its deadline. The refund can be in the asset actually locked for the route: Swift may return USDC or ETH after an initial conversion rather than the token the user originally supplied. The quoted refund relayer fee can reduce the returned balance. A refund therefore does not promise restoration of the original token quantity or reversal of earlier market conversions.[15]

A gasless order can be identified by an order hash instead of a source-chain transaction hash. This changes what should be supplied to a status lookup or support request. It does not justify sending the same payment again merely because the usual wallet transaction list does not display a conventional source transaction.[13]

Mayan publishes links to OtterSec and Sec3 reviews for identified contract and program scopes, including Swift and MCTP versions. The existence of those reports is useful evidence of review activity, but it is not customer insurance or a guarantee that every subsequent deployment, route dependency or integration is free from defects. This profile has not independently re-audited those systems.[16]

The terms require legal capacity and lawful use, including sanctions compliance. They do not support treating an accessible interface as a positive country-by-country eligibility decision. This review did not establish a universal acceptance list or a blanket US exclusion from the inspected terms.[3]

Mayan describes address screening using Chainalysis and Hermod risk information. Flagged addresses can be prevented from processing transactions, with compliance questions directed to official support. The ability to connect a self-custody wallet does not exempt a transfer from those checks.[17]

The privacy policy identifies wallet addresses and public blockchain activity among the information used by the service, alongside website and analytics data. Wallet-based access should not be equated with anonymous activity or a promise that no transaction information is processed.[2]

The ordinary refund guide ties recovery to the order deadline and execution outcome. It does not establish an instant cash withdrawal or a universal manual reversal. When an order is unresolved, the original route, input token and final status are needed to determine whether the expected result is a destination payment or a source-side refund.[15]

The named operator is Sand Lake Labs, Ltd., doing business as Mayan Finance. The reviewed privacy policy does not establish its incorporation jurisdiction. A governing-law clause should not be used to fill that gap.[2]

The terms state that the service is not registered with a government agency. That is an operator statement, not an independently verified worldwide regulatory conclusion. They also provide for New York law and JAMS arbitration, with an aggregate USD 100 liability cap subject to applicable exceptions. That contractual cap is not an insured balance or compensation scheme.[3]

The documentation reports more than USD 20 billion moved, nine million swaps and three million users. These are provider-published cumulative figures observed on 21 October 2026. They do not identify current funded accounts, monthly active traders or independently audited exchange turnover.[1]

Mayan announced the launch of Mayan 2.0 on 24 March 2026, describing changes to auctions, execution and downstream application actions. That release is a dated product milestone. Its marketing comparisons with earlier performance are not used here as an independently measured speed or cost benchmark, and its older activity totals are not mixed with the current documentation figures.[24]

Operator

Sand Lake Labs, Ltd. (d.b.a. Mayan Finance)

Exchange model

Decentralised

Service scope

Wallet-based token swaps using Swift, MCTP, Fast MCTP and Wormhole routes; developer integrations include reusable deposit addresses.

Client types

Retail clients; Professional clients; Institutional clients

Pricing publication

Public and quoted pricing

Other names

Mayan Finance

Pricing scope

Route-specific protocol charges plus quoted relayer, conversion and possible integrator costs.

Funding scope

Supported-chain wallet transactions, with selected gasless and destination-gas options; refund assets depend on the route.

Custody and asset handling

Users authorise from their own wallets; route-specific contracts, drivers and cross-chain verification handle settlement.

Client eligibility

Legally capable users satisfying the terms, sanctions requirements and transaction-screening controls.

Support

Official email, Discord links and public transaction explorer; no response-time guarantee tested.

Authorisation and registration scope

The operator states the service is not agency-registered; this review does not establish a financial licence or compensation scheme.

Exchange metadata checked 21 Oct 2026Source 2Source 1Source 8Source 3Source 16Source 4Source 12Source 7Source 17Source 13Source 14Source 15

The quote API and SDK can be used without an API key, with higher limits available through an approved request. This access obtains quotes and transaction instructions; the application still needs the appropriate wallet signer. The documented mobile SDK paths do not establish a separate Mayan custodial account or identical functionality on every device.[11][12]

Zaps can pass a payload to a destination application, which must decode and validate it. That integration capability does not make Mayan the manager of the resulting position. Its AI guidance likewise describes coding-assistant access to technical workflows, including signer-dependent execution; it does not establish a managed AI investment service or an independent mandate to spend customer funds.[22][23]