Skyvern/docs/cloud/managing-credentials/credit-card-credentials.mdx
Naman 59cd1e10bb
Some checks are pending
Run tests and pre-commit / Run tests and pre-commit hooks (push) Waiting to run
Run tests and pre-commit / Frontend Lint and Build (push) Waiting to run
Publish Fern Docs / run (push) Waiting to run
suchintan's feedback + changelog (#4947)
Co-authored-by: Ritik Sahni <ritiksahni0203@gmail.com>
2026-03-02 18:41:31 +00:00

76 lines
3.5 KiB
Text

---
title: Credit Card Credentials
subtitle: Store payment details for purchase and checkout workflows
slug: cloud/managing-credentials/credit-card-credentials
---
Credit card credentials store payment details so the AI can fill checkout forms without you embedding card numbers in prompts or parameters. Like all credentials, card numbers never reach the LLM. They are injected directly at the browser level.
## Creating a credit card credential
<Steps>
<Step title="Open the Add dialog">
Click **+ Add → Credit Card** from the Credentials page.
</Step>
<Step title="Fill in the card details">
Provide all required fields:
| Field | Description |
|-------|------------|
| **Name** | A label like "Corporate Visa" to identify it later |
| **Cardholder Name** | Name printed on the card |
| **Number** | Full card number (spaces added automatically as you type) |
| **Brand** | Card network: Visa, Mastercard, American Express, Discover, JCB, Diners Club, Maestro, UnionPay, RuPay, or Other |
| **Expiration** | Month and year in `MM/YY` format (slash inserted automatically) |
| **CVV** | 3 or 4 digit security code |
</Step>
<Step title="Save">
Click **Save**. After saving, the card number is masked and only the last four digits are ever shown again.
</Step>
</Steps>
<img src="/images/cloud/credentials-add-credit-card.png" alt="Add Credit Card credential modal" />
<img src="/images/cloud/credentials-credit-card-detail.png" alt="Saved credit card credential showing masked card number" />
## Using credit cards in workflows
Credit cards work with [**Browser Task** and **Browser Action**](/cloud/building-workflows/configure-blocks) blocks that interact with checkout pages. The AI automatically recognizes standard checkout forms and fills card number, name, expiration, and CVV fields with the stored details. No field mapping is required.
For workflows that need different cards at runtime, add a **Credential parameter** (type: `credential_id`) in the [workflow editor](/cloud/building-workflows/add-parameters). When someone runs the workflow, they select which card to use from a dropdown. This lets the same checkout workflow work with different payment methods.
<Note>
If you use 1Password as a credential provider, credit cards require a custom text field named **"Expire Date"**, **"Expiry Date"**, or **"Expiration Date"** in `MM/YYYY` or `MM/YY` format. 1Password does not expose the native expiration field through its API, so Skyvern reads this custom text field instead. See [External Providers](/cloud/managing-credentials/external-providers#1password) for full setup details.
</Note>
## Editing and deleting
<Note>
To edit a credential, click the **pencil icon** on its row. For security, saved card details are never retrieved, so you must re-enter all fields when updating.
</Note>
Click the **trash icon** on any credential row to delete it. Deletion is permanent and cannot be undone.
<CardGroup cols={3}>
<Card
title="Password Credentials"
icon="key"
href="/cloud/managing-credentials/password-credentials"
>
Store login details with optional 2FA
</Card>
<Card
title="External Providers"
icon="vault"
href="/cloud/managing-credentials/external-providers"
>
Connect Bitwarden, 1Password, Azure Key Vault, or a custom API
</Card>
<Card
title="Credentials Overview"
icon="lock"
href="/cloud/managing-credentials/credentials-overview"
>
Security model, quick start, and all credential types
</Card>
</CardGroup>