v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB

Bulletin

Register card with Protection Bulletin

The Protection Bulletin is used before a transaction takes place in cases where the issuer is temporarily offline and unable to authorize or decline a transaction. In a process known as stand-in, the card network authorizes or declines the transaction to avoid creating problems for the cardholder and merchant, based on how the card was added to the Protection Bulletin. Once the issuer is back online, the card network lets them know what was authorized or declined while they were down.

You can add a card to the Protection Bulletin with this endpoint or setting a card rule so that when a card's status changes to a rule's configured status, the card is automatically added to the Protection Bulletin.

For more information, refer to 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.

post/v1/bulletin

Headers

Authorizationstring required

Example:Bearer eyJhbGci...IUzUx

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.

x-customer-idnumber required

Pismo customer ID. Must be associated with account whose ID is embedded in the access token.

Request body

Example request

{
  "card_id": 6743052
}

Response

Created

card_idinteger

Enrolled card ID

org_idstring

Organization ID

program_idnumber

Pismo program ID.

network_brand_type'ELO' | 'MASTERCARD' | 'VISA'

Card network brand.

created_atstring date-time

Datetime program calendar strategy was created. Format = YYYY-MM-DDTHH:MM:SS:MM.

updated_atstring date-time

Datetime program calendar strategy was updated. Format = YYYY-MM-DDTHH:MM:SS:MM

network_track_numberstring

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_datestring yyyy-mm-dd

Date when the card will be removed from the Protection Bulletin in the network brand. Format = yyyy-mm-dd.

was_automatically_purgedboolean

Was card removed from the network brand on the purge date?

card_track_numbernumber

Pismo card track number.

region_codestring[]

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

Example response

{
  "card_id": 6743052,
  "org_id": "TN-cc8f8b89-233a-4582-9f36-63ee85278d6d",
  "program_id": 1010,
  "network_brand_type": "ELO",
  "created_at": "2024-09-12T16:46:16.43663522",
  "updated_at": "2024-09-12T16:46:16.43663522",
  "network_track_number": "TN-123XXX-XXXXXX-XXXXXXX::1a2b3c",
  "state": "BLOCKED",
  "status": "PENDING",
  "purge_date": "2025-04-22",
  "was_automatically_purged": true,
  "card_track_number": 1,
  "histories": [
    {
      "event": "POST",
      "event_date": "2025-04-22 20:31:50",
      "status": "PENDING",
      "reason": "L",
      "network_track_number": "TN-123XXX-XXXXXX-XXXXXXX::1a2b3c",
      "was_automatically_purged": true,
      "card_track_number": 1,
      "network_response_data": "{\"status\":\"SUCCESS\",\"message\":\"Card added to Protection Bulletin\"}"
    }
  ]
}