Transaction and order are separate
Support still needs to search multiple systems after receiving a screenshot or hash.
See amount due, amount paid, asset, network and status in one place.
Know when to fulfill, activate service or keep waiting.
Support still needs to search multiple systems after receiving a screenshot or hash.
Actual received value may differ slightly or arrive across several transactions.
Payments across assets and networks need a shared completion state.
Connect orders and payments so every record is searchable, clear and traceable.
Match every payment to a specific order and view the amount, asset and payment record together.
Expected amount, received amount and payment status stay up to date, even across multiple payments.
Filter by order number, status, time and other criteria to quickly find records that need attention.

Clear status at every step reduces repeated checks.
Set the amount, assets, networks and payment rules.
Scan, copy the address or connect a wallet.
Update completion ratio from received value and configured minimum.
Ship, activate service or let a Webhook continue the workflow.
Underpayments, multiple payments and delayed confirmations keep a clear status and full record.
When the payment amount does not meet the minimum requirement, the order remains partially paid to prevent incorrect confirmation.
When the asset, network or amount does not match the order, the exception status is preserved.
Multiple valid payments for the same order are recorded cumulatively and payment progress continues to update.