PayCasePayment Routing & Orchestration
Legal

Complaints policy

A traceable internal process for concerns about PayCase routing, orchestration, developer services, or support.

Effective October 30, 2026

Use redacted operational evidence. Include public PayCase identifiers and request IDs. Do not send passwords, API keys, provider secrets, full payment credentials, or unredacted authentication payloads.

1. Scope

This policy covers dissatisfaction with the internal PayCase developer website, authenticated documentation, WebHub, Core API, checkout demo, routing behavior, App Endpoint delivery, or related support where an investigation or response is expected.

It is an operational issue-handling process. It does not create a statutory consumer-complaint scheme, financial ombudsman process, processor dispute procedure, or replacement for rights and escalation routes that apply under a separate agreement or law.

2. Submit a complaint

Authorized users should submit complaints through the authenticated WebHub support channel or the internal contact specified by the organization operating the relevant project. Authentication helps verify authority and locate the correct project without requesting sensitive data.

Routine incidents, integration questions, and feature requests may use the normal support path. A concern will still be treated as a complaint when its substance asks for investigation or a remedy, even if the word “complaint” is not used.

3. Information to include

  • your name, organization, role, and project public ID;
  • the environment, date, approximate time, and impact;
  • relevant request, session, intent, order, subscription, delivery, or provider reference identifiers;
  • what happened, what was expected, and steps already taken;
  • the outcome or corrective action requested; and
  • lawfully shareable, redacted logs or screenshots.

4. Review process

The support or platform owner will record the complaint, confirm scope and authority, preserve relevant audit information, investigate the affected services, and coordinate with project owners or downstream providers where needed. The response will summarize the finding, corrective action, remaining limitation, or next escalation path.

The target is to acknowledge a complaint within five business days and provide a substantive response within fifteen business days. These are operational targets, not guaranteed or statutory deadlines. Complex security, provider, or multi-system investigations may take longer; material delay should be communicated through the support record.

5. Payment and transaction concerns

PayCase routes and records payment operations but is not the merchant, bank, issuer, acquirer, wallet, or cardholder dispute authority. A buyer-facing charge, refund, delivery, or chargeback concern should normally be raised with the merchant shown on the transaction and, where appropriate, the relevant payment provider or financial institution.

PayCase can help an authorized project operator trace routing, request, intent, lifecycle, and webhook records. It cannot override a downstream provider’s independent decision or dispute process.

6. Escalation, records, and privacy

If the initial response does not resolve the concern, request an internal review through the same authenticated case and explain what remains disputed. The review should be assigned to an appropriate owner who was not the sole author of the original decision where practicable.

Complaint records are restricted to people and service providers who need them for investigation, security, audit, or legal obligations. Retention follows the operating organization’s policies and applicable agreements. Personal data handling is described in the Privacy policy.