PayCasePayment Routing & Orchestration
Legal

Privacy policy

How information is handled in the internal PayCase developer, routing, and orchestration environment.

Effective October 30, 2026

Internal developer environment. PayCase is an internal payment routing and orchestration layer for authorized organizations and project users. Use sandbox credentials and test data on the developer services. Do not place production secrets, full payment credentials, or unnecessary personal information in metadata, URLs, logs, support messages, or demo fields.

1. Scope

This notice covers dev.paycase.io, authenticated documentation, WebHub, Core API, the checkout demo, and related operational support. It describes the technical handling of information in this environment; it does not replace an organization’s employment, customer, provider, or data-processing terms.

“PayCase” in these pages names the internal platform and its services. It does not identify a separate merchant, bank, acquirer, issuer, wallet, or consumer-facing payment provider. The organization operating a project remains responsible for its customer relationship and for choosing the processors and purposes configured in that project.

2. Responsibilities and privacy roles

Privacy roles depend on who actually decides why and how information is used, as well as the applicable organization, project, agreements, and law. This notice does not by itself assign “controller,” “processor,” or similar statutory status to the PayCase platform or to any participant.

Authorized organizations must document their own roles, provide any required notices, configure access and retention appropriately, and ensure that their use of PayCase and each downstream processor is authorized.

3. Information handled

  • Authorized-user information: name, business email, organization, role, project membership, authentication state, invitations, and security settings.
  • Project configuration: routing rules, products, allowed origins, API-key identifiers and scopes, processor-account references, App Endpoints, and lifecycle settings.
  • Orchestration records: public and internal customer, session, intent, order, subscription, and delivery identifiers; amount and currency; selected route; status; timestamps; lifecycle actions; and provider references.
  • Technical records: IP address, browser and device context, request ID, response status, authentication outcome, audit events, error details, and service telemetry.
  • Support content: information an authorized user chooses to include in a support request, complaint, or operational investigation.

Sensitive payment entry is performed in provider-hosted fields, frames, SDKs, or redirect pages. PayCase orchestration expects provider tokens, references, states, and the minimum context needed to route and reconcile an operation—not raw credentials copied into ordinary application fields.

4. Operational purposes

Information is handled only as needed to:

  • authenticate users and enforce project permissions;
  • create, route, observe, and reconcile payment operations;
  • operate captures, refunds, voids, rebills, subscriptions, and configured App Endpoint deliveries;
  • protect the platform, investigate failures or misuse, and maintain audit trails;
  • provide support and improve reliability and developer experience; and
  • meet obligations that apply to the operating organization.

The developer website does not use payment-operation data for advertising. Operational metrics may be aggregated where doing so is appropriate for reliability and capacity analysis.

5. Service dependencies and disclosures

Information may be transmitted to the processor or downstream route selected by the project, cloud and security infrastructure used to operate PayCase, authorized users of the relevant organization, and advisers or authorities when the operating organization is lawfully required to disclose it.

Each processor and infrastructure provider operates under its own contract and technical role. PayCase does not change a provider’s terms, geographic availability, retention, or independent legal responsibilities.

6. Security and retention

The platform uses authenticated access, project permissions, environment separation, encryption where configured, managed secrets, audit logging, request correlation, signature verification, and operational monitoring. Authorized users must protect their accounts, API keys, devices, and allowed origins.

Retention is determined by record type, environment, operational need, security requirements, and the operating organization’s policies and agreements. Developer and sandbox data may be reset or removed. Backups and security logs can remain for a limited period after primary data is deleted.

7. Requests, changes, and contact

Requests about project data should be directed first to the organization that operates the relevant project. Authorized users can submit platform privacy or security questions through the authenticated WebHub support channel. Include public project and request identifiers, but never include credentials or secrets.

This notice may change when the platform, organization, or applicable requirements change. The effective date identifies the published version. Contractual or statutory obligations remain governed by the documents and law that actually apply.