aproxpay.

Refund Policy

Revision 1.2 — effective July 16, 2026

This Refund Policy applies to all payments made to the AproxPay proxy service (the "Service") operated by AproxPay ("we", "us", "our"). This Policy is incorporated into and forms part of the Terms of Service.

1. All Sales Are Final

Payments to the Service are non-refundable except where mandatory law requires otherwise or we grant the discretionary exception in Section 3. All payments are made via the x402 protocol in USDC on a public blockchain. These are push payments authorized before each purchase. The original on-chain settlement entry is irreversible by design — it cannot be cancelled or charged back. Any refund we choose or are required to make is a separate transfer. There are no stored balances or subscriptions.

2. Situations That Do NOT Qualify for a Refund

For the avoidance of doubt, no refund (full or partial) is owed for:

  • unused capacity — session time or byte cap remaining when a session expires or you stop using it;
  • early closure — voluntarily closing a session before its expiry;
  • enforcement for cause — termination or suspension due to a violation of the Terms of Service or Acceptable Use Policy, byte-cap exhaustion, TTL expiry, sanctions screening, or abuse-prevention systems;
  • exit-IP changes — rotation or migration of the exit IP during a session for upstream or operational reasons (your remaining time and byte cap are preserved);
  • blocked destinations — inability to reach a destination that is blocked by our security blocklists, sanctions restrictions, or the acceptable-use policies of our upstream providers;
  • destination behavior — target sites that block proxy traffic, present CAPTCHAs, rate-limit you, or return unexpected content;
  • service interruptions — downtime, degraded performance, or upstream provider outages. The Service carries no SLA or uptime guarantee (Terms of Service, Section 4);
  • buyer error — payments sent for the wrong tier, from the wrong wallet, or for requests you no longer need.

Failed requests where no payment settled cost you nothing: if payment verification or settlement does not complete, the purchase simply does not happen.

3. Discretionary Exception for Verified Service Faults

We may, at our sole discretion and without any obligation, issue a goodwill refund where a settled payment was demonstrably not served due to a fault in our own infrastructure (for example, a payment settled but our systems returned an internal error and delivered nothing).

If granted, such a refund is processed as a manual USDC transfer to the paying wallet, recorded in our books. There is no automated refund mechanism, and a granted refund in one case creates no entitlement in any other case.

4. How to Raise an Issue

Email legal@aproxpay.com with:

  • the on-chain transaction hash of the payment;
  • the approximate timestamp (UTC) and the endpoint or session concerned;
  • a description of what happened.

We aim to respond within a reasonable time. A transaction hash is normally required to locate a payment; without one, investigation may be delayed or may not be possible.

5. Consumer Law

The Service may be used by businesses, professionals, and consumers. Nothing in this Policy excludes liability, cancellation rights, conformity remedies, refunds, or other rights that cannot lawfully be excluded under applicable consumer law.

6. Changes to This Policy

We may update this policy from time to time. Each revision is identified by the Revision number and Effective date at the top of this document; material changes are noted in the changelog below. The policy in effect at the time of your payment applies to that payment.

7. Contact

Document changelog

RevisionDateChanges
1.22026-07-16Simplified the draft operator identity to AproxPay and clarified consumer access.
1.12026-07-16Updated the UK legal context; clarified that blockchain entries are irreversible but refunds are separate transfers; softened investigation and mandatory-law wording.
1.02026-07-16Initial version.