Card as a Service →

Virtual cards, issued by API.

Guara is Card as a Service: issue virtual Visa or Mastercard cards, fund one balance and authorize purchases in real time — behind one API, with business verification (KYB) built in.

Developer? Get sandbox keys →

1 200ms
for your endpoint to approve or decline a purchase
2keys
live at once — rotate without a second of downtime
5simulators
top-up, purchase, decline, refund and 3-D Secure
USDT
fund your balance over TRC-20 or ERC-20
00 — Platform

Card as a Service, end to end.

Issuing, money movement, authorization, controls and compliance come as one stack. You bring the product and the users — we run the cards.

Issuing

Virtual Visa or Mastercard

Issue a card in one call, tie it to your user ID, label it, cap it, block or cancel it. The network is set per card program.

POST /cards201 · active•••• 4417
Funding

One balance, in USDT

Top up over TRC-20 or ERC-20. Cards hold nothing — purchases are paid from the balance at authorization.

Authorization

Your code decides

Default rules by card state, limit and balance — or a real-time call to your endpoint. Fail-closed.

Controls

Limits & freezes

Monthly limits per card, instant block and unblock, scoped API keys with two-key rotation.

Card data

Card numbers off your servers

Number and CVV open in a one-time secure frame and never pass through your systems. 3-D Secure codes arrive by API and webhook.

Events

Signed webhooks

Charges, declines, refunds, card issued, blocked, cancelled and 3DS codes — HMAC-signed, retried up to 7 times over ~9 hours.

Compliance

KYB built in

Verify your company in the console. Until it is approved, live deposits are capped.

Sandbox

Every event, on demand

Test keys from minute one. Simulate top-ups, purchases, declines, refunds and 3DS codes.

Agents

MCP server

Plug cards into Claude, ChatGPT or your own agent, with per-key scopes and daily limits.

01 — Authorization

Approve or decline every purchase from your own endpoint.

Cards hold no money. When a card is used, we check its state, its limit and your balance — then, in external mode, we ask your endpoint. No answer in time means no purchase. Try it.

APPROVED within limit · balance ok · your endpoint approved
Your endpoint receives

        
02 — API

Card issuing API.
REST, scoped keys, signed webhooks.

REST with Bearer keys and scopes. Idempotency on everything that moves money. Signed webhooks. An MCP server, so an agent can hold a card without you writing glue.


      
Scopes products:readcards:readcards:issuecards:writetransactions:readwebhooks:manage
03 — Console

See every card and every decline in one console.

Keys, cards, transactions, webhook deliveries and integration health in one place. Documentation and a Postman collection live right next to your keys.

04 — Programs

Virtual cards for AI agents, ads, wallets and teams.

A

AI agents

An agent gets its own card, a monthly limit and a key with only the scopes it needs. It buys APIs and SaaS; you see every purchase as it happens.

B

Media buying

A card per ad account and per campaign. Top up one balance in USDT, cap each card, block one without touching the rest.

C

Wallets & fintech

Let your users spend what they hold with you anywhere cards are accepted. Show card details in a one-time frame — the numbers never touch your servers.

D

Spend management

Cards for teams, vendors and subscriptions. 3-D Secure codes arrive by webhook, so people confirm payments without asking finance.

05 — Onboarding

Sandbox today.
Live when you're verified.

  1. Minute 1Sign up

    Create a console account. Test keys are issued at once — no documents, no calls.

  2. Day 1Build

    Issue test cards and fire every event your integration must handle with the sandbox simulators.

  3. Go-liveScale

    Limits lifted. Fund in USDT, switch to gp_live_ keys, issue as many cards as you need.

06 — Access

Tell us what you're building.

We answer within one business day with pricing for your volume and a direct line to the people who build the API.

Prefer email? support@guarapay.io
What will the cards be for?
Cards per month

07 — Details

Card issuing FAQ

Who can use Guara?

Registered companies that issue cards to their own users, teams or agents. Every business is verified before live limits are lifted.

How is money held?

You keep one balance with us, funded in USDT over TRC-20 or ERC-20. Cards hold nothing: each purchase is paid from the balance at the moment it is authorized.

What if my endpoint is down?

We fail closed: if your endpoint doesn't answer within 1.2 seconds, or answers with something other than a clear approval, the purchase is declined. Integration health is visible in the console.

Do I need PCI DSS?

Card number and CVV open in a one-time secure frame served by us, so they never reach your servers or logs. Your own PCI DSS obligations are for you and your assessor to confirm.

What documents do you ask for?

Certificate of incorporation, shareholders and beneficial owners with 25% or more, and an ID of a director. Proof of address and your AML policy speed things up.

How are Guara and Guarapay related?

Guara is the business side of Guarapay. Guarapay issues cards to people in its app; Guara gives companies the same infrastructure through an API. That's why the console, sandbox, API and support live on guarapay.io.

What cards can I issue?

Virtual cards in USD, on Visa or Mastercard depending on your program. They work online in any currency — we convert at authorization and send you both amounts.

Can an AI agent spend without me?

No more than you allow. Each card has its own limit, each API key only the scopes you grant and a daily issuing cap, and in external mode every purchase still goes to your endpoint for a decision.

How is it priced?

Per card issued and per operation, set by your volume. Send a request — we'll come back with numbers, not a sales deck.