Terms of Service

1. Who these terms are for

YembiPay is a business service. It is offered to organizations, such as fintechs, remittance operators, payroll providers, and merchants, that settle value for themselves or for their own customers. It is not offered to individuals acting as consumers, and it is not available to anyone under 18 or to any person or organization in a restricted location listed in the Acceptable Use policy. If YembiPay launches a consumer product, it will publish separate consumer terms.

2. Accepting these terms

You accept these terms by browsing the website, creating an organization, requesting or using credentials, using the sandbox, or calling the API. An operator who accepts on behalf of an organization confirms that they have authority to bind it. Sandbox access is acceptance of these terms even though no value moves.

3. Organizations, operators, and credentials

An organization is responsible for every operator it authorizes and for every request made with its credentials. API keys, webhook signing secrets, and browser sessions are the security procedure that identifies your organization to YembiPay. A request that carries your valid credentials is treated as your instruction and is binding on you, even if it was sent by someone you did not authorize, until you have told us the credential is compromised and we have had a reasonable opportunity to revoke it.

A leaked API key can create settlements, lock quotes, read recipient records, and change webhook endpoints within its scope. Treat keys accordingly: issue one key per integration and environment, use the narrowest scope the integration needs, rotate keys on a schedule, and revoke a key the moment you suspect exposure. Never place a key, a webhook secret, or beneficiary bank data in a public form, a URL, a support message, or a shared document. Report suspected compromise immediately to security@yembipay.com. Except where a loss is caused by YembiPay's own failure, YembiPay is not responsible for instructions accepted under your credentials before you reported the compromise.

Browser sessions for the partner dashboard are short-lived, bound to one organization, and carried in encrypted, HttpOnly, same-site cookies. Closing a session does not revoke API keys.

4. Service states

YembiPay publishes three service states and labels every capability with one of them.

• Sandbox. No value moves. Rails, screening providers, and chain writes are documented simulations. Quotes, settlements, and certificates produced in the sandbox are not evidence of live compliance and must not be presented to anyone as such.
• Controlled readiness. Real dependencies are wired but value movement is gated per corridor and per organization. Access may be narrowed or withdrawn while gates are open.
• Live. Value moves for a named corridor and a named organization under a signed agreement.

Website content is not a guarantee that a corridor, rail, currency, token, limit, or feature is available to your organization. The authenticated capability state returned by the API controls. Features marked preview or beta may change or be withdrawn without notice and must not be relied on for production volume.

5. Integration obligations

• Keep your integration on a supported API version and implement announced changes within the window stated in the change notice.
• Webhooks are delivered at least once. Verify the signature on every delivery, deduplicate by event identifier, and acknowledge only after durable intake.
• Rate limits and volume limits apply per organization and may change with notice. Do not attempt to bypass them.
• Retry a value-moving command only with the original idempotency key and only after reading the current authoritative state. Submitted, accepted, confirmed on-chain, paid out, reversed, and reconciled are distinct states with distinct meanings.
• Software agents, automations, and AI tools that act under your credentials are you. Their requests are your instructions and are subject to the same idempotency, state, and screening rules as any other request.

6. Compliance obligations and screening consent

Before an organization can move value, YembiPay verifies it. That includes the legal entity name and registration, the registered address and country, beneficial owners holding 25 percent or more, directors and authorized signatories, and a source-of-funds declaration. YembiPay may ask for re-verification at any time and may suspend access until it is complete.

By using the service you consent, on behalf of your organization, to YembiPay screening your organization, its operators, its beneficial owners, and every recipient and wallet address you submit, at onboarding and on every settlement, against sanctions lists, stablecoin issuer address lists, and anti-money-laundering controls. You agree to supply accurate originator and beneficiary information with every settlement, including the identifying information required by the Travel Rule at or above USD 3,000, and to produce your own customer due diligence records on request when you settle on behalf of your customers.

YembiPay may delay, hold, reject, return, or reverse a settlement, and may suspend or end an organization's access, on the basis of a screening result, a monitoring alert, a legal order, or a provider's action. Where law prohibits it, YembiPay will not explain the reason for a match or a report. The full program is described in the AML and Sanctions Statement.

7. Prohibited use

You may not use YembiPay for any activity listed as prohibited in the Acceptable Use policy, and you may not use a restricted activity without the licence evidence and enhanced review that policy describes. In every case you may not: access or probe another organization's data or authorization boundaries; submit unlawful, deceptive, sanctioned, or unauthorized transactions; misrepresent a beneficiary, an originator, or the purpose of a settlement; structure settlements to avoid limits or reporting; bypass or test screening, rate limits, evidence requirements, or service restrictions without written permission; reuse another organization's idempotency keys or quote identifiers; or scrape quotes to build a rate feed.

8. Fees, quotes, and taxes

Fees are stated in your signed agreement or shown on the quote before you accept it. Every quote carries an expiry; a rate is locked only when a settlement is accepted against a valid quote within its 30-second lock, and YembiPay never executes at an expired rate. Fees charged in error are refunded. The details are in the Settlement, Quote, and On-Chain Terms.

You are responsible for determining, reporting, and paying any tax that applies to your organization, your customers, or your settlements. Tax treatment of stablecoin settlement differs by jurisdiction and may change. YembiPay may withhold or report where law requires. YembiPay does not give tax, legal, accounting, or investment advice, and nothing in a quote, a rate, a certificate, or the dashboard is a recommendation. No fiduciary relationship arises between you and YembiPay.

9. Suspension and termination

Either party may end the relationship on 10 business days' written notice. YembiPay may suspend or end access immediately, with notice as soon as it is permitted, where a legal order, a sanctions or screening result, a security incident, an insolvency event, a provider's withdrawal, or a breach that cannot be cured requires it.

On suspension or termination: settlements already accepted are completed or returned under the Settlement, Quote, and On-Chain Terms and are not abandoned mid-flight; new settlements are refused; you may export your organization's records through the API for 30 days; and amounts owed by either party remain payable. Sections 3, 6, 8, 10, 12, 13, 14, and 16 survive.

10. Legal orders and holds

YembiPay may comply with a subpoena, warrant, court order, regulator request, or other legal process that it considers valid, may hold or freeze value that is the subject of such process, and may disclose information under it. YembiPay may be prohibited from telling you. YembiPay is not liable for delay or loss that results from good-faith compliance. Procedures for authorities are in Legal and Law-Enforcement Requests.

11. Electronic communications

You agree that YembiPay may deliver notices, disclosures, certificates, statements, and changes to these terms electronically, through the partner dashboard, by email to your registered operators, by webhook, and as PDF documents. Electronic delivery satisfies any requirement that a communication be in writing. Keep your operators' contact details current; a notice sent to the last registered address is delivered. Withdrawing this consent ends your ability to use the service, because the service cannot operate on paper.

12. Intellectual property and marks

YembiPay and its licensors retain all rights in the platform, API, documentation, designs, marks, certificates, and software, except where an open-source licence or a signed agreement says otherwise. You receive a limited, revocable, non-exclusive licence to use them to integrate with and use the service. If you send feedback, YembiPay may use it without restriction or payment.

You may state truthfully that a settlement was executed through YembiPay and may cite a certificate by its identifier. You may not imply that YembiPay endorses your organization, that YembiPay is licensed where it has said it is not, or that a sandbox artifact is a live result. YembiPay will name your organization as a partner only with your written consent.

13. Third-party services

Settlement depends on services YembiPay does not control: stablecoin issuers and their contracts, blockchain networks and node providers, local payment rails and the banks that participate in them, identity verification providers, and hosting and edge providers. Each has its own terms, availability, and conduct. YembiPay selects, monitors, and may change them, and lists the ones that process partner data on the Sub-processors page. Beyond what a signed agreement provides, YembiPay is not responsible for a third-party service's failure, delay, freeze, or change.

14. Disclaimers, liability, and indemnity

Public materials, the sandbox, and preview features are provided as they are, without promises beyond those in a signed agreement. Warranties, exclusions, liability caps, indemnities, and dispute terms for live settlement are set in that agreement. For website and sandbox use where no agreement exists, YembiPay's liability is excluded to the fullest extent the applicable law permits, and it is never liable for indirect or consequential loss, for loss caused by a destination address, network, or beneficiary detail you supplied, or for the irreversibility of a confirmed on-chain transfer. You will defend YembiPay against claims that arise from your breach of these terms, from your customers, or from instructions sent with your credentials.

15. Changes

These terms change as described on the legal hub: independent versioning, at least 14 days' notice of material changes to registered organizations, and earlier effect only where law, a regulator, or a security risk requires it.

16. Governing law and disputes

Governing law and forum for a signed agreement are stated in that agreement. For these website terms, the governing law and forum are those of the jurisdiction in which YembiPay's contracting entity is registered; that entity and its registration details are published on this site after founder and legal verification. Before starting any proceeding, the parties will raise the dispute in writing with legal@yembipay.com and negotiate in good faith for 30 days. Nothing here prevents either party from seeking urgent relief to protect credentials, data, or funds.

17. Contact

Terms and contracting questions: legal@yembipay.com. Security reports: security@yembipay.com. Complaints: see Complaints.