Terms of Service

Verify Checkout is a non-custodial merchant checkout and payment-verification platform. Merchants create deposit requests, Verify Checkout shows payers how to transfer funds directly to a merchant-owned receiving account, and Verify Checkout verifies and reports the resulting deposit status. We do not collect, hold, pool, reverse, refund, withdraw, or settle customer funds.

Verify Checkout is not a bank, payment gateway, money-transfer service, wallet provider, or financial institution. A successful verification result is evidence about a transfer that already happened outside our systems. It is not a funds movement, settlement, or guarantee that a bank or wallet will not later reverse the transfer.

Provider relationships

Verify Checkout is independently operated by Suba Software Solutions. Unless we state otherwise in a separate written agreement or official announcement, Verify Checkout is not affiliated with, endorsed by, sponsored by, approved by, or officially connected to Telebirr, ethio telecom, Commercial Bank of Ethiopia (CBE), Dashen Bank, Bank of Abyssinia, Safaricom M-Pesa, M-Pesa, CBE Birr, Awash Bank, Siinqee Bank, Kaafi Ebirr, Verify.ET, or any other bank, wallet, payment provider, telecom operator, or financial institution.

Names, logos, product names, service names, and marks belonging to banks, wallets, telecom operators, and payment providers are used only to identify supported checkout and verification workflows and remain the property of their respective owners.

You may use Verify Checkout only if you are legally able to enter into a binding agreement and comply with these Terms. If you use Verify Checkout on behalf of a company, shop, organization, or other entity, you represent that you are authorized to bind that entity to these Terms.

Merchant accounts are intended for businesses and authorized operators. Hosted checkout is intended for payers completing a merchant's deposit request. You may not use the service if you are prohibited from doing so under Ethiopian law or other applicable law.

To use merchant features, you may need to sign in with Telegram, create a workspace, complete a business profile, request live-mode access, generate API credentials, or configure receiving accounts. You agree to provide accurate, current, and complete information and to keep it updated.

You are responsible for all activity under your account, dashboard, Telegram login, API keys, staff access, webhook endpoints, and integrations. You must keep login credentials, sessions, devices, webhook secrets, and API keys confidential. If you suspect unauthorized access, exposed credentials, or misuse, you must notify us promptly.

Sandbox and live environments are isolated. Credentials, receiving accounts, deposits, and operational data from one environment must not be treated as interchangeable with the other.

Verify Checkout may allow merchants to create API keys for production, development, or testing. API keys may have permissions, rate limits, shared workspace credit usage, expiration dates, and activity logs. API keys are machine credentials for your backend. They are not a substitute for human dashboard login.

• Do not share, expose, publish, or hard-code API keys in public repositories, client-side applications, screenshots, support tickets, documentation, logs, or other insecure locations.
• Rotate or revoke compromised keys promptly and review suspicious key activity.
• Use server-side integrations where credentials can be protected and apply your own access controls around internal tools.
• Design your systems to handle rate limits, duplicate requests, retries, delayed responses, provider downtime, webhook retries, and reconciliation.
• Credit your own customers only from trusted Verify Checkout deposit status, not from browser redirects, payer screenshots, or unverified callbacks.

We may suspend, throttle, revoke, or disable API keys if we believe they are misused, compromised, used in violation of these Terms, or creating security, reliability, legal, fraud, or operational risk.

Merchants may create deposit requests through the API or dashboard. Hosted checkout displays transfer instructions for a merchant-owned receiving account and collects the payment reference, SMS text, or receipt details the payer submits so we can verify the transfer.

You are responsible for ensuring that every checkout you create, and every verification request submitted for it, is lawful, accurate, authorized, and connected to a legitimate business, support, accounting, fraud-prevention, or customer-service purpose.

Verification results may include information such as verification status, provider or bank, amount, currency, sender or receiver details, reference number, timestamp, processing status, request ID, provider messages, and related metadata, depending on the provider and available data.

Verify Checkout does not guarantee that every verification result will be available, complete, immediate, accurate, uninterrupted, accepted by a bank, accepted by a customer, or error-free. Verification may fail, return not found, be delayed, depend on upstream providers, require merchant or platform review, or be affected by provider downtime, network issues, incorrect inputs, rate limits, fraud controls, queue saturation, maintenance, or other conditions.

Some bank-to-bank, wallet-to-bank, or similar inter-provider transfers may be shown by a bank app, receipt page, SMS, customer screenshot, or provider message as successful before final settlement, reconciliation, or reversal checks are complete. Banks, wallets, payment networks, or settlement systems may later reverse, reject, adjust, or fail a transaction for reasons outside our control.

A successful Verify Checkout response does not mean that funds are finally settled, non-reversible, immune from later bank action, or guaranteed to remain valid after a provider updates its records. You should not rely solely on Verify Checkout for fraud prevention, accounting, customer dispute resolution, legal compliance, credit decisions, or financial decisions without your own checks, controls, and review process.

Payers may have a limited number of reference-submission retries for customer-correctable outcomes. A review-required decision is terminal on the public checkout token. Merchant or platform operators may still review, approve, fail, or retry a deposit through authorized dashboard tools.

Receiving accounts are bank accounts, mobile-wallet numbers, merchant codes, or similar endpoints that you own or are authorized to use. Verify Checkout assigns an eligible receiving account to a checkout so the payer can transfer funds directly to you. We do not take ownership of those accounts or of the funds sent to them.

You represent that every receiving account you add is lawful, belongs to you or is used with the account holder's authorization, and may be shown to payers as a destination for payment. You are responsible for account accuracy, availability, capacity, naming, and any dispute that arises from money sent to those accounts.

You may also provide a business name, phone number, website, support URL, logo, return URLs, and related workspace details used on checkout, dashboards, and live-mode review. You are responsible for those materials and for keeping them current.

If you are a payer using hosted checkout, you use the page to follow the merchant's payment instructions and, where requested, to submit a transaction reference, SMS, or receipt so the merchant can confirm your transfer.

You should only submit references, receipts, or messages for a payment you made or are authorized to report. Do not submit another person's payment evidence without permission. Hosted checkout does not create an account with Verify Checkout for you, and it does not move money on your behalf.

The merchant, not Verify Checkout, is responsible for the goods, services, balances, refunds, or account credit you expect after a verified deposit. Questions about an order, account balance, or missing credit should go to the merchant that sent you the checkout.

Verify Checkout may allow you to configure webhook URLs, return URLs, or other integrations. You are responsible for ensuring that webhook endpoints are secure, available, properly authenticated, and capable of receiving deposit events. Return URLs must belong to domains you control and have authorized.

We may retry webhook delivery, sign webhook payloads, provide test webhook tools, or expose delivery logs, but we do not guarantee delivery of every webhook event. You should design your systems to handle retries, duplicate events, delayed events, failed events, idempotency, and manual reconciliation.

Webhook delivery reports a deposit outcome. It does not credit a customer inside Verify Checkout. You remain responsible for crediting your own users only after trusted, idempotent handling of Verify Checkout deposit status.

Verify Checkout may offer free, paid, developer, or custom plans. Plans may include limits such as included verification credits, users, features, support level, analytics, exports, notifications, or other usage allowances. Current public plan examples may be described on the pricing page, and custom terms may be handled separately.

One verification credit buys one merchant-requested payment verification attempt. Creating, opening, expiring, cancelling, or abandoning a checkout does not consume a credit. A credit is consumed when a payer's reference is accepted for verification. Credits are not automatically refunded because a verification is unsuccessful, not found, reviewed, cancelled, or later reversed by a provider.

You agree to pay all applicable fees, taxes, and charges for the plan or services you select. We may change pricing, features, limits, quotas, support levels, or billing terms by providing notice, updating the applicable pricing page, or entering a separate agreement. Continued use after changes take effect means you accept the updated terms.

You agree not to:

• Use Verify Checkout for unlawful, fraudulent, deceptive, abusive, discriminatory, harassing, or unauthorized purposes.
• Create checkouts, add receiving accounts, or submit verification requests for transfers you are not authorized to collect or verify.
• Access, collect, infer, or attempt to obtain personal, financial, or transaction information without proper permission.
• Reverse engineer, scrape, overload, probe, scan, attack, disrupt, or bypass Verify Checkout systems.
• Bypass rate limits, quotas, checkout retry budgets, security controls, authentication requirements, billing limits, or usage restrictions.
• Resell, sublicense, white-label, or provide Verify Checkout as a competing service without written permission.
• Upload malicious code, compromise platform security, interfere with availability, or misuse integrations.
• Misrepresent verification results to customers, banks, regulators, partners, or third parties.
• Use hosted checkout, receiving-account details, or verification results to impersonate a bank, wallet, or payment provider.
• Use Verify Checkout in a way that violates applicable banking, privacy, consumer protection, data protection, anti-fraud, payment, sanctions, or other laws.

Customer Data means information that you or your users submit to Verify Checkout, including account details, Telegram profile details, business profile information, receiving-account details, logos, return URLs, checkout metadata, merchant customer identifiers, payment references, receipt or SMS contents, webhook URLs, support messages, and usage data.

You retain responsibility for Customer Data. You represent that you have all rights, permissions, notices, consents, and legal bases needed to submit Customer Data to Verify Checkout and to allow us to process it to provide, secure, support, maintain, and improve the service.

We do not sell Customer Data, rent Customer Data, trade Customer Data, or use Customer Data to build advertising profiles. We use data to operate Verify Checkout, verify deposits, prevent duplicate use of the same transfer, improve reliability, reduce errors, strengthen security, support users, enforce these Terms, and comply with lawful obligations.

You are responsible for your own customer notices, receipts, consent flows, accounting records, dispute processes, privacy compliance, staff controls, and internal governance. That includes telling your payers how you use hosted checkout and any customer identifiers you send us.

Our Privacy Policy explains how we collect, use, share, retain, and protect personal information and Customer Data. By using Verify Checkout, you acknowledge that we process information as described in the Privacy Policy and these Terms.

We do not voluntarily provide Customer Data to any government office, public authority, unrelated third party, or private organization for general monitoring, profiling, resale, political use, or unrelated access. We may disclose information only where required by valid legal process, such as a court order, warrant, subpoena, or comparable legally binding request; where legally necessary to protect rights, safety, security, or investigate abuse; or where you direct us to disclose it.

Where legally allowed and appropriate, we review legal requests before disclosure and seek to limit disclosure to the information required.

Verify Checkout is security-oriented because checkout and verification workflows can involve sensitive operational, customer, and payment-related information. We use administrative, technical, and organizational safeguards designed to protect information from unauthorized access, misuse, alteration, loss, and disclosure.

• Authentication, session controls, Telegram sign-in, role-based access, permission-scoped API keys, and credential revocation workflows.
• Encrypted transport where applicable, security logging, request identifiers, rate limits, abuse detection, and operational alerts.
• Masked payment references on merchant APIs where full references are not required, and controls intended to prevent cross-merchant leakage of duplicate-transaction details.
• Internal least-privilege practices, access reviews, dependency checks, configuration reviews, incident reviews, and recurring security checks.
• Monitoring for uptime, provider health, queue health, error rates, suspicious patterns, and unauthorized access attempts.

No internet service, API, dashboard, hosted checkout, integration, or storage system can be guaranteed to be completely secure. You are responsible for protecting your devices, accounts, API keys, webhook endpoints, staff access, receiving-account details, and customer-facing systems.

We may update, improve, suspend, discontinue, limit, or modify any part of Verify Checkout at any time. Some features may depend on banks, wallets, upstream verification providers, hosting providers, analytics providers, support providers, internet connectivity, or other third-party systems.

Some verification workflows depend on publicly reachable provider endpoints, receipt pages, lookup paths, or related upstream systems that we do not own or control. If a bank, wallet, telecom operator, payment provider, or upstream service changes, restricts, rate-limits, disables, blocks, removes, or shuts down those endpoints, the affected workflow may stop working temporarily or permanently.

We may provide uptime or status information, but we do not guarantee uninterrupted service. We are not responsible for downtime, delays, incomplete results, failed requests, unavailable providers, or failures caused by third-party providers, maintenance, network problems, force majeure events, misuse, legal requirements, or circumstances outside our reasonable control.

Support may be provided through the website, dashboard, email, contact form, Telegram, or other official channels. Support availability, response time, escalation, and priority may depend on your plan or separate agreement.

For security-sensitive issues, account access concerns, suspected API key compromise, or data questions, use official support channels so we can verify authority and handle the issue with appropriate context.

Verify Checkout, including its software, APIs, documentation, designs, logos, trademarks, workflows, dashboards, hosted checkout, content, and service infrastructure, is owned by Suba Software Solutions or its licensors.

Subject to these Terms, we grant you a limited, revocable, non-exclusive, non-transferable right to use Verify Checkout for your internal business or development purposes. You may not copy, modify, distribute, sell, lease, reverse engineer, or create derivative works from Verify Checkout except as expressly allowed by us in writing.

You retain rights in your own trademarks, logos, receiving-account labels, and other materials you upload. You grant Verify Checkout a limited license to host and display those materials as needed to operate checkout, dashboards, and related services.

Verify Checkout may interact with or rely on banks, wallets, payment providers, verification providers such as Verify.ET, hosting providers, analytics providers, email or messaging providers, support tools, monitoring tools, Telegram authentication, and other third-party services. Your use of third-party services may be governed by their own terms and policies.

We are not responsible for third-party services, provider data, provider availability, provider endpoint changes, provider errors, settlement reversals, bank or wallet decisions, Telegram account actions, or third-party legal compliance.

Non-public information exchanged between you and Verify Checkout, including API keys, credentials, receiving-account details, technical documentation, non-public pricing, security information, business terms, integration details, and support context, should be treated as confidential unless it is already public or independently developed without use of confidential information.

We may suspend or terminate your access to Verify Checkout if:

• You violate these Terms or applicable law.
• Your account creates legal, security, fraud, operational, provider, or reputational risk.
• Payment fails, usage exceeds plan limits, or billing information cannot be verified.
• Your API keys, accounts, sessions, webhook endpoints, receiving accounts, or integrations are compromised or misused.
• We are required to do so by law, regulation, provider requirement, court order, or valid government request.

You may stop using Verify Checkout at any time. Some obligations, including payment obligations, confidentiality, data protection duties, disclaimers, limits of liability, indemnification, and dispute terms, will survive termination.

Verify Checkout is provided on an as is and as available basis. To the maximum extent allowed by law, we disclaim all warranties, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, availability, security, and error-free operation.

We do not guarantee that verification results will always be correct, complete, current, accepted by a bank, accepted by a customer, accepted by a regulator, final for settlement, protected from reversal, or sufficient for accounting, fraud prevention, dispute resolution, or legal compliance.

Verify Checkout does not guarantee that a payer will complete a transfer, that a merchant will credit a customer, or that funds sent to a receiving account will remain available.

To the maximum extent allowed by law, Suba Software Solutions, its owners, employees, contractors, affiliates, suppliers, and partners will not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, lost goodwill, business interruption, failed transactions, reversed transactions, unsettled transfers, customer disputes, fraud losses, chargebacks, provider downtime, provider endpoint shutdowns, or third-party failures.

To the maximum extent allowed by law, our total liability for all claims related to Verify Checkout will not exceed the greater of the amount you paid to us for the service during the three months before the event giving rise to the claim or the liability amount stated in your active written plan or separate agreement, if any.

Some jurisdictions do not allow certain limitations, so some of the above may not apply.

You agree to defend, indemnify, and hold harmless Suba Software Solutions, its owners, employees, contractors, affiliates, suppliers, and partners from claims, damages, liabilities, losses, costs, and expenses arising from:

• Your use of Verify Checkout.
• Your Customer Data, receiving accounts, logos, and checkout materials.
• Your violation of these Terms.
• Your violation of applicable law.
• Your misuse of verification results.
• Unauthorized checkouts or transaction checks submitted by you or your users.
• Your integrations, webhook endpoints, applications, customer-facing services, staff activity, or disputes with your payers.

We may update these Terms from time to time. When we do, we will update the effective date or provide notice where appropriate. Your continued use of Verify Checkout after updated Terms take effect means you accept the changes.

These Terms are governed by the laws of Ethiopia, without regard to conflict of law rules. Disputes will be handled through the competent courts or dispute-resolution process available under applicable Ethiopian law unless a separate written agreement states otherwise.

For questions about these Terms, contact Verify Checkout through official channels.

• Verify Checkout
• Suba Software Solutions
• Email: info@verifycheckout.et
• Website: checkout.verify.et
• Telegram: https://t.me/suba_software_solutions
• Operator: subasoftware.com