Help / Getting Started

Receive native USDC into your own wallet and keep evidence of verified payments. Skavio never needs your private key or recovery phrase.

Five-minute quick start

Open My account, enter your business email and choose Send code. Enter the eight-digit code sent to your inbox. This both registers new users and signs in returning users.
Your seven-day trial starts automatically after verification. The setup guide opens inside your account. Back and Next save progress; Skip for now pauses it. Use Getting started / resume setup to reopen it later.
In Settings select your wallet’s network, choose Connect wallet and approve the ownership message in a compatible wallet.
In New payment → Get paid in USDC, select that wallet, enter an amount and description, then choose Create payment link.
Copy the generated link and send it to your customer. Ask them to follow its network, native USDC token and exact amount instructions.
Open Payments to track confirmation. When PAID, download the PDF receipt. Documents offers reports, CSV and issued invoices.

Five minutes is a guide to setup, not a promise about email delivery, wallet availability or blockchain confirmation time.

Wallet setup, step by step

A receiving wallet is an account on a blockchain where your customer sends tokens. You keep control of it. Only the public receiving address is recorded by Skavio.

Use a wallet that supports signing messages. For Base, Polygon PoS and Arbitrum One, use a compatible EVM browser wallet such as MetaMask. For Solana, use a compatible wallet such as Phantom.
On mobile, open Skavio in the wallet’s built-in browser if your ordinary browser does not provide a wallet connection. A hardware wallet needs a compatible browser-wallet connection that supports message signing. Skavio currently cannot verify a wallet solely by pasting its address.
Select the network in Settings. The same-looking address on another network does not mean your payment arrived on the chosen network.
Choose Connect wallet. Approve the selected account and network in your wallet, then read and sign the Skavio ownership message. This proves control of the address; it does not send USDC or give permission to debit it.
After success the wallet appears under Receiving wallets. Already verified wallets do not need to be signed again when you reopen the guide.

Never share a private key or recovery phrase. Skavio never requests them. If verification is rejected, the wallet is not added; fix the wallet/network problem and try again.

Supported networks and tokens

Receiving payments supports Base, Polygon PoS, Arbitrum One and Solana. Send native Circle USDC on the selected network. USDC.e, other bridged tokens, USDT and other tokens do not qualify. Subscription checkout currently offers Base and Polygon PoS; this does not change your receiving-wallet options.

Create, share and match a payment request

In New payment → Get paid in USDC, choose a receiving wallet, enter the amount, a clear description and optionally a customer or order reference. Choose Create payment link and Copy payment link. You can reopen any request from Payments.

Skavio adds a unique matching amount smaller than 0.01 USDC. For example, a request for 150.00 USDC may show 150.004219 USDC. This is an example, not a payment instruction. Always use the exact amount on your actual link, including all decimals. The watcher checks the native token, network, recipient, amount and blockchain confirmation. If you supply a known sender in Advanced options, sender matching also applies.

Ordinary matched payments are monitored automatically. If a verified transfer cannot be attributed confidently, REVIEW requires written evidence identifying the customer. Do not approve it based on an unverified screenshot.

Wrong token, network, address or amount

The request is not automatically PAID. Check the transaction in the appropriate block explorer and compare it with the link. Contact the customer and support with the transaction ID, network and request reference. Skavio cannot move, bridge, reverse or refund funds from your wallet. A transfer to another address may be unrecoverable. Do not send a second payment until you understand what happened.

Tracking and confirmation

AWAITING: Waiting for a matched, verified payment. A transaction may have been detected but still lack sufficient confirmation. Detection and confirmation are not separate stored request statuses.
REVIEW: A verified on-chain transfer needs your evidence identifying the payer. Use Match payer in Payments after checking it.
PAID: Payment verification and matching succeeded. Payment evidence is available.
EXPIRED: The request’s deadline passed. Do not assume a late or unmatched transfer has been accepted. Investigate the transaction before deciding what to do.

Confirmation times depend on the blockchain, finality and monitoring availability. The app’s monitoring indicator shows operational status; it does not promise instant settlement. Never treat a simulated demo or an unconfirmed transaction as real verified settlement.

History, evidence and invoices

Payments lists request history and links to customer payment pages. A PAID request offers a PDF receipt. Documents offers Download PDF report, Export CSV, accountant CSV and issued sales invoices. Sign in to access your own exports.

Payment evidence is not a legally compliant tax invoice. A receipt records verified token settlement. A sales invoice separately describes goods or services and the information you supplied. Review tax requirements with your accountant. USDC is not automatically valued at one USD for accounting; the optional accounting tools keep valuation evidence separate.

Trial limits and subscription pricing

The seven-day free trial starts once after email verification: 2 wallets, 12 requests, 12 invoices, 2 recurring schedules, 25 transactional email attempts, 1 API key and 1 webhook endpoint. Requests cannot outlast the access window. Signing in again never resets the trial.

Starter — 9.00 native USDC / 30 days

2 wallets · 50 requests and 50 invoices · 2 schedules · 25 transactional email attempts.

Business — 19.00 native USDC / 30 days

4 wallets · 200 requests and 200 invoices · 10 schedules · 100 transactional email attempts.

Pro — 29.00 native USDC / 30 days

6 wallets · No monthly request or invoice cap, subject to fair use · 20 schedules · 200 transactional email attempts.

Starter includes 1 API key and webhook endpoint, Business 3 of each, Pro 10 of each. Rolling 30-day usage applies. An issued invoice uses one invoice and one request allowance. All plans have fair-use guards: 300 requests/hour, 30 API invoice creations/hour, 20 transactional email attempts/hour, plus existing rate and anti-abuse limits. Failed or ambiguous email attempts can consume email allowance.

After expiration new requests require an active paid plan; existing history and exports remain available. Choose the next paid plan in Settings and follow its checkout instructions. Renewal is manual; no automatic wallet debit. A tier change applies to the next paid period. After downgrade excess wallets retain history but cannot receive new requests; excess recurring schedules pause.

Troubleshooting

No email code?

Check spelling and spam folders. Use the latest code before it expires. If you requested too many codes, wait before trying again. Contact work@skavio.eu if delivery keeps failing; do not send the code to support.

No wallet connection or unsupported network?

Use a compatible wallet browser or extension with message signing. Choose one of the four receiving networks listed above. If an EVM wallet asks you to add a network, add the correct supported network in the wallet, then reconnect. There is no unsupported-network fallback.

Signature rejected?

Ensure the wallet account and network match, approve the current challenge and retry if it expired. Cancelling a signature does not add a wallet or transfer money.

Paid but still AWAITING?

Check the exact native USDC amount, selected network, receiving address, confirmation and request expiry. Check monitoring status and allow time for confirmation. Provide your transaction ID and request reference to support. Do not pay twice while waiting.

Cannot create a request?

Check trial/subscription expiration, usage allowance and whether your selected wallet can receive new requests under your plan. A verified wallet retained after downgrade may be outside the current allowance.

Lost your place?

Sign in with the same email and choose Getting started / resume setup. Progress is saved to your account, including across devices. Existing wallets and requests are detected.

Frequently asked questions

Does Skavio hold my funds?

No. Customers pay your receiving wallet directly. Skavio verifies and records evidence.

Does connecting a wallet authorize charges?

No. Ownership message signing does not transfer funds. Subscription renewal requires your separate wallet approval.

Can I use API, webhooks or recurring invoices?

Yes. Open Advanced features for API keys, webhooks and developer documentation. Existing recurring schedules and accounting forms remain available. A recurring invoice is not an automatic wallet debit.

Can I use the demo to prove a payment?

No. The demo uses simulated transactions and does not transfer funds.

Need help? work@skavio.eu. Include a request reference and error message, never a private key, recovery phrase or sign-in code.