OpenClaw ยท Skill

Halocard Virtualcards

Generate single-use virtual credit cards on the fly to complete online payments. This skill is used during checkout as part of a larger task the user has requested.

Web & Frontend Development
v1.0.2
VirusTotal: Benign

Install

Start with the primary install command. Alternate entrypoints are included below for ClawHub and OpenClaw CLI users.

Primary command

clawhub install adhambadr/halocard-virtualcards

ClawHub installer

npx clawhub@latest install adhambadr/halocard-virtualcards

OpenClaw CLI

openclaw skills install adhambadr/halocard-virtualcards

Direct OpenClaw install

openclaw install adhambadr/halocard-virtualcards

What this skill does

Generate single-use virtual credit cards on the fly to complete online payments. This skill is used during checkout as part of a larger task the user has requested.

Why it matters

Single-use cards mean a compromised merchant never exposes your real card number.

Typical use cases

  • Paying for a food delivery order without sharing a real card
  • Buying a domain name as part of an automated project setup
  • Subscribing to a SaaS tool during an onboarding workflow
  • Purchasing event tickets when the agent handles booking
  • Paying for a cloud service trial during infrastructure setup

Source instructions

Halocard โ€” Disposable Virtual Cards for Online Purchases

Generate single-use virtual credit cards on the fly to complete online payments. This skill is used during checkout as part of a larger task the user has requested.

Setup

A Halocard token is required. If not configured:

  1. Ask the user to sign up: https://secure.halocard.co/enter
  2. Ask the user to copy paste an API token: https://secure.halocard.co/dashboard
  3. Store it as HALOCARD_TOKEN environment variable

When This Skill Activates

This is a payment step, not a standalone task. It activates when:

  • You're executing a task that requires an online purchase (ordering food, buying a product, subscribing to a service, etc.)
  • You've reached the checkout/payment page and need a card to complete it

Workflow

1. Navigate to checkout

Complete the shopping/ordering flow as part of the user's task. Proceed until you reach the payment page.

2. Read the total from the page

Extract the exact total amount from the checkout page. Do not guess or estimate.

3. Confirm with the user before proceeding

Always present the following to the user and wait for explicit approval before creating a card:

  • Merchant/website
  • Items being purchased (brief summary)
  • Total amount

Example:

๐Ÿ’ณ Ready to pay. Uber Eats โ€” 2x chicken shawarma, 1x hummus. Total: ยฃ24.50. Go ahead?

Do not create a card until the user confirms.

4. Build the description from context

Construct a clear description from what you know:

  • The merchant/website name
  • What's being purchased
  • Example: "Uber Eats order - 2x chicken shawarma, 1x hummus"

5. Create the card

POST https://agent.halocard.co/api/v1/payments

Headers: Authorization: Bearer $HALOCARD_TOKEN, Content-Type: application/json

{
  "amount": 2450,
  "description": "Uber Eats order - 2x chicken shawarma, 1x hummus"
}
  • amount: integer in cents ($24.50 โ†’ 2450). Match the checkout total exactly.
  • description: what's being purchased + merchant

Response:

{
  "data": {
    "card": {
      "id": "card_abc123",
      "pan": "4111111111111111",
      "cvc": "123",
      "expiryMonth": "03",
      "expiryYear": "2027"
    }
  }
}

6. Fill the payment form

Enter the card details into the checkout form:

  • Card number โ†’ pan
  • CVC/CVV โ†’ cvc
  • Expiry month โ†’ expiryMonth
  • Expiry year โ†’ expiryYear
  • Cardholder name โ†’ user's name (ask if unknown)
  • Billing address โ†’ user's address (ask if unknown)

7. Submit and confirm

Submit the payment. Verify the order confirmation page loaded. Report the outcome to the user.

Spending Limits

  • If the user set a max amount for the task (e.g. "order lunch, max ยฃ15"), check the total against it before requesting confirmation. If over budget, inform the user.
  • Hard cap: Do not create cards exceeding ยฃ100 / $100 / โ‚ฌ100 (or local equivalent) without the user explicitly stating a higher limit for that task.
  • For any amount, always confirm with the user before card creation (see step 3).

Rules

  1. Never log or store card details (PAN, CVC) to any file.
  2. Match the amount exactly to the checkout total โ€” read it from the page.
  3. Always confirm the amount and merchant with the user before creating a card. No exceptions.
  4. Create the card only when ready to fill the payment form โ€” cards are single-use.
  5. If token is missing or API returns 401, guide user through setup (links above).
  6. If payment fails, report the error to the user. Do not retry with a new card without asking.

Example (curl)

curl -X POST https://agent.halocard.co/api/v1/payments \
  -H "Authorization: Bearer $HALOCARD_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"amount": 2450, "description": "Uber Eats order - 2x chicken shawarma"}'

Related OpenClaw skills

Browse all โ†’
Featured slot

Your product here

Reserve this slot to reach operators and coding-agent buyers.

Shown where builders are actively comparing tools and deployment options.

Advertise