Skip to main content
    How It Works

    How ArosaPay protects
    every transaction.

    ArosaPay safeguards payment before release and releases settlement only after buyer confirmation, review window expiry, or the agreed release condition. If something goes wrong, the transaction moves into review before release, refund, or partial resolution.

    Payment safeguarded before release · Buyer confirms before settlement · Review path if contested

    The Process

    How protected checkout works

    The same five steps apply to buyers and merchants. Every transaction moves through them in order.

    01

    Create the transaction

    The buyer and merchant agree on the item, amount, release condition, and review window before payment is safeguarded.

    02

    Payment is safeguarded

    The buyer pays through ArosaPay's protected checkout flow. Payment is attached to the transaction record and is not released to the merchant yet.

    03

    Merchant fulfills

    The merchant ships, delivers, hands over, or completes the agreed service. Delivery proof or supporting evidence may be attached where supported.

    04

    Buyer reviews

    The buyer checks the item, service, or agreed outcome against the transaction terms.

    05

    Confirm or report an issue

    If the buyer confirms, settlement moves toward release. If there is a problem, the transaction moves into review before release, refund, or partial resolution.

    The applicable review window is defined in the transaction terms or merchant agreement. Confirmation moves the transaction toward release according to the approved settlement process.

    Exception path

    If something goes wrong

    If the buyer reports a problem, release pauses and the transaction moves into review. Evidence may be requested from the buyer, merchant, or both before settlement release, refund, or partial resolution.

    Possible outcomes

    • Settlement released
    • Refund
    • Partial resolution
    • Further evidence requested

    Funds flow

    How payment moves from checkout to conditional settlement.

    ArosaPay separates payment safeguarding from final merchant settlement. Payment is attached to a transaction record first. Settlement follows buyer confirmation, review window expiry, or the agreed release condition.

    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.

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

    Why ArosaPay

    Built around visible transaction states.

    Protected checkout works because every party sees the same status, evidence, and release rules.

    Clear release conditions

    Every transaction carries a release condition so both sides understand what must happen before settlement.

    Buyer confirmation

    Settlement follows buyer confirmation, review window expiry, or another agreed release condition.

    Structured review path

    If something is contested, release pauses while evidence is reviewed before release, refund, or partial resolution.

    Audit trail

    Material transaction events are recorded so buyer, merchant, support, and admin views stay aligned.

    FAQ

    Frequently Asked Questions

    Everything you need to know about using ArosaPay

    Still deciding? See the ArosaPay overview for buyers and merchants or start a merchant application.

    Ready to use protected checkout?

    Create a transaction with clear release rules, visible status, and a review path if something goes wrong.

    Standard pricing: 2.9% + KES 30, minimum KES 100, charged on completed transactions only.