SETTLEMENT INFRASTRUCTURE · MARKETPLACES
Govern when marketplace payments are released.
ArosaPay gives marketplaces a conditional settlement layer for buyer confirmation, delivery proof, review windows, and dispute handling — so funds move only when the agreed conditions are met.
Rules are enforced by ArosaPay's transaction state model and audit trail. Every material state transition is recorded so buyer, seller, and platform teams share the same view of the transaction.
Funds safeguarded at checkout · Released after confirmation · Review path if something goes wrong
The settlement primitives marketplaces need
Four primitives. One governed transaction flow.
Funds safeguarded
Payment is safeguarded against a transaction record before fulfillment begins. Seller release depends on the agreed condition.
Outcome triggers
Release can depend on buyer confirmation, delivery proof, review window expiry, or a platform-approved condition.
Configurable rules
Review windows, release conditions, seller references, and platform fees can be configured by approved integration profile.
Structured review
If something goes wrong, the transaction moves into review. Evidence can be requested before release, refund, or partial resolution.
Funds move when the agreed conditions are met. Not before.
Traditional payment flow
─Payment can move before the outcome is verified
─Trust gaps are handled manually
─Disputes may rely on ad-hoc support
─Settlement logic often lives outside the marketplace workflow
ArosaPay conditional settlement
▸Payment is safeguarded before fulfillment
▸Release follows buyer confirmation or the agreed condition
▸Review paths are structured and auditable
▸Settlement status is visible across buyer, merchant, and admin views
Transaction lifecycle
One governed path from payment safeguarding to release.
Every transaction on your platform advances through the same state model. Release depends on the agreed condition — buyer confirmation, delivery proof, review window expiry, or another approved trigger.
FUNDS SAFEGUARDED
funds_safeguarded
Payment is safeguarded against the transaction record. Funds are not released to the seller yet.
IN FULFILLMENT
in_fulfillment
Seller fulfills the order. Delivery proof or fulfillment status may be recorded against the transaction.
AWAITING CONFIRMATION
awaiting_confirmation
Buyer confirmation, delivery proof, or review window expiry is awaited before release becomes eligible.
RELEASE PENDING
release_pending
The release condition has been met. Settlement action is pending completion under the approved workflow.
SETTLEMENT RELEASED
settlement_released
Settlement has been released according to the approved transaction outcome. Configured platform fee splits apply.
Exception path · if a buyer reports a problem
UNDER_REVIEW ──▶ EVIDENCE_REQUESTED ──▶ RESOLUTION_DECISION ──▶ SETTLEMENT_RELEASED │ REFUNDED │ PARTIAL_RESOLUTION
Release is blocked while the transaction is under_review. Buyer and merchant evidence may be requested; the outcome resolves to settlement_released, refunded, or partial_resolution.
Review window
Configurable by approved integration profile.
Release trigger
Buyer confirmation, delivery proof, review window expiry, or another approved condition.
Rule enforcement
Rules are enforced by ArosaPay's transaction state model and audit trail.
Public lifecycle shown · Internal states align with the canonical transaction state machine
See the full state referenceProgrammable settlement
Settlement rules expressed in marketplace language.
Define release conditions, review windows, platform references, and payout logic through approved integration rules.
POST /v1/transactions
{
"amount": 12500,
"currency": "KES",
"merchant_reference": "MKT-ORD-100245",
"seller_id": "seller_4f9",
"idempotency_key": "txn_2026_07_26_001",
"release_condition": {
"type": "buyer_confirmation_or_review_window",
"review_window_days": 7
},
"settlement_rules": {
"platform_fee_bps": 290,
"fixed_fee": 30
},
"callback_url": "https://platform.example.com/webhooks/arosapay"
}Illustrative request structure. Final production schema may vary by approved integration profile.
Use cases
Where marketplaces apply conditional settlement
E-commerce marketplaces
Multi-vendor platforms where settlement release depends on delivery confirmation or buyer confirmation.
Release · on confirmation · Rules · per profile
Classifieds platforms
Buyer-to-seller transactions where payment can be safeguarded until the agreed condition is met.
Release · on confirmation · Review · window-based
B2B procurement
Order, delivery, or milestone-based settlement rules for approved supplier workflows.
Release · milestone · Rules · contractual
Logistics-linked commerce
Release conditions tied to delivery proof or partner-confirmed fulfillment events where integrated.
Release · on delivery proof · Rules · per profile
Outcome
Lower COD exposure
Outcome
Structured dispute handling
Outcome
Clearer seller release rules
Outcome
Auditable settlement decisions
Integration
Wire conditional settlement into your stack.
REST API
Create, inspect, and govern transactions through an approved API surface.
Webhooks
Receive signed events for material state changes across the transaction lifecycle.
Reconciliation
Use merchant_reference, seller_id, arosapay_transaction_id, settlement_status, and event IDs to reconcile transactions.
Rule profiles
Configure approved release conditions and review windows by integration profile.
Integration timelines depend on platform scope, payment methods, reconciliation needs, and approval requirements.
View API docsFunds safeguarding & settlement controls
How the money layer is governed.
ArosaPay records each transaction against a settlement state, release condition, and audit trail. Every material state transition is audit-logged.
Ledger records
Each transaction carries references, status history, and settlement state so buyer, merchant, and admin views stay aligned.
Release controls
Settlement release follows buyer confirmation, review window expiry, delivery proof, or another approved condition.
Dispute posture
If a problem is reported, release is blocked while evidence is reviewed. Routing rules are platform-configurable; outcomes are auditable.
Audit trail
Material events are recorded for reconciliation, support, and review. Payment movement follows approved partner rails and ArosaPay's conditional settlement workflow.
Simple, Transparent Pricing
Sellers pay the fee. Buyers pay nothing.
per completed transaction · min KES 100
- 7-day inspection period
- Photo evidence system
- Dispute mediation
- M-Pesa settlement on confirmation
- Works with any listing platform
- No buyer fees
Minimum
KES 5,000
Maximum
KES 2,000,000
Example Calculation
FAQ
Common questions from platform teams
Marketplace settlement review
Request a marketplace settlement review.
Tell us how your platform handles seller payouts, disputes, reconciliation, and release conditions. Our platform team will review the fit and come prepared with a proposed ArosaPay settlement flow.
Run a marketplace? Govern when money moves.
Conditional settlement infrastructure for platforms. Wire it in days, not quarters.