Declared Stock cancellation flow guide

Example: Cancellation after provision

1. Order is placed, RESERVATION callback sent from Eneba
2. Payment is successful, PROVISION callback sent from Eneba
3. Order fails (e.g. another merchant failed to provision) - CANCELLATION callback sent from Eneba
   • If you registered a Cancellation API Callback via P_registerCallback and respond 200 to our CANCELLATION callback the key is deleted and never returns to Eneba stock
   • If no Cancellation API Callback is registered or respond 500 to our CANCELLATION callback the key returns to Eneba stock

Example: Cancellation before provision

1. Order is placed - RESERVATION callback sent from Eneba
2. Order is cancelled - CANCELLATION callback sent from Eneba, example reason: payment declined

Example: Buyer returns undisplayed keys

1. Order is placed, and correctly fulfilled, customer received their keys
2. Customer returns the undisplayed keys and receives a refund
3. Keys are returned to Eneba stock ready to be sold again. No CANCELLATION callback sent from Eneba