Card Issuing & Management

CVV & PIN Status Management

This page explains how your system can retrieve CVV and PIN status information and perform unblock operations when supported. These flows are used after card issuance and help your system support sensitive card operations in a controlled way while keeping the cardholder experience within your own digital channels.

Updated 15 minutes ago

On this page

Overview

CVV and PIN status management allows your system to support sensitive card operations after the card has been issued. These flows should be handled carefully because they relate to cardholder security and card usage controls.

Your system can retrieve the applicable status information and, when supported, perform unblock operations. Show the status or unblock result to the cardholder after the operation completes.

Recommended flow

Use the following flow when retrieving CVV or PIN status information or performing supported unblock operations.

Identify the card

Use the stored card reference to identify the card that requires CVV or PIN status review.

Get Card CVV Status or Get Card PIN Status

Request the current CVV status or PIN status from the matching Payblr operation.

Unblock Card CVV or Unblock Card PIN

Submit the matching unblock operation only when supported by the card flow and business rules.

Display result

Show the status or unblock result to the cardholder in the client app.

CVV & PIN Status Management Sequence Diagram

Recommended CVV and PIN status sequence

User

Cardholder

System

Client System

Platform

Payblr APIs

1. Request CVV or PIN status

Cardholder requests CVV or PIN status information in the client app.

CardholderClient System

2. Get Card CVV Status

Sensitive operation

Endpoint

Get Card CVV Status

Method

GET /program-manager/thr/card-cvv/{publicToken}/cvv/status

Client system requests CVV status when the cardholder flow needs CVV state.

Client SystemPayblr APIs

3. Return CVV status

Endpoint

Get Card CVV Status

Payblr returns the current CVV status information.

Payblr APIsClient System

4. Get Card PIN Status

Sensitive operation

Endpoint

Get Card PIN Status

Method

GET /program-manager/thr/card-pin/{publicToken}/pin/status

Client system requests PIN status when the cardholder flow needs PIN state.

Client SystemPayblr APIs

5. Return PIN status

Endpoint

Get Card PIN Status

Payblr returns the current PIN status information.

Payblr APIsClient System

6. Request unblock

Cardholder requests an unblock action when supported.

CardholderClient System

7. Unblock Card CVV

Sensitive operation

Endpoint

Unblock Card CVV

Method

PUT /program-manager/thr/card-cvv/{publicToken}/cvv/status

Client system submits Unblock Card CVV when CVV unblock is supported.

Client SystemPayblr APIs

8. Return CVV unblock result

Endpoint

Unblock Card CVV

Payblr returns the result of Unblock Card CVV.

Payblr APIsClient System

9. Unblock Card PIN

Sensitive operation

Endpoint

Unblock Card PIN

Method

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

Client system submits Unblock Card PIN when PIN unblock is supported.

Client SystemPayblr APIs

10. Return PIN unblock result

Endpoint

Unblock Card PIN

Payblr returns the result of Unblock Card PIN.

Payblr APIsClient System

11. Display result

Client system displays the status or unblock result to the cardholder.

Client SystemCardholder

Sequence diagram showing how the cardholder, client system, and Payblr APIs participate in CVV and PIN status management flows. Unblock operations are optional and depend on supported card behavior.

API sequence

The following sequence summarizes the API activities involved in CVV and PIN status management.

Order	API activity	Purpose	Output / next action
1	Get Card CVV Status / Get Card PIN Status	Retrieve current CVV or PIN status information for the card.	Display the status or determine whether an unblock flow is needed.
2	Unblock Card CVV / Unblock Card PIN	Call the matching unblock operation when supported by the card flow.	Display the status or unblock result to the cardholder.

Request patterns

GET /program-manager/thr/card-cvv/{publicToken}/cvv/status
Authorization: Bearer [ACCESS_TOKEN]
Accept: application/json

GET /program-manager/thr/card-pin/{publicToken}/pin/status
Authorization: Bearer [ACCESS_TOKEN]
Accept: application/json

PUT /program-manager/thr/card-cvv/{publicToken}/cvv/status
Authorization: Bearer [ACCESS_TOKEN]
Content-Type: application/json

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

Implementation notes

Before implementing CVV and PIN status management, confirm which status and unblock operations are supported for the applicable card product and client program.

Use the stored card reference to identify the correct card before requesting CVV or PIN status information.
Only perform unblock operations when the operation is supported for the card product and client flow.
Do not expose sensitive card data in logs, screenshots, browser storage, or client-side code.
Log request identifiers, card references, operation type, response status, and timestamps for troubleshooting.

Protect sensitive operations

Treat CVV and PIN-related operations as sensitive. Keep the operation controlled, authenticated, and auditable.

Display clear results

Show the status or unblock result clearly to the cardholder after the operation completes.

Next steps

After implementing CVV and PIN status management, continue with secure card data and renewal or replacement documentation as needed for your cardholder lifecycle.