Insights on Crypto Payments, Infrastructure, and Operations

Payment Status and Exception Simulator

Payment Operations Tool

Payment Status and Exception Simulator

Model how a crypto payment moves from creation to payment, confirmation, fulfillment, underpayment, expiry, refund, or manual review. Test amount rules, timing, webhook delivery, and merchant-side order handling without using an API key or sending a real transaction.

9 documented statuses 15 operational presets Webhook retry modelling Runs entirely in your browser
Core principle

The payment gateway reports what happened to the payment. Your application decides what happens to the order. A reliable integration never fulfills from an unverified callback, never moves an order backward after a later event, and never treats an amount exception as a normal paid order without an explicit policy.

Before you begin This simulator applies documented payment rules to a fictional order.

It helps you understand likely status transitions and merchant actions. It does not create a payment, call an endpoint, validate a real transaction, or replace Payment Information.

RULE-BASED EDUCATIONAL MODEL
Simulation mode

Start with a simple business scenario or inspect every operational variable.

Ready-made scenarios Select one to load realistic values instantly.
Quick Simulation

Test a payment situation in seconds

Choose a scenario and adjust only the details most merchants need.

5 simple inputs
No technical setup required

The simulator fills the webhook, order-state, confirmation, and policy settings for you. Open Advanced Configuration to inspect or change them.

01 Choose and adjust
Simulation output

Expected status and merchant action

Results update when you run the scenario.

paid
Simple answer

Payment complete — the order can be delivered

The customer paid enough within the payment window.

Recommended action: fulfill the order once and record the payment.
Gateway status paid

Confirmed value satisfies the acceptance threshold.

Order decision Fulfill

The payment reached the required terminal state.

Amount classification Exact

Received amount equals the requested amount.

Delivery outcome Accepted

The callback is valid and the handler returns 200 with ok.

Threshold math

Amount decision

Minimum accepted: 99.00 USD
Received: 100.00 USD Difference: 0.00 USD
Event progression

Payment timeline

    Operational review

    Exceptions and controls

    Webhook model

    Delivery attempts and illustrative payload

    2 events

    Illustrative simulated payload — fields may differ from a live response.

    Implementation rule
    Reference

    Documented OxaPay payment statuses

    The simulator uses these names. Merchant-side order states remain your responsibility.

    new

    Invoice created; payment currency not selected.

    waiting

    Payment currency selected; waiting for payment.

    paying

    A payment attempt or transaction is being processed.

    paid

    The invoice has been fully paid.

    manual_accept

    The merchant manually accepted the invoice.

    欠薪

    A partial payment did not fully satisfy the invoice.

    refunding

    A refund has been initiated.

    refunded

    The payment has been refunded.

    expired

    The invoice was not paid within its lifetime.