Netflix card
Recurring only
Garde
Purpose-specific virtual cards that let you decide exactly how your money can be charged before a transaction happens.
Your money. Your rules.
Illustrative control desk
ActiveSubscriptions card
Garde virtual cardSubscriptions
Spends only inside the rules below.
5129 **** **** 4182
Rule stack5 checks
- Purpose: subscriptions
- Per charge: NGN 8,000 max
- Merchant: streaming services
- Renewals: notify before approval
- Expires: 31 Dec 2026
Cards carry intent, not just card numbers.
Each card starts with a purpose. The rules, limits, lifecycle, and activity all stay attached to that purpose, so the user knows what can happen before a merchant tries to charge them.
Shopping card
Online checkout
Travel card
Merchant category
Cards to rules to limits to activity to intervention.
Garde is designed around preventive control. The web experience should make every step visible without turning into a wallet, banking suite, or expense platform.
Create a card for one intent
Name the card by what it is allowed to do: subscriptions, shopping, travel, or a one-off purchase.
Attach rules before it spends
Set limits, expiry, merchant controls where supported, renewal behavior, and freeze states ahead of time.
Review every intervention
Approved and declined transactions stay visible with clear reasons, not a generic payment failure.
Declines should explain themselves.
A blocked transaction is only useful when the user understands the reason and the next available action: raise a limit, change the rule, unfreeze the card, or leave the block in place.
| Merchant | Amount | Card | Result | Reason |
|---|---|---|---|---|
| Netflix | NGN 7,000 | Netflix card | Approved | Recurring rule matched |
| Gamebox Pro | NGN 18,500 | Subscriptions | Declined | Per-charge limit exceeded |
| Konga | NGN 42,000 | Shopping | Pending | Waiting for confirmation |
Built around payment realities.
The customer-facing product can feel simple only if the underlying model respects authorization, card lifecycle, KYC, ledger, webhook, and sensitive-data boundaries from the beginning.
- Issuer and processor constraints shape card lifecycle states.
- Authorization rules must fail closed when limits or ownership are unclear.
- Webhook and ledger state must stay reliable through retries and duplicate events.
- KYC, AML, and sensitive payment data handling are product requirements.
Control the charge before it becomes a problem.
Garde's web dashboard will bring the same card-first controls to the browser: purpose cards, rules, limits, lifecycle actions, notifications, and clear transaction history.