Skip to main content

    Trust & custody

    How ArosaPay holds your money.

    Payment is secured through ArosaPay and released only according to the agreed confirmation rules.

    Conditional settlement

    ArosaPay funds flow

    How buyer payments move from checkout to conditional merchant settlement. ArosaPay separates payment collection from final merchant settlement — funds are secured first and released only after satisfaction is confirmed or predefined conditions are met.

    • Funds movement
    • Status / confirmation signal
    • Successful release path
    • Review or exception path
    1. Phase 1 · Checkout

      Buyer

      Merchant

      ArosaPay

    2. Phase 2 · Payment

      Buyer

      Payment / settlement partner

      ArosaPay

    3. Phase 3 · Safeguarded

      Payment / settlement partner

      ArosaPay

    4. Phase 4 · Fulfilment

      Merchant

      Buyer

    5. Phase 5 · Confirmation

      ArosaPay

    6. Phase 6 · Outcome

      Release path

      ArosaPay

      Payment / settlement partner

      Merchant

      Dispute path

      ArosaPay

      Payment / settlement partner

      Outcome

    7. Phase 7 · Audit

      ArosaPay

      Outcome

    Transaction state

    1. Initiated
    2. Paid
    3. Funds safeguarded
    4. In fulfilment
    5. Confirmed / Under review
    6. Released / Refunded

    Final payment, safeguarding, settlement, and payout configuration depends on ArosaPay's approved payment and banking partner setup.

    1. Phase 1 — Checkout. Buyer: Selects goods or services. Status: Initiated. Merchant: Offers ArosaPay checkout. ArosaPay: Creates transaction record. Status: Initiated.
    2. Phase 2 — Payment. Buyer: Authorises payment. Payment / settlement partner: Processes payment. Status: Paid. ArosaPay: Records payment status.
    3. Phase 3 — Safeguarded. Payment / settlement partner: Payment safeguarded before release. Status: Funds safeguarded. ArosaPay: Awaiting confirmation. Status: Awaiting confirmation.
    4. Phase 4 — Fulfilment. Merchant: Ships product or delivers service. Status: In fulfilment. Buyer: Receives product or service.
    5. Phase 5 — Confirmation. ArosaPay: Satisfied or release conditions met?.
    6. Phase 6 — Outcome. ArosaPay: Issues release instruction. Status: Confirmed. Payment / settlement partner: Settles funds to merchant. Status: Released. Merchant: Receives settlement. Status: Settled. ArosaPay: Enters dispute workflow. Status: Disputed. Payment / settlement partner: Funds remain held. Status: Under review. Outcome: Resolution decision. Status: Refunded · Partial · Released.
    7. Phase 7 — Audit. ArosaPay: Records full audit trail. Status: Audit trail updated. Outcome: Closed. Status: Closed.

    Custody of funds

    Buyer funds are held by our licensed payment partner pending release. ArosaPay never commingles buyer funds with operating capital. Settlement accounts are segregated and reconciled daily.

    Regulatory posture

    ArosaPay operates as a technical orchestration layer integrated with licensed Payment Service Providers in Kenya. We are progressing toward direct CBK licensing as transaction volume scales.

    Security controls

    PCI DSS-aligned card handling via tokenisation. TLS 1.3 in transit, AES-256 at rest. Role-based access with full forensic audit logging on every state change.

    Settlement & disputes

    Settlement cycle is T+1. Disputes are reviewed by our arbitration team within < 48hrs based on documented evidence — not subjective judgement.

    Auditability

    Every fund movement is recorded in an immutable transaction ledger with idempotency guarantees. Merchants and regulators can request full reconciliation reports at any time.

    Buyer protection

    Funds are not released to the seller until the buyer confirms receipt or a policy timer completes. If something goes wrong, funds are frozen pending resolution.

    Operating partners

    Licensed payment infrastructure

    ArosaPay integrates with licensed Payment Service Providers in Kenya for fund custody, M-Pesa rails, and card processing. Specific partner names and license references are disclosed under NDA to enterprise customers and regulators on request.

    Public policies