Payments, Payouts, Refunds, Chargebacks, and Settlement Policy

Pawalink helps create payment requests, track transaction references, reconcile provider events, calculate platform fees, generate receipts, and maintain seller-visible settlement or payout states. The movement of funds itself is handled by third-party processors and payment rails where configured, including services such as Paystack, MTN MoMo, and Hubtel.

Processor availability may vary by merchant setup, market, payment method, device, or operational status. Processor rules, KYC requirements, fraud controls, and callback timing are outside Pawalink direct control.

A payment attempt is not the same as a confirmed payment. Pawalink may rely on provider callbacks, provider verification calls, internal reconciliation, or manual review before treating a transaction as confirmed. Settlement and payout readiness can also depend on refund activity, reserve handling, payout-account readiness, provider processing windows, and risk review.

Payouts may fail, be delayed, or be reversed. If a payout fails, amounts may return to a visible balance state or remain pending while the issue is resolved. If a refund or reversal occurs after payout, Pawalink may record a seller liability or reserve adjustment until the matter is settled.

Refunds and buyer disputes may be initiated by the merchant, the buyer, the payment provider, or as part of a chargeback or fraud workflow. Pawalink may record and surface these events, but refund rights, processor deadlines, and chargeback procedures are also governed by the merchant own terms and the processor rules that apply to the transaction.

Pawalink does not promise escrow, insurance, guaranteed fraud prevention, guaranteed seller verification, or guaranteed buyer recovery. [NEEDS FOUNDER DECISION: default refund posture and standard merchant response timeline.]