Associate noname card with customer

Bind an account and customer to a noname card, which changes its status to CREATED. The card is then treated as a normal physical plastic or metal card.

You have to pass this endpoint a noname card's ID. Card IDs are generated when the Start noname card bulk process endpoint is called. This endpoint generates an event for each card - Card created - with event data that includes the card ID, bulk ID, and external ID. Refer to the Data and reporting guide for information on events and setting up event notifications.

The bind operation is completed asynchronously and generates a Customer bound to noname card event. Make sure the operation has completed and the event generated before attempting to access or use the associated card.

Card reissuing

  • You can use this endpoint to reissue a card—replacing the card to be reissued with a noname card, which is then treated as a normal physical card. If a card to be replaced is entered (reissued_card_id), the Card updated event is also generated.

  • If you attempt to reissue a card to a card that has already been associated, meaning it is no longer a noname card and no longer has an UNBOUND status, you will get a 409 Conflict error.

Note: This endpoint requires an account token - an access token encoded with a Pismo account ID.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Pismo card ID

Body Params
integer

Last issued card ID

Headers
string
required

Account ID

integer
required

Pismo customer ID

Responses
202

Your request was accepted. The bind operation is made asynchronously, check the event Customer bound to noname card.

400

Bad Request

401

Access token is missing or invalid

403

You don't have permission to access this resource

409

Specified resource status conflict with current request

500

Internal server error

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here!