# Cards

## Overview

The Cards module in the customer API provides essential functionalities related to the financial cards of the customers. It offers two primary endpoints that facilitate the retrieval of card balances and transaction histories.

Here is an overview of the endpoints available within the Cards module:

#### **Card Creation**

1. [**Review Customer Details for Card Creation**](/api-endpoints/cards/review-customer-details.md): Customers / managees that are **older than 6 months** are required to review and confirm that certain details are up to date. This endpoint will provide details for relevant endpoints
2. [**Upload Document**](/api-endpoints/cards/review-customer-details.md#upload-missing-document): This endpoint is used when clients need to upload missing documents in order to create a card.
3. [**Create Customer Card**](/api-endpoints/cards/create-card.md#create-customer-card)**:** Enables users to create a new card for a customer. This is usually the first step in providing a customer with transactional capabilities.

#### **Card Management**

1. [**Activate Card**](/api-endpoints/cards/activation-deactivation.md#post-api-v1-customer-cards-activate): Used to activate a card for use, this endpoint should only be used once the physical / virtual card is intended to be used.
2. [**Deactivate Card**](/api-endpoints/cards/activation-deactivation.md#post-api-v1-customer-cards-deactivate): Used to deactivate a card, in cases where a card is lost or stolen. Cards may be reactivated at a later date.
3. [**Change Card PIN**](/api-endpoints/cards/change-card-pin.md) **-** A `POST` request where users can change the pin of an existing card

**Card Analytics**

1. [**Get Customer Cards By Customer:**](/api-endpoints/cards/get-customer-cards.md#get-cards-by-customer) Retrieves a list of all cards issued under the customer's account, offering a consolidated view of the card inventory.
2. [**Get Card Details by ID**](/api-endpoints/cards/get-card-details-by-id.md#get-card-details-by-id): Retrieves details of a single card, including relevant account details.
3. [**Get Sensitive Card Details by ID**](/api-endpoints/cards/get-card-details-by-id.md#get-sensitive-card-details-by-id): Retrieves sensitive card details of a single card by its ID.
4. [**Get Card Balances**](/api-endpoints/cards/list-card-balances-and-transactions.md#get-card-balances) **-** This `GET` endpoint allows users to retrieve a list of all the cards available on the customer's account, providing details such as card ID, currency, total balance, available balance, and the status of any pending transactions. Users can also obtain information on whether a card is currently enabled or disabled.
5. [**Get Card Transactions**](/api-endpoints/cards/list-card-balances-and-transactions.md#get-transactions) **-** A `GET` request where users can access a detailed list of transactions for a specific card over a defined time period. This endpoint supplies information like transaction ID, card ID, amount, currency, description, transaction date and time, as well as the pending status of the transaction. It is crucial for customers who need to track their spending or review their transaction history for accounting or budgeting purposes.

#### **Money Movement**

1. [**Add Funds to a Card**](/api-endpoints/cards/card-transfers.md#card-transfer-funds): Facilitates moving of funds between a customer asset account and a card.
2. [**Move Funds Between Cards**](/api-endpoints/cards/card-transfers.md#card-to-card-transfer): Facilitates movement of funds between two different cards.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://customer-api-docs.ibanera.com/api-endpoints/cards.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.