Skip to main content
GET
Get Card Status

Overview

Retrieves comprehensive information about the authenticated user’s card, including its current status, holder details, expiry date, and card type. This endpoint is essential for checking card availability and displaying card information in your application.
This endpoint returns basic card information only. Sensitive details like the full PAN, CVV, and PIN are never exposed through this endpoint. Use the secure token-based endpoints for accessing sensitive information.

Authentication

This endpoint requires authentication via Bearer token:

Request

Headers

string
required
Your public API client key
boolean
default:false
Set to true to route requests to the US backend environment
string
required
Bearer token for authentication

Request Example

Response

Success Response

string
Unique identifier for the card
string
Cardholder name as it appears on the card (uppercase)
string
Card expiry date in YYYY/MM format
string
Last 4 digits of the card PAN (Primary Account Number)
string
Current card statusPossible Values:
  • ACTIVE - Card is active and can be used for transactions
  • FROZEN - Card is temporarily frozen by the user
  • BLOCKED - Card is permanently blocked (requires replacement)
string
Type of cardPossible Values:
  • VIRTUAL - Digital card for online/mobile payments
  • PHYSICAL - Physical plastic card
  • METAL - Premium metal card
string
ISO 8601 timestamp when the card was ordered

Error Responses

Card Status Explained

Meaning: Card is fully functional and can process transactionsUser Actions Available:
  • Make purchases online and in-store
  • View card details and PIN
  • Freeze the card temporarily
  • View transaction history
Next Steps: User can begin using the card for payments
Meaning: Card is temporarily disabled by the userTransaction Behavior: All transaction attempts will be declinedUser Actions Available:
  • Unfreeze the card to restore functionality
  • View card details (but cannot use for purchases)
  • View transaction history
Common Use Cases:
  • Suspected fraudulent activity
  • Lost card (temporary measure before reporting)
  • User wants to temporarily prevent spending
Recovery: Call POST /v1/card/unfreeze to restore card to ACTIVE status
Meaning: Card is permanently disabled and cannot be reactivatedTransaction Behavior: All transaction attempts will be declinedUser Actions Available:
  • View historical transaction data only
  • Order a replacement card
Common Causes:
  • Card reported as lost or stolen
  • Security concerns or fraud detected
  • Card compromised
  • Multiple failed PIN attempts
Recovery: Cannot unfreeze a BLOCKED card. User must order a new card via POST /v1/card/order

Common Use Cases

Check if User Has a Card

Display Card Summary

Monitor Card After Ordering

Check if Card Can Process Transactions

Edge Cases and Important Notes

404 Not Found ResponseA 404 error means the user has not ordered a card yet. Handle this gracefully by prompting the user to order a card via POST /v1/card/order.
Security Best PracticeThis endpoint intentionally returns only the last 4 digits of the PAN. Never attempt to reconstruct or store the full card number. Use POST /v1/card/details/token to securely display full card details in a PCI-compliant hosted environment.
Polling FrequencyIf polling for card status after ordering, use exponential backoff or a reasonable delay (2-5 seconds) between requests to avoid rate limiting.

Implementation Best Practices

Error Handling

UI Display Logic

  • POST /v1/card/order - Order a new card
  • POST /v1/card/details/token - Generate token to view sensitive card details
  • POST /v1/card/freeze - Temporarily freeze the card
  • POST /v1/card/unfreeze - Unfreeze a frozen card
  • GET /v1/card/transactions - View card transaction history
  • POST /v1/card/pin/token - Generate token to view card PIN