POST /management/wire/disable

This request will be used to disable the use of the given wire method. We use POST instead of DELETE because the exchange will retain state about the wire method (specifically the end date) to prevent replay attacks abusing the WireSetupRequest. Also, DELETE would not support a body, which is needed to provide the signature authorizing the operation.

Request:

The request must be a WireTeardownRequest.

Response:

204 No content:

The auditor has successfully disabled the wire method. The body is empty.

403 Forbidden:

The signature is invalid. Returned with an error code of TALER_EC_EXCHANGE_MANAGEMENT_WIRE_DEL_SIGNATURE_INVALID.

404 Not found:

The wire method is unknown to the exchange. Returned with an error code of TALER_EC_EXCHANGE_MANAGEMENT_WIRE_NOT_FOUND.

409 Conflict:

The exchange has a more recent request related to this wire method (replay detected). Returned with an error code of TALER_EC_EXCHANGE_MANAGEMENT_WIRE_MORE_RECENT_PRESENT.

413 Request entity too large:

The uploaded body is to long, it exceeds the size limit. Returned with an error code of TALER_EC_GENERIC_UPLOAD_EXCEEDS_LIMIT.

500 Internal Server Error:

The server experienced an internal error. This response comes with a standard ErrorDetail response. Possible error codes include TALER_EC_GENERIC_DB_FETCH_FAILED or TALER_EC_GENERIC_DB_STORE_FAILED.

Details:

interface WireTeardownRequest {

  // Full payto:// URL identifying the account and wire method
  payto_uri: string;

  // Signature using the exchange's offline key over a
  // TALER_MasterDelWirePS.
  // with purpose TALER_SIGNATURE_MASTER_WIRE_DEL.
  master_sig_del: EddsaSignature;

  // Should be the time when the signature was created,
  // using the (monotonic!) local time of the system
  // with the offline master public key.  Note that
  // even if the time is in the future, the wire method will
  // become inactive immediately! Used ONLY to detect replay attacks.
  validity_end: Timestamp;

}