Where the money goes
A Payclave payment moves from the customer's wallet to the merchant's settlement wallet. Payment execution sends the merchant's net settlement to the merchant's wallet and Payclave's 0.7% platform fee to a separate fee wallet in the same payment. Payclave does not keep pooled or intermediary accounts for merchant settlement, and there is no later payout step.
Payclave never holds or controls customer payments or merchant settlement, and it never stores or has access to private keys. Merchants are responsible for their settlement wallet, including its keys and recovery credentials. Payclave cannot access, freeze, or reverse funds after settlement.
Connected-wallet payments
When a customer connects a wallet, the customer reviews and signs the transaction in that wallet. Payclave never receives the customer's keys or signing authority. If the customer pays with a different token or network, the payment route converts it so the merchant receives the configured settlement token on Polygon.
Scan or copy payments
Scan or copy gives the customer one-time deposit instructions for a single checkout. The checkout address is generated for that payment route by Payclave's payment orchestration provider, and the route delivers the settlement token to the merchant's configured settlement wallet. Payclave does not hold the keys to these addresses.
Customers must send the exact token, amount, and network shown before the checkout expires. Payclave cannot reverse an onchain transaction after confirmation and does not guarantee recovery of mistaken transfers. Refunds, store credit, and order decisions belong to the merchant under its own policies.
Independent onchain verification
Payclave marks an invoice paid only after it verifies the settlement onchain. The browser and the payment route are never trusted on their own. Verification checks the transaction hash, recipient wallet, token contract, chain ID, amount received, invoice expiry, confirmation and finality, duplicate transaction use, underpayment, and overpayment.
Signed webhooks
Every webhook carries X-Payclave-Signature, X-Payclave-Timestamp, X-Payclave-Delivery, and X-Payclave-Event headers. The signature is an HMAC SHA-256 over the timestamp, a period, and the exact raw request body, using the endpoint's signing secret. Merchants should verify it in constant time, reject stale timestamps, and deduplicate deliveries before fulfilling an order.
API keys, test mode, and accounts
Secret keys (sk_test_* and sk_live_*) belong only on the merchant's server. Publishable keys (pk_test_* and pk_live_*) can create and read checkout sessions with a limited set of fields. Test mode and live mode use separate keys and separate records, so test activity never mixes with live payments.
Dashboard passwords are hashed with Argon2id, and sessions are stored server-side behind an opaque session token. Live settlement wallet changes can require extra verification or review before they take effect.
Report a security issue
Send security reports to security@payclave.com with the affected page, endpoint, or integration and steps to reproduce. Do not include private keys, wallet recovery phrases, secret API keys, or webhook signing secrets. Payclave publishes a security.txt file with its current contact details.