Refunds and Reconciliation

Kairostamp is presently operated by its individual operator, trading under the Kairostamp name. LentiLabs LLC (New Mexico) formation is pending and that entity does not yet operate the service.

This is an operational draft published in good faith and pending professional legal review. It is not legal advice.

1. Payment happens after fulfilment

The Service verifies your payment authorization, performs the snapshot, and only then settles the payment. If the snapshot fails — an unreachable target, a blocked address, a timeout, an oversized body or a platform fault — the authorization is not settled and you are not charged. Most failure cases therefore need no refund at all.

2. Completed services are generally final

Digital and API services are generally final once performed and delivered. This is not a blanket "no refunds" rule and does not override the exceptions below. A receipt recording a 404, 500 or empty page is a successful fulfilment: the Service records what the target returned, and does not guarantee any particular content.

The exceptions, in which the operator will refund or reconcile, are:

• a duplicate charge for a single intended request;
• failed delivery or non-delivery of the paid result;
• an erroneous charge, including a charge for a call that was never delivered;
• any case where applicable law requires a refund.

Nothing in this document waives rights that cannot be waived under the consumer-protection law that applies to you. Where such law grants a remedy, that law prevails over this document.

3. Settled but unfulfilled

If settlement succeeds but you do not receive a receipt — for example a response with reconciliation_required — the operator will investigate against the internal payment ledger and the append-only evidence chain. Where the ledger shows a settled payment with no linked receipt, the operator will either deliver the receipt or return the settled amount to the payer address, at the operator's discretion and subject to network fees.

4. Duplicate charges

Each settlement transaction hash is processed once. A retried request carrying the same settlement is not charged again. If your own client signs and settles two distinct payments for one intended request, contact the operator with both transaction hashes.

5. How to request reconciliation

Send the settlement transaction hash, the payer address, the approximate time, the target URL, and any error code you received to support@kairostamp.com (see the contact page). Target response time: 5 business days. Keep transaction hashes; without one a payment cannot be located.

6. What the operator cannot do

• Reverse a settled blockchain transaction — settlement is final on chain.
• Recover funds sent to an address other than the advertised receiving address.
• Recover funds sent on a network other than the advertised network.
• Refund test-network tokens as anything other than test-network tokens.

7. Network in force

The network, token and price in force are those advertised in the Service's 402 payment challenge and in /api/public/discovery. Refunds, where due, are made in the same token on the same network as the original payment, to the payer address, less network fees.