Card as a Service · Spend management

Cards for teams and subscriptions

One card per person, vendor or SaaS tool, each with its own limit. Over the limit — declined.

Request access Get API keys
  • A card per vendor
  • Monthly limits
  • Block in one call
01 — How it works

Live in three steps.

  1. Minute 1A card per vendor

    Label it with the tool or the team.

    api
    POST /cards 201
    · label: Figma · Design
  2. Minute 2Set the limit

    A renewal above the limit is declined.

    api
    PATCH /cards/3305/limits 200
    · monthly: $45
  3. Every monthReview

    Every charge reaches you by webhook.

    api
    ⇢ transaction.posted ✓
    × declined · over limit
02 — What you get

Spend management, end to end.

Issuing

A card per subscription

Stop a vendor by blocking its card — no surprise renewals, no shared card to replace.

GuaraVIRTUAL
•••• •••• •••• 3305
Figma · DesignMASTERCARD
Controls

Monthly limits

Each card stops at its cap.

$380 / $1,000
Rules

Only the right merchant

Your endpoint approves just the vendor on the card.

APPROVEDECLINE
Controls

Block in one call

Offboarding takes a second.

Funding

One USDT balance

Every card is paid from it.

TRC-20ERC-20
03 — Code

A few lines
to start.

Same REST API, same keys and limits for every program. Docs open in the console after sign-up.

Request access →All API samples
// one card per vendor: approve only the merchant the card was issued for
app.post("/guara/authorize", express.raw({ type: "application/json" }), (req, res) => {
  if (!verify(req)) return res.status(401).end();   // HMAC-SHA256 signature

  const { data } = JSON.parse(req.body);
  const vendor = vendors.byCard(data.card_id);       // e.g. "Figma"

  res.json({ decision: data.merchant === vendor ? "APPROVE" : "DECLINE" });
});

// no answer in 1.2 s, or anything but APPROVE → declined
04 — Access

Tell us what you're building.

Three steps from here to live cards.

  1. We reply within a business dayPricing for your volume, by email or your contact.
  2. You connect the APIKeys, webhooks and MCP for your agents.
  3. You go liveSwitch to live keys and issue cards to your users.
Prefer email? support@guarapay.io
What will the cards be for?
Cards per month

We use these details only to reply to your request. See our Privacy Policy.

05 — Details

Spend management: FAQ

Can I limit a card to one vendor?

Yes. Your endpoint sees the merchant of every purchase and approves only the vendor the card is for.

What happens above the limit?

The purchase is declined, and you get the decline by webhook.

How do I cancel a subscription?

Block or cancel its card with one API call.

Are the cards virtual?

Yes — virtual USD Visa or Mastercard cards that work in any currency.

Virtual cards for teams and subscriptionsRequest access →