Create noname card bulk

post

https://sandbox.pismolabs.io/cards/v1/bulks

Create up to 1000 noname cards per bulk/batch process. After calling this endpoint, call Start noname card bulk process to begin the bulk/batch card creation and embossing process.

Noname cards are batch-generated and not initially associated with customers, which occurs later. Noname cards work well for special use cases like gift cards or in countries or scenarios where a password or chip might be required but not necessarily a printed card name.

One card is created for each external_id entered.

For more information on embossing, refer to the Physical card embossing guide.

For detailed information about embossing flows, refer to Embossing flows.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Body Params

Create bulk request body

external_ids

array of strings

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.

external_ids*

program_id

integer

required

Pismo program ID

template_id

string

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

pin_length

integer

enum

Defaults to 4

PIN length - 4 or 6 digits. Default is 4.

Allowed:

abu_enabled

boolean

deprecated

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 ABU documentation.

contactless_enabled

boolean

Defaults to true

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_field

string

length ≤ 1000

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.

embossing_group

string

length between 2 and 32

Embossing group name. Clients can work with multi-embossers. You can use this field to notify an embosser about a card request. If this parameter is not passed, and you work with multi-embossers, the default embosser is used. For more information, refer to the Physical card embossing guide.

metadata

object

Any key-value object. Max length = 3200 bytes. This must be valid JSON data.

mode_type

string

enum

Mode type enum - SINGLE or COMBO. A combo card can have both a credit and debit mode, meaning it is associated with both a credit and debit program and account. A single card has one mode - credit or debit. Refer to the mode documentation in the Card overview guide for more information.

Allowed:

validity_period_hours

integer

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.

Responses

400

Bad Request

409

Specified resource status conflict with current request

500

Internal server error

Create noname card bulk

Changelog

Support

Pismo is here to help

201Bulk created successfully