# Card issuing - Cards This table lists the cards endpoints and the events they generate. For information on setting up event notifications, see the [Data and reporting overview](https://developers.pismo.io/pismo-docs/docs/data-reporting-overview).
Endpoint Event
**Cards API**
[Create card](https://developers.pismo.io/pismo-docs/reference/post-v2-card) [Card created](https://developers.pismo.io/events/docs/cards-create-1)
[Associate noname card with customer](https://developers.pismo.io/pismo-docs/reference/post-v2-card-bind) [Customer bound to noname card](https://developers.pismo.io/events/docs/cards-bind-card-1)
[Update card information](https://developers.pismo.io/pismo-docs/reference/patch-v2-card) [Card updated](https://developers.pismo.io/events/docs/cards-update-1)
[Update card status](https://developers.pismo.io/pismo-docs/reference/put-v1-card-status) [Card updated](https://developers.pismo.io/events/docs/cards-update-1)
[Reissue physical card](https://developers.pismo.io/pismo-docs/reference/post-v1-card-reissue) [Card updated](https://developers.pismo.io/events/docs/cards-update-1) (old card)\ [Card created](https://developers.pismo.io/events/docs/cards-create-1) (new card)
[Activate physical card](https://developers.pismo.io/pismo-docs/reference/put-v1-card-activate) [Card updated](https://developers.pismo.io/events/docs/cards-update-1)
[Change card password](https://developers.pismo.io/pismo-docs/reference/put-v2-card-password) [Card password changed](https://developers.pismo.io/events/docs/cards-update-password-1)
[Reset password try count](https://developers.pismo.io/pismo-docs/reference/post-v2-card-password-reset) [Card updated](https://developers.pismo.io/events/docs/cards-update-1)
[Rotate virtual card CVV](https://developers.pismo.io/pismo-docs/reference/post-v2-reset-cvv) [Card CVV updated](https://developers.pismo.io/events/docs/cards-rotate-cvv-1)
[Start noname card bulk process](https://developers.pismo.io/pismo-docs/reference/start-bulk) [Card created](https://developers.pismo.io/events/docs/cards-update-1)\ [Card can be added to next scheduled embossing](https://developers.pismo.io/events/docs/cards-embossing-card-ingress-1)\ [Card embossing notification received](https://developers.pismo.io/events/docs/cards-embossing-1)\ [Embossing rejection file processed](https://developers.pismo.io/events/docs/cards-card-rejection-1)\ [Embossing summary received](https://developers.pismo.io/events/docs/cards-embossing-summary-1) See [Embossing events](https://developers.pismo.io/pismo-docs/docs/physical-card-embossing#embossing-events) for more information.
[Update PIN from PINBlock](https://developers.pismo.io/pismo-docs/reference/put-v1-update-pin-from-pinblock) [Card password changed](https://developers.pismo.io/events/docs/cards-update-password-1)
Append issuer script [Card issuer script notification received](https://developers.pismo.io/events/docs/cards-issuer-script-1)
[Append update PIN script](https://developers.pismo.io/pismo-docs/reference/post-v1-append-update-pin-script) [Card issuer script notification received](https://developers.pismo.io/events/docs/cards-issuer-script-1)\ [Card password updated](https://developers.pismo.io/events/docs/cards-update-password-1) - When script executes
[Automatic Billing Update](https://developers.pismo.io/pismo-docs/docs/cards-overview-1#mastercards-automatic-billing-updater-option) file sent to Mastercard [ABU notification file sent](https://developers.pismo.io/events/docs/cards-automatic-updater-1)
**Cards on file API**
[Create card on file](https://developers.pismo.io/pismo-docs/reference/create-a-cardsonfile-v3) [Card on file created](https://developers.pismo.io/events/docs/cardsonfile-provision-1)\ [Card on file validation result received](https://developers.pismo.io/events/docs/cardsonfile-verification-1)\ [Card excluded](https://developers.pismo.io/events/docs/cardsonfile-exclusion-1)
[Update card on file](https://developers.pismo.io/pismo-docs/reference/updates-a-cardsonfile) [Card on file updated](https://developers.pismo.io/events/docs/cardsonfile-patch-cards-1)\ If the card status is being changed to `SUSPENDED`, it also generates an [Card excluded](https://developers.pismo.io/events/docs/cardsonfile-exclusion-1) event
[Create card validation](https://developers.pismo.io/pismo-docs/reference/create-a-new-validation-for-a-given-card) [Card on file validation result received](https://developers.pismo.io/events/docs/cardsonfile-verification-1) If validation fails, an [Card excluded](https://developers.pismo.io/events/docs/cardsonfile-exclusion-1) event is generated.
[Submit validation try](https://developers.pismo.io/pismo-docs/reference/create-a-new-validation-for-a-given-card) [Card on file validation result received](https://developers.pismo.io/events/docs/cardsonfile-verification-1) event with `PENDING` status. If the verification/validation fails, an [Card excluded](https://developers.pismo.io/events/docs/cardsonfile-exclusion-1) event is generated and the card is deleted from the customer's wallet.
**Card tokenization API** None directly via endpoints, though the tokenization process itself generates a number of events:\ [Token provisioning response received](https://developers.pismo.io/events/docs/cards-tokenization-notification-1)\ [Token provisioning rejected](https://developers.pismo.io/events/docs/cards-tokenization-notification-refusal-1)\ [Tokenization challenge sent](https://developers.pismo.io/events/docs/cards-tokenization-send-challenge-1) See [Card tokenization flow and events](https://developers.pismo.io/pismo-docs/docs/card-tokenization-flow-and-events) for more information.