Provider event
Receive the callback, authenticate it and match it to the original merchant order and payment amount.
Crypto settlement.
Your wallet. Your visibility.
Built around non-custodial V3 settlement architecture, transparent fee accounting and independent on-chain payment evidence. Configure a merchant-owned receiving wallet and connect approved payment rails.
Only audited provider and asset combinations can be offered for live payment processing.Four settlement assets.
Two EVM networks.
USDCPolygonNative Polygon USDC
POLPolygonPolygon native asset
USDCEthereumEthereum ERC-20 USDC
ETHEthereumEthereum native asset
These are settlement-engine capabilities, not a promise that every card or fiat provider pays out in all four assets. Production approval requires funded proof for each enabled route.
WHY CHAIN PROOFS MATTERDon't confuse 'paid' with
01 02 03 04
Don't confuse 'paid' with
funds delivered.
Independent funding evidence
Check the expected network, asset, recipient and transaction outcome independently of the provider response.
Settlement verification
Verify the contract state and settlement transfers before recording merchant or platform proceeds.
Merchant withdrawal
Confirm the merchant payout transaction and reconcile verified platform fees without treating the full customer payment as KoviraPay revenue.
How crypto checkout fits your business
Start with a public EVM wallet address that you control. You do not provide a seed phrase or private key. A payment session is assigned its provider routing and its intended network and asset. KoviraPay's settlement worker then relies on on-chain evidence and its ledger to determine actual completion.
When a customer pays with a card or bank method at an external provider, additional processing, identity verification and exchange fees can apply. Those operations sit outside a 1% software platform fee. No blockchain design alone can remove provider chargeback or compliance obligations, so we describe finality and custody according to the exact route rather than the payment method's marketing name.
For production operations, run the CLI worker, configure each network RPC and webhook, verify that required transaction tracing is supported, and use dedicated signing credentials with secured nonce management. Do not enable live charges based on setup checkboxes alone. Our release gate expects real funded payment evidence and correctly reconciled merchant payouts.
GOOD TO KNOW
Clear answers, before you connect.
Where do my funds go?
Verified V3 self-settlement routes are designed to settle on-chain to the merchant-controlled EVM wallet. Provider handling and availability differ, and live routing is activated only after a successful real-payment audit.
Which assets are supported in the V3 design?
The integrated settlement engine includes Polygon native USDC, Polygon POL, Ethereum USDC and native Ethereum ETH. Real payout support for any provider/asset combination requires successful independent end-to-end verification.
Do I share my wallet private key?
No. Merchants provide a public receiving EVM address. The platform relayer configuration is separate and is not an excuse to request merchant seed phrases.
Are chain confirmations immediate?
No fixed timing can be guaranteed. Confirmation depends on the network, gas, provider processing and independent verification of funding and settlement transactions.
YOUR NEXT MOVE
Create merchant account ↗Use a merchant-controlled receiving wallet.
Configure your EVM address, explore approved crypto methods and verify your integration in test mode.