Skip to main content

Legal

Terms of Service

Last updated 24 August 2026

These terms explain how PeerPay works and what you agree to when you create an account, request merchant access, or use the dashboard, API, hosted checkout, or related services at peerpayment.org.

What PeerPay is

PeerPay is a non-custodial merchant platform for Ethiopian bank transfers and mobile wallets. We host checkout, assign merchant-managed receiving accounts, verify each submitted transaction ID or reference against the assigned receiving account through bank and wallet APIs, and notify you with signed webhooks and dashboard status.

PeerPay does not hold, pool, settle, refund, or pay out customer funds. Money moves outside PeerPay: the customer transfers from their own bank or wallet to a receiving account you control, or your agent transfers from a merchant-managed account to a customer destination.

Accounts and access

Merchant dashboard login uses Google. Creating an account does not by itself activate live merchant operations. You must submit a business application. PeerPay may approve, delay, or reject access based on the information you provide and our risk review.

  • You must be authorized to bind the business you represent.
  • Keep your Google account, API keys, webhook secrets, and dashboard access under your control.
  • API keys are machine credentials for your backend. They are not login passwords and must never be used in checkout or browser clients.

Your responsibilities

You operate the commercial relationship with your customers. PeerPay does not know whether you credited a wallet, fulfilled an order, or paid a withdrawal from your own books.

  • Provide accurate business, product-category, and support details.
  • Use only receiving accounts you own or are contractually authorized to use. Do not rotate personal or mule accounts to hide the merchant or evade bank, AML, or payment-provider controls.
  • Credit your customers only after a trusted PeerPay terminal success event, and do so idempotently by PeerPay order ID.
  • Comply with Ethiopian law, bank and wallet rules, licensing for your product category, and any age or restricted-user controls that apply to you.
  • Keep webhook endpoints public HTTPS, verify signatures, and handle events idempotently.

Deposits

When you create a deposit, PeerPay returns a hosted checkout URL and assigns an eligible receiving account. The customer transfers outside PeerPay and submits a transaction reference. PeerPay then checks receiver, amount, currency, transaction timing, and duplicate use. Browser redirects, screenshots, and customer claims are support signals only. Success comes from server-side verification.

Withdrawals

Withdrawals are a separate workflow. PeerPay can collect a customer destination, assign work to your agents, and verify the agent-submitted transfer reference. PeerPay does not send the money, hold a float, or treat deposits-minus-withdrawals as a bank balance.

Credits and fees

Approved merchants receive a one-time allowance of usage credits for successful deposits and withdrawals. Credits are not money or wallet balance. After credits are used, platform fees follow the pricing shown on the site and in your dashboard, currently including a percentage of successful transactions on the paid plan. We may change published pricing with notice on the site or dashboard.

Prohibited use

Do not use PeerPay to bypass bank or payment-provider restrictions, operate an unlicensed money-transfer service, run a hidden receiver network, or treat PeerPay as a trading, token, FX, or custodial wallet product. We may suspend tenants, keys, receiving accounts, or orders when we see abuse, fraud, duplicate-reference farming, or activity we cannot support.

Service and outcomes

Verification depends on banks and wallets confirming a submitted transaction ID or reference. Orders may succeed, fail, expire, or require review. We provide dashboards, evidence, and notifications so you can operate; we do not guarantee uninterrupted availability or that every submitted reference will verify.

Limitation of liability

PeerPay is provided as-is for orchestration and verification. To the extent allowed by law, we are not liable for lost funds sent to the wrong account, merchant wallet-crediting mistakes, downstream bank delays, or indirect losses. You remain responsible for customer support and for money that never passed through PeerPay.

Changes

We may update these terms as the product changes. The “Last updated” date at the top of this page is the current version. Continued use after an update means you accept the revised terms.

Contact

Questions about these terms can be sent through your merchant dashboard or the public site at peerpayment.org. Related reading: Privacy Policy.