paybondpaybond
Sign in

Legal

Paybond Terms of Service

Effective May 26, 2026
These terms govern access to Paybond self-serve signup, hosted operator tooling, APIs, SDKs, and related settlement workflow services.
Effective: May 26, 2026Last updated: June 2, 2026

1. Agreement and order precedence

These Terms of Service apply when you access or use Paybond public signup, the hosted console, APIs, SDKs, documentation, support, and related services. "Paybond" means the Paybond entity identified in your order form, invoice, or other contracting record.

If you have a signed order form, data processing addendum, statement of work, enterprise agreement, or similar written agreement with Paybond, that agreement controls where it conflicts with these terms. For self-serve use without a signed order form, these terms and the plan limits shown in the product or checkout flow apply.

2. Service scope

Paybond provides hosted software for tenant-scoped settlement workflows, operator tooling, evidence-based release or refund decisions, ledger provenance, Signal records, compliance exports, policy workflows, API access, and related integrations.

  • Harbor records intents, evidence, disputes, settlement state, and ledger provenance.
  • The hosted console and APIs provide authenticated access, admin workflows, protocol verification, SSO, SCIM, API delivery, and billing surfaces.
  • Signal indexes verified settlement history into signed standing artifacts and review surfaces.
  • Kit and protocol surfaces help customer runtimes create sessions, verify capabilities, submit signed evidence, and retrieve supported records.

Service availability, support windows, entitlements, usage limits, feature flags, and beta access depend on your plan and any separate order form.

3. Account authority and admins

The person completing signup represents that they are authorized to act for the customer organization. The initial signup user may become the initial tenant admin. Your organization is responsible for assigning roles, removing users who no longer need access, configuring SSO or SCIM correctly, and keeping account, billing, and security details accurate.

You are responsible for all activity under your accounts, API keys, trusted agent keys, service accounts, operators, and tenant-directed integrations, except to the extent caused by Paybond's breach of these terms.

4. Customer data and tenant scope

As between Paybond and the customer, the customer retains ownership of customer content submitted to the service, including tenant configuration, evidence, dispute records, policy data, SSO or SCIM configuration, settlement configuration, trusted agent key metadata, signed workflow artifacts, and related product records.

You grant Paybond the rights needed to host, process, transmit, secure, analyze, support, and display customer data to provide and improve the service, enforce tenant isolation, investigate incidents, comply with law, and honor the customer agreement.

Cross-tenant access

Attempting to access another tenant's data, workflows, operators, settlement configuration, audit exports, or credentials is prohibited and may be treated as a security incident.

5. Acceptable use

  • Do not use Paybond to violate law, sanctions, export controls, payment network rules, or third-party rights.
  • Do not attempt cross-tenant access, credential theft, unauthorized scraping, abuse of support access, security probing without authorization, or denial-of-service activity.
  • Do not submit malware, secrets you are not authorized to use, illegal content, or data that your organization lacks authority to process through Paybond.
  • Do not reverse engineer private customer data, bypass rate limits, interfere with ledger or audit integrity, or misrepresent settlement or dispute outcomes.
  • Do not use Paybond as a regulated financial service, escrow agent, custodian, money transmitter, broker, bank, fiduciary, or payment processor unless a separate written agreement expressly says otherwise.

6. Billing, taxes, renewal, and cancellation

Paid self-serve plans are billed through Stripe. Free, Starter, Team, and Business plans may use public signup where available; Enterprise and custom plans are sales-led unless Paybond states otherwise.

  • Fees, usage limits, overages, billing periods, renewal terms, cancellation rights, and taxes are controlled by the checkout flow, billing portal, order form, invoice, or signed agreement that applies to your plan.
  • Self-serve subscription changes and payment-method updates may be handled through the Stripe customer portal or workspace billing controls.
  • Unless your order form says otherwise, fees are non-refundable except where required by law or where Paybond expressly approves a refund.
  • Paybond may suspend or limit paid features for overdue amounts, payment failure, fraud risk, abuse, or material breach after reasonable notice where practical.

7. APIs, SDKs, rate limits, and beta features

You may use Paybond APIs, SDKs, docs, examples, and developer tools only as permitted by these terms, the applicable plan, and the relevant documentation. Paybond may apply rate limits, abuse controls, feature flags, and compatibility requirements to protect the service.

Beta, preview, example, experimental, or evaluation features may be changed, limited, or discontinued and may not be appropriate for production workflows unless Paybond expressly designates them as production-ready.

8. Configuration and hosted operations

You are responsible for business information, settlement destinations, identity-provider settings, SCIM provisioning, trusted agent keys, API-client behavior, policy configuration, evidence submissions, and other tenant-specific credentials or inputs you configure in your workspace.

Paybond is responsible for platform-owned secrets and hosted runtime operations for managed services, including webhook secrets, signing keys, shared provider credentials, and operation of Paybond-managed services.

Payment and settlement role

Paybond is software that defines and records workflow rules around supported payment and settlement rails. Unless a written agreement says otherwise, payment processors, card networks, banks, wallet providers, stablecoin networks, or other rail providers move funds under their own terms and compliance obligations.

ACH Direct Debit live use

If Stripe ACH Direct Debit is enabled for live workflows, you are responsible for using it only with authorized bank-account holders, accurate transaction details, and workflows that satisfy applicable payment-network, bank, and legal requirements. Paybond may require tenant-by-tenant approval, Stripe capability readiness, mandate and authorization review, operating limits, or additional controls before live ACH access is enabled.

ACH debits can remain pending for several business days and may be returned, disputed, blocked, or reversed under provider, bank, or network rules. Refunds and disputes can overlap, including cases where a customer receives duplicate credits. You are responsible for monitoring ACH exceptions, preserving supporting records such as receipts and evidence, and resolving customer or counterparty issues outside Paybond where required.

9. Security, support, and incident response

Paybond maintains safeguards designed for tenant-scoped hosted operations. Customers must maintain their own endpoint security, identity-provider controls, credential hygiene, authorization reviews, webhook handling, and API-client behavior.

Paybond may access customer environments or records when needed to provide support, investigate incidents, comply with law, enforce agreements, or protect service integrity. Elevated support access is expected to be time-bounded and auditable.

10. Privacy, DPA, and subprocessors

Paybond handles personal data as described in the Privacy Policy, the Cookies & Analytics Notice, and the Subprocessors page.

If your organization needs a data processing addendum, security exhibit, subprocessor notice, or custom privacy terms for a paid or enterprise plan, contact [email protected].

11. Intellectual property and feedback

Paybond and its licensors retain all rights in the service, documentation, software, designs, trademarks, APIs, SDKs, examples, templates, product logic, and related technology. Except for rights expressly granted to you, Paybond reserves all rights.

If you provide feedback, suggestions, or requests, Paybond may use them without restriction or compensation, provided Paybond does not disclose your confidential information contrary to these terms or a signed agreement.

12. Confidentiality

Each party may receive non-public information from the other party. The receiving party must use reasonable care to protect confidential information and use it only for the relationship contemplated by these terms, except where disclosure is authorized, already public, lawfully obtained from another source, independently developed, or required by law.

13. Suspension and termination

You may stop using Paybond at any time, subject to plan cancellation rules and payment obligations. Paybond may suspend or terminate access for material breach, non-payment, security risk, legal risk, abuse, sanctions concerns, or service integrity issues.

After termination, Paybond may delete or retain data according to the Privacy Policy, the applicable order form, legal obligations, backup practices, audit integrity needs, and dispute or incident requirements.

14. Disclaimers

Except as expressly stated in a signed agreement, Paybond is provided "as is" and "as available." Paybond disclaims all implied warranties to the maximum extent permitted by law, including warranties of merchantability, fitness for a particular purpose, non-infringement, uninterrupted operation, and error-free operation.

Paybond does not provide legal, tax, accounting, investment, banking, money-transmission, sanctions, or payment-network advice. You are responsible for determining whether your workflows, counterparties, payment rails, data processing, and settlement decisions comply with applicable obligations.

15. Limitation of liability

To the maximum extent permitted by law and unless a signed agreement states a different limit, neither party will be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, loss of goodwill, or business interruption.

Unless a signed agreement states a different cap, each party's aggregate liability under these terms is limited to the amounts paid or payable to Paybond for the service giving rise to the claim during the twelve months before the event giving rise to liability.

16. Indemnity

You will defend and indemnify Paybond from third-party claims arising from your customer data, tenant configuration, settlement destinations, API clients, operators, breach of these terms, or use of Paybond in violation of law or third-party rights. Paybond will defend and indemnify you from third-party claims that the unmodified Paybond service infringes intellectual property rights, subject to exclusions and procedures in any signed agreement.

17. Governing law and disputes

The governing law, venue, notice address, and dispute process are controlled by your order form, invoice, or signed agreement. If those records do not identify governing law or venue, contact [email protected] before paid production use so the contracting record can be completed.

18. Changes and contact

Paybond may update these terms as the service, plans, legal requirements, or risk controls change. Material changes will be reflected by updating the effective or last-updated date and, where appropriate, by providing additional notice through the service, contract record, or email.

Questions about these terms should go to [email protected].