PayCasePayment Routing & Orchestration
Legal

Terms of use

Operational rules for authorized use of the PayCase developer website, WebHub, Core API, documentation, and checkout sandbox.

Effective October 30, 2026

Your organization’s rules control. These are general operational conditions for developer services. Any applicable services agreement, order form, internal policy, provider agreement, or other authorized arrangement takes priority if it addresses the same subject differently.

1. Scope and priority

These conditions apply to authorized use of dev.paycase.io, authenticated documentation, WebHub, Core API developer access, and the checkout demo. They do not identify a contracting entity, select a governing law, create a consumer payment service, or replace an agreement or policy that governs your organization’s use of PayCase.

Access is permitted only for an organization, project, or user that has been authorized to use the relevant environment. If you are unsure whether you are authorized, stop and contact the project owner or the support channel available in WebHub.

2. Platform role

PayCase is an internal payment-routing and orchestration layer. It applies project configuration and forwards eligible requests to configured downstream services. PayCase is not the merchant, cardholder, bank, issuer, acquirer, payment method, wallet, or downstream processor involved in a routed transaction.

A route, status, capability matrix, or sandbox result does not guarantee authorization, capture, settlement, refund, dispute outcome, provider availability, or production eligibility.

3. Developer and sandbox environments

Developer services are intended for integration work, evaluation, and controlled testing. Accounts, fixtures, routes, credentials, and stored test data may be changed or reset as environments evolve.

  • Use only sandbox keys, sandbox provider accounts, and published test payment data.
  • Do not submit real card data, bank credentials, production secrets, or production personal data to a sandbox.
  • Do not use sandbox output for settlement, accounting, compliance, tax, legal, or financial decisions.
  • Validate a production integration under the agreements, controls, and provider requirements that apply to it.

4. Accounts, keys, and authorized access

Keep credentials confidential, use the narrowest available permissions, and remove access when it is no longer required. Access only projects, routes, transactions, customer records, and provider accounts that your organization has authorized.

Report suspected credential exposure or unauthorized access through the authenticated WebHub support channel or the contact route established by your organization. Never place secrets or sensitive payment data in URLs, metadata, logs, issue reports, or support messages not designed to receive them.

5. Acceptable use

You must not use a PayCase developer service to:

  • break applicable law, facilitate fraud, test stolen credentials, or process prohibited activity;
  • bypass access controls, project boundaries, ownership checks, request signatures, or rate limits;
  • probe security outside an expressly authorized testing program, distribute malware, scrape protected data, or impair service operation;
  • misrepresent PayCase, a provider, transaction status, or a sandbox result as a production approval or certification; or
  • copy, modify, or reverse engineer protected components except where separately authorized or where applicable law does not permit that restriction.

6. Downstream services

A project can route requests to independent processors, wallets, fraud tools, infrastructure services, or other downstream providers. Those services may require their own accounts, agreements, configuration, geographic eligibility, and operational controls.

The project owner is responsible for selecting and configuring permitted routes and for ensuring that its notices, instructions, and provider use are appropriate. Provider terms govern provider-controlled functionality, availability, data handling, authentication, settlement, and disputes.

7. Availability and service levels

Developer and sandbox services may be unavailable, incomplete, or changed without a production release commitment. Published documentation and capability matrices describe intended current behavior and may change as routes and providers evolve.

No public service level, warranty, liability allocation, data processing commitment, or production support obligation is created by this page. Those matters are governed only by the applicable agreement or internal policy, subject always to obligations that cannot be limited under applicable law.

8. Access changes and contact

Access may be restricted to protect the platform, respond to suspected misuse, maintain services, or follow applicable law and organizational policy. This page may be updated when the developer environment or operating model changes.

Questions should be submitted through the authenticated WebHub support channel or the contact route established in your organization’s controlling agreement or policy. See also the Privacy policy, Cookie policy, and Complaints policy.