Terms of Service

These Terms of Service specify the complete contract between your operating entity and Payzaapi governing platform consumption, system interfaces, and transaction records.

Platform API interfaces are gated. Standard accounts do not include programmatic access keys. API keys are provisioned selectively to authenticated commercial entities following verification protocols.

Payment operations execute via integration with licensed monetary settlement processors, including Korapay, Tuma, and PawaPay. Usage of payment settlement workflows requires compliance with third party partner frameworks.

System account creation requires strict fulfillment of these criteria:

• Maintaining a minimum legal age of 18 years or legal majority within your jurisdiction.
• Holding full legal status to enter into binding commercial contracts.
• Conducting valid business operations selling lawful items or services.
• Submitting true, active registration details and updating system credentials as changes occur.
• Operating outside sanctioned geographical areas subject to monetary restrictions.
• Having no prior account bans or regulatory terminations on Payzaapi infrastructure.

Payzaapi reserves operational rights to run validation checks against entity details at any point.

System access actions tied to your API keys or user credentials remain your primary responsibility. Required protocols include:

• Credential Protection: Safeguard passkeys, authentication tokens, and administrative credentials. Enable multifactor steps where supported.
• Breach Notification: Report unauthorized panel access immediately via [email protected].
• Data Integrity: Ensure item catalog entries, price fields, tax structures, and business information remain accurate.
• Consumer Privacy: Process end buyer personal records according to applicable local data privacy frameworks.
• Single Instance Rules: Avoid setting up parallel system accounts to bypass platform volume caps or security blocks.

Platform resources must exclusively serve legal operations. Forbidden uses include:

• Distributing unlicensed, bootlegged, or contraband products.
• Clearing payments related to unlicensed gambling, adult platforms, weapons, or controlled substances.
• Executing fraudulent transaction sequences, circular transfers, or laundering funds.
• Generating false sales records, artificially manipulating metrics, or misleading consumers.
• Running collection workflows without active fulfillment capabilities or delivery intents.
• Attempting system reverse engineering, database extraction, or platform resource denial attacks.
• Misrepresenting company registration details, shop physical locations, or goods catalogs.
• Deploying web scrapers or unauthorized automated scripts to grab platform assets.

Payzaapi charges platform service maintenance fees based on real time processing throughput. Standard rates run as follows:

System charges deduct dynamically from incoming transactions. Rate structure updates require a 30 day written notification cycle sent to active account email addresses.

Merchants can transfer platform ledger totals outward to authorized commercial destination accounts under these parameters:

• Outward transfers trigger standard manual or systemic approval steps, normally completing within 1 business day.
• Floor limits apply to payout operations per currency bracket.
• Destination account parameters must be verified prior to dispatch. Systems do not accept responsibility for transfers sent to miskeyed destinations.
• Payzaapi keeps system authority to apply administrative locks on transfers during security checks or identity confirmations.
• Outward transfer fees deduct directly from requested totals rather than appending on top.
• If an external transfer fails at the processing partner level, 100% of the locked capital routes back to your ledger automatically.

All core platform assets, web applications, underlying codebases, layout engines, branding elements, and graphics remain the exclusive property of Payzaapi Technologies.

Merchants hold a limited, revoked-on-demand, non-transferable runtime access license to interface with Payzaapi applications for direct shop operations. Restricted actions:

• Replicating, harvesting, or building derivative applications off platform source code.
• Using Payzaapi trade assets or graphic marks without written license files.
• Reselling, sublicensing, or white labeling dashboard access to third parties.

Merchants maintain absolute ownership of uploaded product datasets, sales records, customer lists, and store logos.

Merchant Initiated: You can close account access by notifying [email protected]. Ensure all ledger balances are cleared out prior to closure request. In cases where voluntary closures leave positive balances uncollected, our team attempts contact for 90 days. Unclaimed funds remaining past 90 days auto transfer outward to your last verified payout destination via partner gateways.

Platform Initiated: Service locks or account terminations occur under the following conditions:

• Direct breaches of contractual clauses inside these Terms.
• Detections of high risk, deceptive, or prohibited transaction flows.
• Submission of fraudulent business identity records.
• Court commands or statutory compliance instructions from regulatory bodies.

If an account terminates due to policy violations, balance releases pause during audit periods. Once clearing teams confirm no financial liability or loss risk remains, funds release to your primary payout channel minus standard processing fees.

Payzaapi disclaims financial liability regarding:

• Secondary operational losses, revenue impacts, or business interrupts stemming from outage events.
• Third party clearing delays caused by telecom gateway interruptions, bank ledger locks, or partner gateway outages.
• Unapproved account operations occurring through compromised user credentials.
• Third party banking, mobile money, or clearing gateway service suspensions.

Total system liability caps at the sum of platform fees paid by your account over the 3 months leading up to a logged incident.

These terms operate under statutory frameworks of the Republic of Kenya. Contractual disputes, claims, or system litigation fall under exclusive legal jurisdiction in Nairobi, Kenya.

Informal Dispute Stage: Before taking formal judicial steps, parties agree to file issue logs directly to [email protected]. Operational support teams commit to standard response times within 5 business days to work toward resolution.

In store disputes between merchants and buyers remain strictly between those two parties. Payzaapi does not mediate retail merchandise claims or fulfillment disagreements.

Payzaapi reserves authority to adjust terms clauses to match structural software or compliance updates. Material modifications trigger these steps:

• Modification of the revision tracking date at the top of this document.
• Issuance of email updates sent to primary account contact addresses 30 days prior to implementation.
• Deployment of notification banners inside merchant account dashboards during the review window.

Continued platform operations past the effective date of changes implies agreement to revised terms.

For inquiries regarding platform compliance, system features, or technical questions: