# Security control

<figure><img src="/files/hhmt0WSJXZKHT4BB2hLl" alt="" width="375"><figcaption></figcaption></figure>

Security and user control are designed around the card itself and the payment flow, rather than user accounts.

The product relies on standard payment network mechanisms and mobile wallet protections to help ensure safe card usage while maintaining a simple, frictionless experience.

***

## Card and payment protection

Card payments are processed using established payment network standards and modern protection mechanisms.

When cards are used via Apple Pay or Google Pay, additional device-level protections are applied by the mobile wallet, such as biometric authentication or device security settings.

***

## Card Controls

Users have full control over their virtual card directly from the dashboard. Key control features include:

| Control             | Description                              |
| ------------------- | ---------------------------------------- |
| Freeze / unfreeze   | Temporarily block or restore card usage  |
| Spending limits     | Apply limits to control spending amounts |
| Transaction history | Review completed card transactions       |
| Card reissue        | Generate new card details if needed      |

Card controls can be used at any time without contacting support.

{% hint style="warning" %}
Never share card details, verification codes, or device access with third parties. Mobile wallet security depends on device-level protections.
{% endhint %}

## Transaction Protection

Each card transaction includes clear details such as merchant name, amount, and timing, helping users monitor activity and identify unexpected payments.


---

# 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://docs.starpayinfo.com/welcome/security-control.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.