Retrieves card details if the card exists and belongs to a verified user.
Usage Notes:
Depending on the card’s current state, further actions may be required:
card_images_required: The cardholder must upload both front and back images before the card can be used for any transactions.withdrawal_confirm_required: A withdrawal setup or confirmation step must be completed before withdrawals are allowed.payment_confirm_required: Additional registration or verification is required before new payments can be made with this card.is_limited: The user has reached their daily payment limit.
→ Note: When is_limited is true, no new payments can be made today using this card, but withdrawals are still permitted.If any of the first three flags (card_images_required, withdrawal_confirm_required, or payment_confirm_required) are set to true, the card must be updated before it can be fully used.
→ Use the Update Card Endpoint to complete the necessary steps.
Unique platform identifier (UUID). You receive this during onboarding. Must be sent with every API request.
HMAC-SHA256 request signature for authentication. Use your platform secret key to compute it as: METHOD + PATH + QUERY + BODY_HASH.
Unique identifier (UUID) of the card to be retrieved.
Successful Response
Indicates whether the request was processed successfully.
true
A short, human-readable message describing the result of the request.
"Operation completed."
The main response payload, if applicable
The Unix timestamp (in seconds) indicating when the response was generated.
1718006400