Manual Confirmation Acceptance

Overview

Manual Confirmation Acceptance lets an operator decide that a payment is acceptable despite an unresolved or exceptional automatic state. OxaPay includes a manual_accept payment status for invoices manually accepted by the merchant.

The operator should review network, asset, destination, Paid Amount, transaction status, conflict evidence, and customer context. A screenshot or unverified explorer link is not sufficient.

Manual acceptance differs from Confirmation Override. An override changes a threshold or rule, while manual acceptance directly changes the business payment outcome for the reviewed case.

Downstream actions such as balance credit, fulfillment, accounting, and notification must remain idempotent. Later automatic confirmation should not trigger a second credit.

The audit record should include operator, time, reason, evidence, prior state, resulting state, and any financial variance. Frequent manual acceptance should trigger review of matching, confirmation, or support processes.

Manual review should use a checklist and dual approval for high-value cases. The operator needs the canonical transaction, provider status, asset and network, amount variance, customer claim, and downstream order state. The interface should preview every resulting financial action before acceptance and require an explicit acknowledgment of residual risk.

Manual acceptance should be reversible only through an explicit correction or refund workflow. Allowing operators to toggle the status repeatedly can create conflicting ledger entries, customer notifications, and fulfillment actions.

The review interface should calculate the exact financial consequence, including shortfall or excess, before the operator commits the decision.

For especially sensitive cases, a second reviewer can verify the evidence and the resulting ledger impact before release. The system should also notify the original case owner if later blockchain evidence conflicts with the manual decision.