Skip to content
AttestLayer

AttestLayer Policy

Refund Routing

attestlayer.com is the company and trust root and does not operate checkout. This page routes billing questions to the policy or agreement that governs the applicable transaction.

attestlayer.com is the corporate and trust site. Direct-client, partner, Console, Verify, Registry, and API tasks use their dedicated domains.
Updated 25 September 2026 Canonical root-domain policy

What the root domain covers

attestlayer.com publishes company, trust, and policy information and does not complete a paid transaction. Direct-client purchases use buy.attestlayer.com; partner, enterprise, and invoiced engagements use their executed commercial documents.

A refund or billing question is evaluated under the storefront policy, order form, invoice, or signed agreement that governed the transaction. This root page does not replace those terms.

Which terms control a paid transaction

Surface or relationship What controls the refund question
attestlayer.com root site No direct self-serve sale occurs here. The root site only routes the request to the governing surface or agreement.
Direct Buyer Review Pack purchase The checkout terms, Client Refunds and Billing Policy, order confirmation, and any applicable written terms.
Partner, enterprise, or invoiced engagement The signed order form, invoice terms, negotiated commercial document, or other written agreement attached to that engagement.

How to route a refund or billing question

Include enough information for AttestLayer to identify the transaction quickly.

  • The client email address used for the purchase or account.
  • The order ID, invoice reference, or payment date if available.
  • The surface or agreement you believe governed the transaction.
  • A short explanation of the issue you want reviewed.

Refund and billing questions can be sent to billing@attestlayer.com. General routing questions can go to contact@attestlayer.com.

Record-only boundary

Standard AttestLayer workflows are designed around records the customer is authorized to provide without endpoint installation or production credentials. Package verification can establish integrity and issuer-receipt authenticity; it does not establish the truth or completeness of supplied records, control effectiveness, compliance, certification, legal sufficiency, or customer approval.