PayCasePayment Routing & Orchestration
Legal

Cookie policy

Cookies and browser storage used by the PayCase developer website, authenticated documentation, WebHub, and checkout demo.

Effective October 30, 2026

Essential storage first. PayCase developer services use cookies or local browser storage where required for authenticated sessions, security, project context, and the checkout flow. The public developer website does not currently set PayCase advertising cookies.

1. Scope

A cookie is a small value stored by a website in a browser. Local and session storage are browser facilities that can keep interface or workflow state. This policy describes their use on PayCase-controlled developer services. A downstream processor’s hosted frame, SDK, or page may use its own cookies under its own policy.

2. Service usage

Service Purpose Typical lifetime
Developer website Static pages and status checks. No PayCase browser session is required for ordinary use. No PayCase cookie required
WebHub Authenticated session, request protection, security state, selected project, and interface preferences. Session or configured security lifetime
Documentation A dedicated HttpOnly session confirms that WebHub authorized the current documentation visit. The WebHub session itself is not shared with the docs subdomain. Up to one hour
Checkout demo Protected sandbox connection and browser workflow state used to recover the current session and intent. Session or short-lived sandbox lifetime
Provider components Hosted payment fields, redirects, wallets, customer authentication, fraud controls, and return recovery. Determined by the selected provider

Exact names can change as security frameworks and provider SDKs evolve. Browser developer tools show the current values for the service and environment being used.

3. Categories

Strictly necessary

Used for sign-in, session continuity, request protection, access control, load balancing, security, and checkout state. Blocking these values can prevent WebHub, documentation, or the demo from working.

Functional

May remember a selected project, theme, locale, or sandbox workflow choice. Clearing browser data removes values stored only on the device.

Analytics and advertising

The public developer website does not currently set PayCase analytics or advertising cookies. If non-essential browser tracking is introduced, this policy and any required choices must be updated before it is enabled.

4. Downstream provider components

The checkout demo can load scripts, frames, SDKs, or hosted pages from the processor selected by PayCase. That provider may receive ordinary request and sandbox transaction context and may set storage needed for its authentication, wallet, tokenization, or fraud-control flow. PayCase does not control a provider’s independent cookie lifetime or policy.

External font and content-delivery services may receive request information needed to deliver a file. They are not used by PayCase to build an advertising profile on the public developer website.

5. Browser choices

Browser settings allow you to inspect, block, or delete cookies and local storage. Blocking all storage can prevent sign-in, documentation access, request protection, checkout recovery, wallets, and provider authentication from working.

Use demo restart or sign-out controls before clearing sandbox state. Never use browser storage for a secret API key or production provider credential.

6. Changes and contact

This policy may be updated when services, providers, or browser technologies change. Questions can be submitted through the authenticated WebHub support channel. Personal-data handling is described in the Privacy policy.