Cancelling Orders

Cancelling A Single Order

1. Display maker's orders (listings and/or offers).
2. Maker selects an order to cancel.
3. If standard order, maker confirms transaction for revokeSingleNonce (when order type is fill or kill) or revokeOrderDigest (when order type is partially fillable). Revoking a single nonce or order digest requires calldata to be encoded with PaymentProcessorEncoder.
4. If co-signed order flag order as cancelled in DB and do not allow co-signing service to co-sign the order if requested. Order should be hidden from future listing/offer queries.

Cancelling All Outstanding Standard Orders

1. If the maker chooses to cancel ALL outstanding standard listings and offers they have made, the maker simply needs to confirm a revokeMasterNonce transaction. This will cancel/invalidate all prior orders that were signed using their previous master nonce. revokeMasterNonce has no calldata requirements and may be called directly by a maker without using PaymentProcessorEncoder.

Cancelling All Outstanding Co-Signed Orders

1. The marketplace should flag all outstanding orders for the user as cancelled in their database. The co-signing service should not return co-signatures for any of the cancelled orders, and the orders should be hidden from all future queries.

Cancelling a Single Permit Order

1. Display maker's permit orders (listings and/or offers).
2. Maker selects an order to cancel.
3. Maker confirms transaction for invalidateUnorderedNonce (when the order type is fill or kill) or closePermittedOrder (when the order type is partially fillable). Note: These operations are executed on Permit-C, not Payment Processor, as that is where permit nonces and permitted partially fillable orders are tracked.
4. If co-signed order flag order as cancelled in DB and do not allow co-signing service to co-sign the order if requested. Order should be hidden from future listing/offer queries.

Cancelling ALL Outstanding Permit Orders

1. If the maker chooses to cancel ALL outstanding permit orders, the maker simply needs to confirm a lockdown transaction on the permit processor. This will cancel/invalidate all permits, including permits unrelated to Payment Processor.