# RevCent MCP Guide: `EnableCustomerCard`

AI/MCP-focused guide for enabling a RevCent Customer Card.

---

## Related Documentation

| Guide | Link | Why It Matters |
|---|---|---|
| Customer Card Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewCustomerCard.md` | Required overview for understanding Customer Cards, safe card summaries, default payment method behavior, and Customer Card lifecycle. |
| Customer Overview | `https://revcent.com/documentation/markdown/mcp/operation/OverviewCustomer.md` | Explains Customers and how Customer Cards attach to Customer records. |
| GetCustomer | `https://revcent.com/documentation/markdown/mcp/operation/GetCustomer.md` | Retrieve the Customer connected to the card. |
| AddCardToCustomer | `https://revcent.com/documentation/markdown/mcp/operation/AddCardToCustomer.md` | Add a new card to an existing Customer. |
| BigQueryRunQuery | `https://revcent.com/documentation/markdown/mcp/operation/BigQueryRunQuery.md` | Correct operation for reporting, metrics, aggregation, and data mining. |


---

## Operation Summary

Operation:

```text
EnableCustomerCard
```

Title:

```text
Enable A Customer Card
```

Purpose:

```text
Enable a specific Customer Card using the Customer Card ID.
```

Use this operation when a previously disabled Customer Card should be enabled again.

---

## Input Schema

| Field | Type | Required | Description |
|---|---:|---:|---|
| `customer_card_id` | string | Yes | 20-character Customer Card ID. |

Example:

```json
{
  "customer_card_id": "XXXXXXXXXXXXXXXXXXXX"
}
```

---

## Output Schema

Successful output can include:

| Field | Description |
|---|---|
| `api_call_id` | 20-character API call ID. |
| `api_call_unix` | Unix timestamp when the API call was initiated. |
| `code` | API response code. `1` indicates success. |
| `customer_id` | 20-character Customer ID associated with the Customer Card. |
| `customer_card_id` | 20-character Customer Card ID. |
| `result` | Result message. |


---

## Recommended Workflow

```text
1. Use GetCustomerCard to verify the card and related Customer.
2. Confirm why the card is disabled and why it should be enabled.
3. Verify the Customer in customer-facing flows.
4. Confirm the action.
5. Run EnableCustomerCard.
6. Use GetCustomerCard or GetCustomer to verify.
```

---

## Safety Guidance

Enabling a card can allow the payment method to be used for future billing if other conditions allow it.

Before enabling, confirm:

- correct Customer Card ID,
- correct Customer,
- card is intended to be usable again,
- risk/fraud/chargeback context has been considered where relevant,
- user explicitly confirmed the action.

---

## Customer-Facing AI Verification Warning

Customer Card records are sensitive payment-method records, even though RevCent only returns safe card summaries such as card type, first 6/BIN, last 4, and expiry.

If this operation is used inside a customer-facing AI flow, such as:

- AI Voice Agent,
- public chatbot,
- customer portal assistant,
- SMS assistant,
- any visitor-facing AI workflow,

AI/MCP should verify that the visitor is actually the Customer or is otherwise authorized before providing card details or taking action.

Recommended rule:

```text
Do not provide Customer Card details or perform Customer Card actions based only on visitor-provided input.
```

Use a secondary value from the retrieved RevCent record, such as customer email or phone from `GetCustomerCard.customer`, `GetCustomer`, or another related record.

Safe flow:

```text
Visitor provides customer/card input
    ↓
AI locates/retrieves the Customer Card
    ↓
AI retrieves or reviews the related Customer
    ↓
AI verifies a secondary value from the retrieved RevCent record
    ↓
AI confirms the requested action
    ↓
Only then provides limited information or performs the operation
```

Do not disclose or request full card numbers, CVV/card code, secrets, or payment credentials in normal public chat. Use secure PCI-appropriate payment collection flows for adding cards.


---

## Reporting Guidance

This operation is not a reporting or analytics tool.

Do not use Customer Card lookup/search or mutation operations for:

- counting,
- aggregations,
- metrics,
- reporting,
- data mining,
- bulk retrieval,
- broad analysis,
- card portfolio analysis,
- card expiry reports,
- default-card reports,
- payment-method performance reports,
- customer segmentation reports.

Use:

```text
BigQueryRunQuery
```

for those purposes.

Important AI/MCP behavior:

```text
If AI/MCP intended to use this operation for reporting, metrics, aggregation, or data mining and then realizes BigQueryRunQuery is the correct operation, it does not need to tell the user about the correction.

It should simply use BigQueryRunQuery instead.
```



---

## Final AI/MCP Instruction

Use `EnableCustomerCard` only when the user explicitly wants to enable a specific Customer Card. Retrieve and verify the card first, then confirm and run the operation.


---
Document Parent Directory
* [Operations](https://revcent.com/documentation/markdown/mcp/operation/index.md) - AI/MCP details and overviews for operations available within the RevCent MCP.