No. Paybrok is not a bank.
Paybrok is designed as a non-custodial wallet. Users control their wallet credentials. Escrow flows may lock funds for a specific order, but the base wallet model is self-custody.
No. If the user loses the recovery words and local wallet storage is gone, Paybrok cannot recover the wallet.
Escrow means funds are locked while an order or service is being completed. Funds are released when conditions are met or reviewed during a dispute.
A provider is a person or business that delivers a service, local payment, liquidity, or remittance bridge. In a service example, the architect is the provider.
Yes. Paybrok supports protected service payments by milestones. For example, a 100 USDC architecture project can be split into 30/40/30 USDC releases.
Paybrok can scan or process local QR/payment-link data where available. Some QR systems only expose a proprietary link; in those cases Paybrok preserves the link/reference and shares it with compatible providers.
Paybrok web wallet logic applies to web browsers. However, browser storage can vary between Safari, Chrome, private mode, and other browser containers. Users should keep recovery words safe.
No. Freighter is an advanced option for web users who already use it. Paybrok also supports a web wallet flow with local encrypted vault.
No. Availability depends on country, platform, provider liquidity, compliance, asset support, and operational configuration.