---
title: "Delete card from Protection Bulletin"
method: DELETE
path: "/v1/bulletin/{card_id}"
tags: ["Bulletin"]
---

# Delete card from Protection Bulletin

`DELETE /v1/bulletin/{card_id}`

Remove a Pismo-issued card from the Protection Bulletin.

**Note:** This endpoint takes an account token - an access token encoded with a Pismo account ID. Tokens can expire quickly, which can result in a <b>401 Unauthorized</b> message.

## Path parameters

- `card_id` number, required

## Headers

- `Authorization` string, required

## Response `201`

Created

- BulletinResponseModel — Response model for the Bulletin API.
  - `card_id` integer — Enrolled card ID
  - `org_id` string — Organization ID
  - `program_id` number — Pismo program ID.
  - `network_brand_type` 'ELO' | 'MASTERCARD' | 'VISA' — Card network brand.
  - `created_at` string, date-time — Datetime program calendar strategy was created. Format = YYYY-MM-DDTHH:MM:SS:MM.
  - `updated_at` string, date-time — Datetime program calendar strategy was updated. Format = YYYY-MM-DDTHH:MM:SS:MM
  - `network_track_number` string — Created in the internal system to track the card's event history. This is a combination between the tenant and the truncated random uuid.
  - `state` '' | 'BLOCKED' | 'UNBLOCKED' — Is card blocked or not in the network brand? When the state is empty, it means the network brand did not successfully receive any action.
  - `status` 'PENDING' | 'PROCESSING' | 'CANCELLED' | 'SETTLED' | 'PROCESSED' — PENDING: Charge is scheduled and waiting for the cycle to close. PROCESSING: Cycle closing process has started and is awaiting completion. CANCELLED: Charge canceled due to link cancellation. SETTLED: Amount is zero and/or `minimum_spend_to_charge` has not been reached. PROCESSED: Charge was posted on the statement."
  - `purge_date` string, yyyy-mm-dd — Date when the card will be removed from the Protection Bulletin in the network brand. Format = yyyy-mm-dd.
  - `was_automatically_purged` boolean — Was card removed from the network brand on the purge date?
  - `card_track_number` number — Pismo card track number.
  - `region_code` string[] — Region code contains one or more Account Screen Authorization File (ASAF) region codes that define the distribution of a Visa cardholder account number in Card Recovery Bulletin Service files. **REQUIRED** for Visa. `0` - No Bulletin / V.I.P. Only (cannot be combined with other region codes) `A` - All Asia-Pacific region countries `B` - All Central Europe, Middle East, and Africa (CEMEA) region countries. `C` - All Visa Canada `D` - National Card Recovery Bulletin `E` - All European countries `F` - All Latin America and Caribbean (LAC) region countries Region codes can be in any order, except no other region code can be specified in combination with region code 0. Visa documentation: VisaNet Authorization-Only Online Messages – Technical Specifications - Table 215: Field 127E.2 Account Screen Authorization File (ASAF) Region Codes
  - `histories` object[] — Response history model for the Bulletin API.
    - `event` 'POST' | 'UPDATE' | 'DELETE' — Event performed in the request
    - `event_date` string, yyyy-mm-dd hh:mm:ss — Date and time when the event was received in the Protection Bulletin.
    - `status` 'PENDING' | 'PROCESSING' | 'CANCELLED' | 'SETTLED' | 'PROCESSED' — PENDING: Charge is scheduled and waiting for the cycle to close. PROCESSING: Cycle closing process has started and is awaiting completion. CANCELLED: Charge canceled due to link cancellation. SETTLED: Amount is zero and/or `minimum_spend_to_charge` has not been reached. PROCESSED: Charge was posted on the statement."
    - `reason` string — Reason that indicates why the card was added to the Protection Bulletin.
    - `network_track_number` string — Created in the internal system to track the card's event history. This is a combination between the tenant and the truncated random uuid.
    - `was_automatically_purged` boolean — Was card removed from the network brand on the purge date?
    - `card_track_number` number — Pismo card track number.
    - `network_response_data` string — Response JSON data received from the network brand. The content of this field will indicate the original response from the network brand, whether success or failure. The example provided in this model is for illustrative purposes only.
    - `region_code` string[] — Region code contains one or more Account Screen Authorization File (ASAF) region codes that define the distribution of a Visa cardholder account number in Card Recovery Bulletin Service files. **REQUIRED** for Visa. `0` - No Bulletin / V.I.P. Only (cannot be combined with other region codes) `A` - All Asia-Pacific region countries `B` - All Central Europe, Middle East, and Africa (CEMEA) region countries. `C` - All Visa Canada `D` - National Card Recovery Bulletin `E` - All European countries `F` - All Latin America and Caribbean (LAC) region countries Region codes can be in any order, except no other region code can be specified in combination with region code 0. Visa documentation: VisaNet Authorization-Only Online Messages – Technical Specifications - Table 215: Field 127E.2 Account Screen Authorization File (ASAF) Region Codes

## Other responses

- `400` — Bad Request
- `401` — Unauthorized
- `404` — Not Found
- `422` — Unprocessable Entity
- `500` — Internal Server Error
- `504` — Gateway Timeout

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/versions/935b62e16de4/schema)