v1

latestOpenAPI 3.1.0Copyright Pismo2026-07-247702,7523.1 MB

Noname

Increment noname card bulk

Increment noname card bulk/batch with up to 1000 additional cards. Use the bulk ID returned from Create noname card bulk.

One card is created for each external_id entered.

put/cards/v1/bulks/{bulkID}

Path parameters

bulkIDstring required

Bulk ID returned from /cards/v1/bulks (Create noname card bulk) endpoint

Request body

external_idsstring[] required

Client assigned IDs for internal tracking purposes. One card is created for each ID. The maximum number of cards in one bulk/batch is 1000.

If you want to use more than 36 characters for your external IDs, please request a change in the embossing layout via a Jira ticket. By default, an embossing layout supports 36 digits for external IDs.

Example request

{
  "external_ids": [
    "8675309",
    "586038",
    "585603"
  ]
}

Response

Bulk was incremented

abu_enabledboolean

This field is DEPRECATED. For more information, refer to the ABU documentation in the Cards overview guide.

When a card is created or reissued, or its account credentials change, Mastercard is notified if this feaure is enabled. Notification updates are sent to Mastercard on a daily basis.

For more information, refer to Mastercard's <a href="https://developer.mastercard.com/product/automatic-billing-updater-abu/" target="_blank">ABU</a> documentation.

contactless_enabledboolean

For physical cards. Is card enabled for contactless transactions?

With contactless transactions, you hold or tap the card on contactless-enabled card reader to complete a transaction. This requires that both the card and the terminal have Near Field Communication (NFC) technology. Most embossers can create plastic contactless cards.

Default is true.

embossing_custom_fieldstring

For physical cards. Additional information for embossing company. For example: tracking number or whether the card should be plastic or metal.

You can use this field for any embossing needs specific to your business. Whatever is sent must be agreed upon with the embosser—what to send, what values to send, what format to send, what size to send for each value, and so on.

idstring

Bulk ID.

metadatastring

Any data object with key/value pairs. No limit on length.

Note: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to Get started with Pismo APIs.

program_idnumber

Pismo program ID.

template_idstring

Template ID. Templates are used to implement the BIN override feature. For more information, refer to the BIN override guide.

sizeinteger

Bulk size - number of cards

status'CREATED' | 'RUNNING' | 'COMPLETED'

Bulk noname card job status.

validity_period_hoursinteger

How long, in hours, the card is valid. Cannot exceed the card's expiration_date. Once this period is exceeded, and the card has a NORMAL, BLOCKED, PENDING, WARNING or REISSUED status, its status becomes INOPERATIVE.

This field is used to calculate the datetime value for valid_until.

For VIRTUAL and PLASTIC cards. Setting this field for TEMPORARY or RECURRING cards returns a 400 Bad request error.

Example response

{
  "id": "3e8d9c51-64c7-420d-ae53-87e2b76cf45e",
  "program_id": 8519,
  "template_id": "EAFA693A-57B2-4029-97F3-D20D6F06D79B",
  "embossing_custom_field": "Please make cards metal, not plastic",
  "contactless_enabled": false,
  "abu_enabled": false,
  "metadata": {
    "trackingID": 345660
  },
  "status": "CREATED",
  "size": 2
}