Card Issuing & Management

Create Card

This page explains the recommended flow for issuing a new card through Payblr APIs. The process includes retrieving available products, creating the card, storing the returned publicToken, and optionally configuring the PIN.

Updated 15 minutes ago

On this page

Overview

Card creation should follow a controlled sequence. Your system should first identify the correct product, submit the card creation request, and then store the returned card reference for future card management operations.

The publicToken returned by Payblr is an important identifier for future API calls related to the card.

Recommended flow

Use the following flow when issuing a new card through Payblr.

List Products

Identify the card products available for the client program before creating the card.

Create the card

Submit the required cardholder, product, and card issuance details through the card creation API.

Store the publicToken

Store the returned publicToken in your system. This value is used for future card-related operations.

Set Card PIN when applicable

If PIN setup is required for the card type or client flow, complete PIN configuration after card creation.

Create Card Sequence Diagram

Recommended card issuance sequence

User

Cardholder

System

Client System

Platform

Payblr APIs

1. Start card issuance

Cardholder starts the card creation flow in the client app.

CardholderClient System

2. List Products

Endpoint

List Products

Method

GET /program-manager/thr/products

Client system requests available card products.

Client SystemPayblr APIs

3. Return product options

Endpoint

List Products

Payblr returns the products available for the program.

Payblr APIsClient System

4. Create Card

Endpoint

Create Card

Method

POST /program-manager/thr/cards

Client system submits the card creation request.

Client SystemPayblr APIs

5. Return card reference

publicToken

Endpoint

Create Card

Payblr returns the created card reference and publicToken.

Payblr APIsClient System

6. Confirm card creation

Client system confirms the result to the cardholder.

Client SystemCardholder

7. Start PIN setup

Cardholder starts PIN setup when applicable.

CardholderClient System

8. Set Card PIN

Endpoint

Set Card PIN

Method

POST /program-manager/thr/card-pin/{publicToken}/pin

Client system configures the PIN when applicable.

Client SystemPayblr APIs

9. Return PIN setup result

Endpoint

Set Card PIN

Payblr returns the result of the optional PIN setup.

Payblr APIsClient System

10. Confirm PIN setup

Client system confirms the PIN setup result to the cardholder.

Client SystemCardholder

Sequence diagram showing how the cardholder, client system, and Payblr APIs participate in the card issuance flow. PIN setup is optional and depends on the card flow.

API sequence

The following API sequence should be used to understand the order of calls before reviewing endpoint-specific request and response details in API Explorer.

Order	API activity	Purpose	Output / next action
1	List Products	Identify which card products are available for the client program.	Select the appropriate product for card creation.
2	Create Card	Issue a new card using the selected product and required cardholder details.	Store the returned `publicToken`.
3	Set Card PIN	Complete PIN setup when applicable for the card type or client flow.	Continue with cardholder onboarding or card management operations.

Request patterns

GET /program-manager/thr/products
Authorization: Bearer [ACCESS_TOKEN]
Accept: application/json

POST /program-manager/thr/cards
Authorization: Bearer [ACCESS_TOKEN]
Content-Type: application/json

POST /program-manager/thr/card-pin/{publicToken}/pin
Authorization: Bearer [ACCESS_TOKEN]
Content-Type: application/json
publicToken: [PUBLIC_TOKEN]

Implementation notes

Before implementing card creation, confirm product availability, required request fields, and downstream storage requirements.

Confirm the correct product before submitting the card creation request.
Store the returned publicToken securely and associate it with the correct user or account record.
Do not rely on cardholder-visible card data as the primary identifier for future API calls.
Use the API Explorer to review endpoint-level request fields, response fields, and examples.

Validate required fields

Review the API Explorer before implementation to confirm required fields for the selected product and card type.

Log identifiers

Log the relevant request identifier and returned card reference so your team can troubleshoot card creation flows.

Next steps

After implementing card creation, continue with the card status, card detail update, secure card data, and renewal or replacement documentation as needed for your cardholder lifecycle.