Security
Is stablecoin payment safe?
Non-custodial. Kollect never takes custody; licensed partners hold funds during fiat legs.
What happens to my money if Kollect disappears?
It is not Kollect’s to lose. Payments are received on-chain and passed to licensed partners for the fiat leg, so there is no Kollect balance holding your funds. On the stablecoin-to-stablecoin rail the payment is addressed to your own wallet from the start.
Will Kollect ever ask for my wallet keys?
No. Not a private key, not a seed phrase, not a signature to discuss pricing or onboarding. Nobody from the team will request one on any channel. A message that does is not from Kollect, and the security route on the contact page exists to report it.
Which networks does a payment touch?
Ethereum mainnet and Polygon for live payments, and a separate test network for the sandbox so nothing of value moves there. The payment link states the network before the payer confirms, rather than leaving it to be discovered at the wallet step.
Security posture
- Custody
- Non-custodial. Kollect never takes custody; licensed partners hold funds during fiat legs.
- Request signing
- API key + secret, HMAC-SHA256 signature, mandatory idempotency key.
- Webhook verification
- Signed via x-kollect-signature; kollect-server interface only.
- Networks
- Ethereum mainnet, Polygon
- Sandbox
- Sepolia (sandbox only)
What non-custodial means in practice
Non-custodial. Kollect never takes custody; licensed partners hold funds during fiat legs. The distinction is structural rather than a policy that could change: the money does not pass through a Kollect balance, so there is no Kollect balance to be frozen, misappropriated or lost.
On the stablecoin-to-stablecoin rail there is no intermediary at all. The payment is addressed to a wallet you control from the moment it is created, so it never sits anywhere on its way to you. On the fiat legs a licensed partner takes custody for the duration of the conversion and payout, because moving fiat into a bank account is regulated activity and Kollect is not the licensed entity for it.
The practical consequence is worth stating plainly: a failure at Kollect cannot strand funds that were never Kollect's to hold.
How requests and webhooks are secured
API access uses API key + secret, HMAC-SHA256 signature, mandatory idempotency key. The signature covers the request, so a captured key alone is not enough to forge one, and the idempotency key means a replayed request resolves to the operation already performed rather than a second one.
Outbound webhooks are signed too: Signed via x-kollect-signature; kollect-server interface only. Verification happens against the raw request body, compared in constant time. A normal string comparison returns as soon as it finds a difference, and the time that takes leaks how much of the signature was right.
Sandbox isolation and social engineering
The sandbox runs on Sepolia (sandbox only), a separate network from the Ethereum mainnet and Polygon used for live payments. Test tokens have no value, so a sandbox mistake cannot become a real loss. The post-payment settlement timeline there is a labelled simulation rather than an unmarked one.
The likeliest attack on a payments product is not technical. Kollect will never ask for a private key, a seed phrase or a wallet signature, on any channel, for any reason. Any message that does is not from Kollect, and the security route on the contact page exists to report it.
Custody and data questions
Every answer here is mirrored verbatim in this page's FAQ structured data, so nothing is hidden behind a click.
Who is regulated and what is checked is on the compliance page. Report a vulnerability through the security route.
Does Kollect hold my funds?
No. Kollect is non-custodial: payments are received on-chain and passed to licensed partners for conversion and payout. Kollect is not the licensed entity holding your money and never takes custody of your funds.
What happens to your data?
Onboarding documents are handled for compliance purposes only. The full data-protection statement is published with the security page.