Skip to content

Legal

Merchant Services Agreement

The commercial agreement between mPay and a merchant processing payments on the platform.

Effective date: This draft has not yet taken effect.Operating entity: Business identity and registration information will be published before production merchant onboarding opens.

This document is a working draft prepared for qualified legal review. It is not legal advice and has not yet been reviewed by counsel.

1. Merchant responsibilities

Operate a lawful business, describe your goods and services accurately, honour your refund policy, keep your account information current and comply with the Acceptable Use Policy.

2. Processing authorisation

You authorise mPay and its payment providers to process payments you initiate through your account, and to debit amounts owed under this agreement.

3. Pricing

Fees are those shown on your account before processing. mPay will notify you of changes in accordance with the Terms of Service.

4. Settlement, reserves and pending balances

Collected payments may be held in a clearing state, and a reserve may be applied to your account based on risk. Release schedules are shown in your dashboard; settlement terms are Settlement timing, supported assets and any withdrawal or network charges are confirmed during merchant onboarding and will be published before production launch..

5. Prohibited transactions

You may not process transactions on behalf of another business, split a transaction to evade limits, or process any activity listed in the Acceptable Use Policy.

6. Refunds, disputes and fraud monitoring

You will cooperate with refund and dispute handling and provide evidence on request. mPay monitors payment activity for indicators of fraud and prohibited use, and may hold or reverse affected payments.

7. Service suspension

mPay may suspend processing where required by a payment provider, by law, or where this agreement is breached.

8. API usage

API keys are secret and must be used only from your own systems. You are responsible for activity performed with your keys. Do not embed keys in client-side code.

9. Data protection

Each party will handle personal information in accordance with applicable law and the Privacy Policy.

10. Indemnification and termination

You will indemnify mPay against losses arising from your breach of this agreement or your underlying transactions, to the extent permitted by law. Either party may terminate in accordance with the Terms of Service. Final terms are The governing-law provision will be added after the operating entity and jurisdiction are finalized..

mPay

Payment links, hosted checkout and API integration for eligible businesses and independent professionals.

Legal business name
Business identity and registration information will be published before production merchant onboarding opens.
Registered address
Business identity and registration information will be published before production merchant onboarding opens.
Support email
Official domain-based support contact details will be published before production launch.
Merchant onboarding is currently by approval — accounts are issued after review rather than by public sign-up, and available payment methods may be limited per account and region.

Payment-method availability depends on region, merchant eligibility and provider availability. Third-party names and trademarks belong to their respective owners. Their appearance describes potential payment-method compatibility and does not imply ownership, sponsorship or endorsement. Availability may vary.

© 2026 Business identity and registration information will be published before production merchant onboarding opens.. mPay is a product name.

We use strictly necessary cookies to run this site. With your permission we would also use analytics and advertising cookies to measure how the site performs. You can change this at any time. Cookie Policy