Overview
mPAY24 is listed as payment aggregator in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.
Role in the payment stack
PSP / aggregator
This is closer to a provider route than a buyer-facing payment method. Confirm which local methods it can enable, where your merchant entity can be onboarded, and who handles settlement, refunds, and disputes.
What merchants should confirm
- Whether the product is available to merchants incorporated outside the target country.
- Whether a local entity, local bank account, licence, or local tax registration is required.
- Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
- Industry restrictions, reserve policies, onboarding documents, and implementation support.
Merchant eligibility
Merchant eligibility and entity requirements must be confirmed with the provider.
Pricing and settlement
Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.
Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.
Capability verification checklist
Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.
- Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
- Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
- Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.
Official links to open
Commercial terms to confirm
| Pricing model | psp or aggregator quote |
|---|---|
| Pricing basis | official public pricing or terms |
Fields still to confirm
- Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
- FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.
Integration route to confirm
| Sandbox | yes |
|---|---|
| Webhooks | yes |
Fields still to confirm
- API / checkout route: confirm with the provider, acquirer, PSP, or official documentation before launch.
- SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
- Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
- PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
- 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.
Operational features to confirm
| Recurring billing | yes |
|---|---|
| Partial refund | yes |
| Preauth / capture | yes |
Fields still to confirm
- Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.