Terms of Service

Terms status

PayKonek Digital Payments Inc. is preparing its final Terms of Service. The final agreement will govern access to and use of applicable PayKonek services, including the website, dashboards, APIs, integrations, payment workflows, wallet-related services, reporting, support, and other approved capabilities.

Before publication, this template must be updated to reflect the actual service scope, funds-flow model, payment partner agreements, account types, applicable licenses, commercial terms, support model, privacy practices, and legal requirements.

1. Agreement and eligibility

The final Terms should explain when an organization or individual enters into an agreement with PayKonek, which related documents are incorporated by reference, and the eligibility requirements that apply to the relevant service.

Required before publication: Confirm the agreement acceptance mechanism, eligible customer types, authority requirements, user age requirements, jurisdictional limitations, incorporated documents, and applicable customer representations.

2. PayKonek services

PayKonek may provide software, dashboards, APIs, integrations, merchant tools, reporting, wallet-related workflows, payment orchestration, settlement-support tools, and related payment operations services.

The exact services available to a customer depend on the approved account, product configuration, jurisdiction, payment partners, operational requirements, commercial agreement, and applicable law.

Required before publication: Insert the final service description, licensing statement, regulated-activity limitations, funds-flow explanation, payment-partner responsibilities, and service exclusions.

3. Accounts, access, and security

The final Terms should require customers to provide accurate information, keep account details current, use authorized users, protect credentials, and comply with account-access and security requirements.

• Use unique accounts for authorized team members and apply appropriate access roles.
• Keep passwords, one-time passwords, private keys, secret API keys, tokens, and other credentials confidential.
• Notify PayKonek promptly about suspected unauthorized access, compromised credentials, or security incidents.
• Maintain accurate organization, representative, settlement, contact, and configuration information.

Required before publication: Confirm account responsibility, access controls, credential rules, API-key requirements, customer security obligations, and the allocation of responsibility for unauthorized activity.

4. Payments, wallets, payouts, and partners

The final Terms should explain how payment, wallet, payout, settlement, reversal, dispute, refund, failed-transaction, and partner workflows apply to each approved product configuration.

Payment availability, transaction timing, limits, payment states, settlement timing, reversals, disputes, and other outcomes may depend on customer configuration, payment partners, verification, risk controls, funding, and applicable rules.

Required before publication: Insert final funds-flow terms, authorization requirements, payment-instruction rules, available-balance rules, payout conditions, chargeback or dispute terms, refund handling, reversal handling, partner responsibilities, and customer obligations.

5. Fees, taxes, and billing

The final Terms should describe the applicable implementation, platform, transaction, partner, rail, usage, support, and other charges identified in the relevant order form, pricing schedule, dashboard, account agreement, or commercial agreement.

Required before publication: Define billing dates, invoicing, payment methods, taxes, renewals, refunds, fee changes, overdue amounts, minimum commitments, volume commitments, and any partner-related commercial terms.

6. Acceptable use and prohibited activity

The final Terms should prohibit unlawful, fraudulent, abusive, deceptive, sanctioned, restricted, or otherwise prohibited use of PayKonek services, as well as activity that creates unacceptable risk for PayKonek, customers, users, payment partners, or the broader ecosystem.

Required before publication: Add the approved restricted-business list, prohibited-activity list, sanctions requirements, transaction-monitoring terms, partner requirements, and consequences for violations.

7. Data and privacy

The final Terms should incorporate the final Privacy Policy and explain the rights, permissions, and responsibilities required for customers to provide information to PayKonek or instruct PayKonek to process information on their behalf.

Where PayKonek processes personal information for a customer, the final agreement may need applicable data-processing terms, security obligations, subprocessor terms, international-transfer provisions, and responsibilities for data-subject requests.

Required before publication: Confirm the final Privacy Policy, data-processing addendum, data-controller and processor roles, subprocessor disclosures, and cross-border transfer mechanisms.

8. Intellectual property

The final Terms should identify ownership of PayKonek services, software, APIs, documentation, branding, materials, and customer data, as well as the limited rights granted to customers for approved use of the services.

Required before publication: Define software license scope, API use rights, restrictions, feedback rights, branding rules, customer-data rights, and any open-source or third-party intellectual-property provisions.

9. Availability, maintenance, and changes

PayKonek may need to maintain, modify, suspend, deprecate, or discontinue services, features, integrations, payment channels, or partner-related capabilities as operational, commercial, legal, or security requirements change.

Required before publication: Define maintenance practices, service levels, planned downtime, material-change notices, beta-feature terms, API-versioning rules, deprecation processes, and customer communication requirements.

10. Disclaimers, liability, and indemnities

The final Terms must include legally reviewed warranty disclaimers, liability caps, exclusions, indemnities, limitations, exceptions, and any applicable regulatory or consumer-law provisions required for the actual PayKonek service.

Required before publication: Obtain legal review of all warranty, liability, indemnity, force-majeure, insurance, and limitation-of-remedy provisions.

11. Suspension and termination

The final Terms should describe when a customer may stop using the services and when PayKonek may suspend, restrict, or terminate access because of non-payment, security risk, prohibited activity, partner requirements, legal obligations, risk concerns, or material breach.

Required before publication: Define notice periods, cure periods, data export, retention, outstanding transactions, settlement handling, access after termination, and continuing obligations.

12. Governing law and disputes

The final Terms should identify the governing law, venue, dispute-resolution process, notice requirements, escalation procedures, and any arbitration or court processes approved by counsel.

Required before publication: Confirm the applicable jurisdiction, venue, mandatory consumer or electronic-commerce rules, arbitration provisions, and any partner-required dispute-resolution terms.

13. Changes to these Terms

The final Terms may be updated as services, payment workflows, partner relationships, commercial arrangements, or legal requirements change. The published version should state the effective date and explain how material changes will be communicated where required.