Payment Information

1. Secure checkout

Checkout sends product IDs and quantities to Ordyvia’s server. Prices, inventory, delivery fee and total are recalculated server-side before a pending order and payment reference are created.

2. Authorization and verification

Customers are redirected to Paystack’s authorized payment flow. Ordyvia treats an order as paid only after server-side verification of the reference, status, expected amount and order relationship. A browser redirect alone is not proof of payment.

3. Failed or abandoned payments

A declined, closed or incomplete payment remains unpaid. Customers may cancel an eligible pending attempt to release reserved stock before trying again. Do not repeatedly open payment attempts or pay a seller outside checkout.

4. Duplicate or delayed confirmations

Payment callbacks and webhooks are processed with duplicate-effect protection. If a bank debit appears without an updated order, keep the payment reference and contact support rather than paying again.

5. Refunds

Approved refunds are recorded and require provider or operational reconciliation. Completion times depend on review and payment-provider or bank processing. Refund records do not automate seller payouts or transfers.

6. Customer payment safety

Ordyvia support and sellers must never ask you to disclose a password, full card number, CVV, PIN or OTP in messages, email, phone calls or support forms. Enter sensitive payment credentials only in the authorized payment interface.

7. Launch payment mode

At the date of this policy draft, Ordyvia’s launch acceptance configuration uses Paystack test mode. Public live-payment availability must not be claimed until live configuration has been separately approved and verified.