MANIDASO PAY

Protected Payments for Verified Trade

Set terms. Fund when eligible. Release only when confirmation is recorded.

Condition-based release — otherwise Resolve.
Eligibility checked
Funds held
Release recorded
Resolve disputes
PAY PROTOCOL
Protected Payment
Rule
Condition-based release
Record
Timestamped release log
Protection
Resolve path available
Reference
Pay ID issued instantly
Status
Protocol active
Every step is recorded to match the trade.
QUICK START
Start a Protected Payment
Availability varies by corridor.
Select the event that triggers release.
We’ll send your Pay reference here.
Required — used to match your Pay request to the correct trade.
Request received

We’ve received your Pay request. Check your email for your Pay reference and next steps.

Keep your Customer reference handy — we use it to match your trade.
We couldn’t create your request

Please check the required fields and try again.

If it continues, contact Support and include your Customer reference.
Enabled where checks and exception handling can be supported.
View fee guide →
OVERVIEW

Condition-Based Release for Trade

Traditional payments can complete even when trade steps are unclear.

Pay links payment handling to agreed conditions, recorded confirmation, and a defined exception path.

DEFINITION

A confirmation condition is a measurable event agreed by both parties (for example: handover, inspection approval, delivery confirmation).

Terms First

Terms and conditions are agreed before funding.

Release by Condition

Release follows recorded confirmation of the condition.

Reviewable History

Key actions are time-stamped for review and exceptions.

SCOPE & ROLE

MANIDASO Pay is a platform payment workflow for verified trade.

It may rely on regulated payment providers for processing and does not provide regulated financial services unless explicitly stated.

PROCESS

How Payment Release Works

Pay follows a defined sequence. Requirements and confirmation are visible to both parties.

01

Create Terms

Amount, parties, corridor, and condition.

02

Complete Required Checks

Identity and trade readiness where required.

03

Confirm Funding

Funding confirmed and linked to a transaction ID.

04

Record Stage Updates

Move/Verify records may support confirmation.

05

Record Confirmation

Condition met, evidence recorded.

06

Release or Resolve

Designed to release under the rules — or route to Resolve.

COVERAGE

What Pay Protects — and What It Doesn’t

Pay reduces payment uncertainty by making conditions explicit and reviewable.

For Buyers
Release is tied to the agreed condition
Clear view of what is required
Defined exception path
For Sellers
Funding confirmation recorded before processing
Conditions agreed up front
Structured handling when exceptions arise
What Pay does not do
No guarantees on delivery dates, quality, or outcomes
Does not replace due diligence, inspection, or documentation checks
Risk is reduced, not removed
ENABLEMENT

Enabled When Conditions Can Be Supported

Pay is enabled where verification and exception handling can be supported. Requirements vary by corridor and context.

Enabled only where corridor support and exception handling can be provided.
Eligibility checklist
Verified participant identity (role-based)
Transaction details complete and reviewable
Required documentation present where applicable
Condition is clear and measurable
Corridor support is active (where relevant)
Not supported (examples)
Conditions that cannot be evidenced
Prohibited/restricted items or sanctioned parties (where applicable)
High-risk contexts where required checks cannot be completed
Standard Trade
High-Value Trade
Business / Bulk
Requirements are proportionate to role, value, and stage.
FEES

Transparent Fees, Shown Before You Confirm

Fees depend on value, payment method, corridor, and verification requirements.

You’ll see all fees before you confirm.

Protected payment handling fee — varies by value & method
Verification requirements — role/value dependent
Exception handling (only if used) — only when triggered
View Fee Guide →
SECURITY

Built for Auditability

Actions are recorded so exceptions follow a defined process.

Identity & Role Checks
Access is granted based on verified identity and approved role (where required).
Recorded Confirmations
Key confirmations are recorded with timestamps and linked to the transaction.
Exception Routing
When confirmation isn’t reached, cases route into a structured review path.
Account Controls
Secure access, monitoring, and safeguards help protect account activity.
Records support audit and dispute handling. Access is role-based.
Controls reduce risk. They do not eliminate risk.
View Fee Guide →
EXCEPTIONS

When Confirmation Isn’t Reached, There’s a Path

If confirmation cannot be reached, the transaction routes into a structured review process.

Exception types
Missing confirmation evidence
Delivery exception or inspection hold
Documentation mismatch
Fraud indicators (review triggers)
HELP

Common Questions

Quick answers. Full details are available in the Help Centre.

READY

Start a Protected Payment

Set terms, confirm eligibility, and fund with a condition-based release path.

Pay supports structured transactions. It does not guarantee results, timelines, or third-party performance.