How ArosaPay works

1. 01

   Payment safeguarded

   The buyer completes checkout. Funds are safeguarded against the transaction and are not available to the seller yet.

2. 02

   Merchant fulfils

   The transaction becomes ready for fulfillment. The seller ships, delivers or performs, and records fulfilment on the transaction.

3. 03

   Buyer reviews

   The transaction moves to awaiting buyer confirmation. The buyer checks that what arrived matches what was agreed.

4. 04

   Release pending

   Once the buyer confirms — or the review window closes without a reported problem — the transaction enters release pending.

5. 05

   Settlement released

   Funds are released to the seller's settlement destination and the transaction reaches its final recorded state.

Every state change is recorded against the transaction, so both sides read the same record at the same time. See how protected checkout is presented to buyers and the end-to-end product overview.

When a buyer reports a problem before confirmation, the transaction leaves the standard path and follows a structured review instead of releasing.

1. 01

   Problem reported

   The buyer records what is wrong. Release does not proceed while the report is open.

2. 02

   Under review

   ArosaPay reviews the transaction record and the account history on both sides.

3. 03

   Evidence requested

   Either party may be asked for specific evidence within a stated window.

4. 04

   Resolution

   The outcome is recorded on the transaction: settlement released, refund processing, or a split outcome where that was agreed.

There is one ArosaPay identity per person or business. Buying and selling are capabilities on that identity, not separate accounts. An existing buyer can add seller capability later without creating a second login — see Become a seller.