Wert: crypto checkout, partner fees and wallet delivery

The production asset list includes Bitcoin, Ethereum, Solana, stablecoins and network-specific tokens. USDC is listed on several chains, while Ethereum purchases also have multiple network options. The same ticker is therefore insufficient to specify delivery. The production and sandbox tables are separate, and test tokens in the integration environment should not be counted as customer assets.[21]

Wert publishes a production demonstration page with an explicit notice that the card will be charged. It is not a practice trading balance. A business evaluating the integration has separate sandbox tooling; a customer using the production checkout is authorising a real purchase if they complete it. This profile did not submit a payment or test a live order.[26][21]

The 4% customer article and the negotiated partner terms should be read together. A partner’s particular rate, service charge or sponsorship can change the amount charged on that integration. For a hypothetical $100 purchase, a 4% processing component would be $4 before considering the separately identified network fee and spread. That illustration explains the percentage; it is not a quote for a particular asset or checkout.[7][20]

The final confirmation displays the crypto amount, exchange rate and fee breakdown for approval. The short rate-lock window is relevant during checkout, especially if authentication or verification interrupts the flow. It should not be confused with how long the user remains logged in. The documentation uses different clocks for a quote, an integration token and an authenticated widget session.[7][20][22][5]

The customer’s Profile → Details and Limits screen is the documented place to see current KYC status and available allowance. The public help pages use euros while partner documentation uses dollars. A profile that shows a specific currency and remaining allowance is more useful than assuming that both written numbers describe the same amount at every exchange rate. NFT allowances also differ from crypto allowances and should not be imported into the onramp limit.[8]

A failed order can still appear as a reserved amount in the banking app. Wert’s card-hold guide explains that a bank can retain a temporary authorisation for hours or days, with the bank responsible for confirming its release timing. If the bank says no hold remains or cannot resolve the discrepancy, Wert support can investigate the payment reference. An authorisation release is different from a completed refund of a captured payment.[14]

The item purchased matters when allocating a delivery complaint. For an ordinary onramp transaction, the blockchain transfer can establish delivery of crypto to the address. For a token sale or external-platform purchase, Wert’s guide directs the customer to the partner when payment has completed but the project’s item or entitlement has not arrived. The receipt and transaction hash help identify which stage has actually failed.[12]

Wert says it neither creates customer wallets nor stores their private keys or recovery phrases. Its role in ordinary delivery is to use the public address supplied for the purchase. The receipt identifies that destination. If a partner creates the wallet, that partner’s access and recovery arrangement must be understood separately from the Wert login used for purchasing.[11][18]

This distinction remains relevant after a failed partner transaction. Crypto received through failover may sit in a wallet even though the intended project action did not execute. The customer needs the means to control that wallet to use the crypto later. Recovering access to the purchase profile cannot recreate an unrelated wallet’s private key.[13][18]

For card-removal requests, the guide requires document verification and proof of ownership, with special alternatives where the card is digital or no longer physically held. The published procedure asks that sensitive card digits be concealed except the last four. This is a manual support process, not an advertised instant switch that can be assumed to work identically on every device.[15]

Wert’s broad country-count claims vary between product pages and pricing pages. They describe reach rather than an independently verified permission map. The specific service column, state restriction and partner route carry more useful information for an individual purchase. For UK crypto buying, the conflicting pages do not justify a confident statement that access has been restored.[2][3][9][1]

The partner page describes passwordless login with an OTP each time the customer signs in. An OTP problem can arise from mobile reception, carrier filtering or the phone’s spam controls. Wert publishes troubleshooting for those possibilities and directs unresolved cases to its official support. A delayed code is therefore not itself evidence of a failed wallet transfer: authentication and blockchain delivery are different stages and should be investigated using their own references.[16][12][5]

The customer help article identifies [email protected] and the wert.io domain as its official contact environment, and says the company does not approach customers through Telegram, WhatsApp or social-media direct messages. A partner-specific help desk may still be necessary for a token sale or item-delivery complaint. The appropriate contact depends on the failed stage rather than merely the logo visible when payment began.[6][12]

Past orders and downloadable receipts are available in the profile, according to the limits guide. The emailed receipt provides the destination address and a blockchain link for delivery checks. Retaining those records before closing a profile helps connect a card payment with the resulting wallet transfer. No universal jurisdiction-specific tax calculation or standard post-closure export service was established by the material reviewed.[8][11][12][19]

The distinction between a published company statement and a verified permission matters here. Wert’s onramp page uses licensing language and links the MSB document, but the document has a narrower meaning and an older date. Public service availability also does not resolve whether a particular customer contracts with the US or Estonian company. That allocation is a material contractual detail still requiring the current checkout agreement.[2][24][4]

Wert describes a 2020 founding and publishes offices in Tallinn and Oakland. Its public team page names George Basiladze as founder and Daria Bogatyreva as co-founder. These details explain the brand’s background; they do not establish transaction volumes or the number of currently active buyers. The research did not find a directly comparable audited turnover figure for ranking this checkout service alongside large order-book exchanges.[4]

Operator

SHA2 Solutions Inc. and SHA2 Solutions OÜ; exact regional transaction allocation requires the checkout agreement

Exchange model

Centralised

Service scope

Fiat-to-crypto purchases through a checkout that delivers to a wallet or supports a partner transaction. NFT checkout is separate; an order-book trading account is not described.

Client types

Retail clients

Pricing publication

Public and quoted pricing

Pricing scope

Customer help publishes 4% processing plus network fee and spread; partner documentation permits contracted rates, a $1/€1 minimum, partner service fees and sponsorship.

Funding scope

Eligible Visa/Mastercard, Apple Pay, Google Pay, SEPA and Cash App routes; USD/EUR checkout. Certain additional card networks are NFT-only.

Custody and asset handling

Wert says it does not create customer wallets, hold wallet balances or access private keys. Partner-created wallets and partner-delivered items have separate responsibilities.

Client eligibility

Location, US state, partner and verification restrictions apply. UK onramp availability is inconsistent between the country table and the homepage banner; no clear current UK permission is asserted.

Support

Live chat in the official help centre and [email protected]. General office contacts are published separately.

Authorisation and registration scope

Website names Estonian and US operators. A company-hosted July 2025 FinCEN transcript records Sha2 Solutions, Inc. as an MSB; this is not a current independently verified worldwide or state licence. No MiCA authorisation is asserted.

Exchange metadata checked 21 Oct 2026Source 4Source 6Source 2Source 20Source 7Source 11Source 24

The partner FAQ states that an authenticated widget session lasts 60 minutes by default and can be extended to 24 hours for an individual partner integration. Separately, the current session-creation API returns a one-use token valid for 30 seconds. Neither interval is the 30-second exchange-rate lock described in the customer fee guide. Treating these three clocks as one timeout would misdescribe both price validity and login persistence.[20][22][7]

The current API guide lets partners create a user-selected flow or lock the asset, amount, network and destination for a specified use. It warns that the integration key has substantial privileges and should remain on the partner backend. This is a business integration credential, not evidence that a retail user has authorised an autonomous bot to spend wallet funds.[22]

An older multiple-address integration guide says supplied wallet addresses can be pre-filled and edited. The current session guide also supports a restricted mode with locked values. The difference is configuration: a partner’s onramp can expose different user choices depending on the mode it implements. The visible destination and transaction summary therefore remain important even when an address arrives automatically from the partner’s app.[23][22]