Skip to content
GitHub Sign In Get Started

Legal

Terms of Acceptable Use

The rules for building on Ureh: what you're responsible for, what isn't allowed, and what happens if it is.

Last updated: August 28, 2026

These Terms of Acceptable Use ("Terms") govern your access to and use of the Ureh API platform, Developer Console, documentation, and related services (together, the "Service"), operated by Ureh ("Ureh," "we," "us," or "our"). By creating an account, generating an API key, or otherwise using the Service, you ("you," a "Client") agree to these Terms on behalf of yourself and, if applicable, the business you represent.

If you do not agree to these Terms, do not use the Service. For how we handle data rather than how we expect it to be used, see the Privacy Policy.

1. Acceptance of Terms

Registering for a Developer Console account, and every subsequent authenticated request made with a Secret or Public Key issued to that account, constitutes acceptance of the version of these Terms in effect at the time. If you're accepting on behalf of a company, you confirm you have the authority to bind that company.

2. Description of Service

Ureh provides a programmatic API for bill payment products (airtime, data, cable TV, electricity and education), together with wallet management, transaction tracking, and webhook notifications. Every request is authenticated, priced by Ureh, debited from your wallet, and fulfilled through a provider on your behalf. We may add, change, or retire products, endpoints, or provider integrations at our discretion, and will use reasonable efforts to give advance notice of a change that breaks an existing integration.

3. Eligibility and Account Registration

  • You must be at least 18 years old and able to form a binding contract to register.
  • Registration information (business name, contact details, settlement information, and any KYC/KYB documentation requested) must be accurate and kept up to date.
  • One account per business, unless we agree otherwise in writing. Creating duplicate accounts to evade a rate limit, a suspension, or a pricing tier is a violation of these Terms.
  • You are responsible for every action taken under your account, whether by you, an employee, or anyone else you give access to.

4. Developer Responsibilities and API Keys

Your Secret Key can execute every endpoint, including purchases and wallet debits. Treat it accordingly:

  • Never expose a Secret Key client-side. It must never appear in a mobile app, browser JavaScript, public repository, or any other place an end user or the public could read it. If your integration has a client-side component, that component should call your own backend, which then calls Ureh, not the other way around.
  • Use the Public Key only for what it's for. Read-only lookups such as validate and variations calls. A Public Key is rejected on a purchase or webhook-subscribe endpoint by design, not by omission.
  • Rotate a key the moment you suspect it's compromised. Issue a replacement from the Developer Console and revoke the old one; we are not liable for activity authenticated with a valid key you failed to secure or revoke.
  • Generate a fresh idempotency_key per logical purchase attempt, and reuse it only when retrying that exact attempt. See the Idempotent requests guide.
  • Verify webhook signatures before trusting a payload, using the HMAC-SHA256 scheme documented in the webhook signature guide, and respond quickly so a slow endpoint doesn't read as a failed delivery.
  • Handle your own end users' data responsibly. See "Data Collection and Usage" below.

5. Acceptable Use

You agree to use the Service only for its intended purpose. You will not:

  • Use the Service for any unlawful purpose, or to facilitate money laundering, terrorist financing, or sanctions evasion.
  • Submit a transaction you know to be fraudulent, unauthorized, or on behalf of a recipient who has not consented to it.
  • Attempt to gain unauthorized access to any account, system, or data that isn't yours, including another Client's.
  • Reverse-engineer, decompile, or attempt to derive the source code of any part of the Service that isn't your own integration.
  • Resell or sublicense direct access to the API itself as a competing bill-payment API: building a product on top of Ureh for your own customers is exactly what the Service is for; reselling raw API access as a substitute for signing up with Ureh directly is not.
  • Interfere with or degrade the Service for other Clients, including through excessive load that isn't reasonably tied to genuine transaction volume.
  • Misrepresent your identity, your business, or your relationship to Ureh, including implying an affiliation, partnership, or endorsement that doesn't exist.

6. API Abuse and Rate-Limit Circumvention

Every request is checked against four independent rate-limit dimensions (ip, api_key, client, and endpoint), documented in full in Rate Limits. These exist to keep the Service available and fairly shared. You will not:

  • Rotate IP addresses, API keys, or accounts to evade a rate limit, a suspension, or a fraud control.
  • Send automated, scripted, or bulk requests at a volume disproportionate to genuine end-user demand, including load-testing production endpoints without our prior written agreement.
  • Probe, scan, or fuzz the API to discover undocumented behavior, or rely on undocumented behavior in a production integration.
  • Bypass, or attempt to bypass, any technical control (authentication, authorization, rate limiting, or idempotency) through means other than the documented API contract.

A rate-limited request already receives a 429 with a Retry-After header rather than being silently dropped. This section covers deliberately working around that limit, not occasionally hitting it.

7. Fraud Prevention and Prohibited Transactions

We monitor transactions for patterns consistent with fraud, and reserve the right to hold, decline, reverse, or request additional verification for any transaction we reasonably believe is fraudulent or unauthorized, without liability to you or your end user for doing so. You will not:

  • Submit transactions funded by stolen payment instruments or compromised accounts.
  • Use the Service to test the validity of stolen card or account details ("carding").
  • Structure transactions to evade a fraud control, reporting threshold, or regulatory limit.
  • Knowingly facilitate a transaction for a sanctioned individual, entity, or jurisdiction.

A failed transaction is refunded to your wallet automatically under normal operation; a transaction reversed for suspected fraud is handled case by case and is not guaranteed the same automatic refund while under review.

8. Data Collection and Usage

Ureh's own collection and use of information is governed by the Privacy Policy, not by these Terms. Where your integration collects information about your own end users (to submit a purchase on their behalf, for example), you are the party responsible for that collection: you must have a lawful basis and, where required, that end user's consent, you must provide your own privacy notice covering it, and you must not submit more of an end user's information to the Service than a given product actually requires to complete the transaction.

9. Intellectual Property

Ureh retains all right, title and interest in the Service itself (the API, the Developer Console, the documentation, and the Ureh name and marks). Nothing here grants you any ownership in it. You retain all right, title and interest in your own integration, your own end-user data, and any application you build on top of the Service. You grant Ureh a limited license to process what you submit through the API solely to provide the Service back to you. Using the Ureh name or marks to imply endorsement of your own product requires our prior written consent.

10. Fees and Payment

Fees are usage-based and resolved per transaction, as described on the Developer Earnings page; there is no setup fee or monthly minimum. You authorize us to debit your wallet for the resolved amount at the time each transaction is submitted. An unfunded wallet causes the request to fail validation before it reaches a provider, not a negative balance.

11. Suspension and Termination

We may suspend or terminate your access to the Service, with or without notice, for:

  • A violation of these Terms, including any prohibited conduct in "Acceptable Use," "API Abuse," or "Fraud Prevention" above.
  • Activity that poses a security risk to the Service or to other Clients.
  • A legal or regulatory requirement to do so.
  • Extended inactivity or a failure to maintain accurate account information.

Where practical, we will give notice and an opportunity to remedy a violation before termination; we may act immediately without notice where the conduct poses an active security or fraud risk. You may close your own account at any time from the Developer Console. Termination does not relieve either party of an obligation that accrued before it: a fee already owed remains owed, and a transaction already settled is not unwound solely because the account later closes.

12. Disclaimers

THE SERVICE IS PROVIDED "AS IS" AND "AS AVAILABLE," WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. WE DO NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, ERROR-FREE, OR FREE OF SECURITY VULNERABILITIES, OR THAT ANY PROVIDER, NETWORK OPERATOR, OR BILLER WE ROUTE A TRANSACTION TO WILL BE AVAILABLE AT ANY GIVEN TIME. YOU ARE RESPONSIBLE FOR TESTING YOUR OWN INTEGRATION AND FOR HANDLING A FAILED OR DELAYED TRANSACTION GRACEFULLY, INCLUDING THROUGH THE POLLING AND WEBHOOK MECHANISMS THE SERVICE PROVIDES FOR EXACTLY THAT PURPOSE.

13. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, UREH WILL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR ANY LOSS OF PROFITS, REVENUE, DATA, OR GOODWILL, ARISING FROM YOUR USE OF THE SERVICE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. UREH'S TOTAL LIABILITY FOR ANY CLAIM ARISING FROM THESE TERMS OR THE SERVICE WILL NOT EXCEED THE FEES YOU PAID TO UREH IN THE THREE MONTHS PRECEDING THE EVENT GIVING RISE TO THE CLAIM. THIS LIMITATION DOES NOT APPLY TO A PARTY'S GROSS NEGLIGENCE, WILLFUL MISCONDUCT, OR ANY LIABILITY THAT CANNOT BE LIMITED UNDER APPLICABLE LAW.

14. Indemnification

You agree to indemnify and hold Ureh harmless from any claim, loss, or expense (including reasonable legal fees) arising from your use of the Service, your violation of these Terms, or your violation of any right of a third party, including an end user of yours.

15. Governing Law and Dispute Resolution

These Terms are governed by the laws of the Federal Republic of Nigeria, without regard to conflict-of-laws principles. Any dispute arising from these Terms or the Service will first be addressed through good-faith negotiation between the parties; failing that, it will be subject to the exclusive jurisdiction of the courts of Nigeria.

16. Changes to These Terms

We may update these Terms as the Service evolves or as legal requirements change. A material change will be reflected by updating the "Last updated" date above, and, where the change meaningfully affects your obligations, by additional notice through the Developer Console or by email before it takes effect. Continued use of the Service after a change takes effect constitutes acceptance of the updated Terms.

17. Contact Us

Questions about these Terms can be sent to [email protected], through our Support page, or — if you already have an account — through the Developer Console's Support page.

Related: Privacy Policy · Developer Earnings