A company spend policy is a document; a shared company card does not read documents. The policy says $500 a month per person, and the card approves $5,000 without blinking. Giving each purpose its own card with a fixed cap closes that gap, and you can start today with cards you buy, not build.
In short: a corporate virtual card API lets finance create a separate payment card for each team, vendor or project from code, each with its own limit. Gpaynow Card API v2 is planned for this and is in early access (not live yet). Today, finance can get the same control by buying prepaid cards in the Gpaynow store, where each card's balance is its cap, with no KYC to buy.
Buy a prepaid virtual card per team, vendor or project in the Gpaynow store, paid from your balance topped up with crypto. A prepaid card can only spend its balance, so the balance is the cap, set in advance. Each card price is the card balance plus a one-time activation fee ($5, or $15 on $300 cards); there are no monthly fees, and there is no KYC to buy. Some merchants refuse prepaid cards, so check their payment rules first.
For companies that want cards created and controlled by software, Card API v2 is planned to offer programmatic issuing, per-card limits, instant freeze and close, and a signed webhook on every charge for live spend visibility. It is in early access: no card issuer is connected yet, and API keys, a test environment and webhooks are not available yet. No payment is taken until your access is approved. Planned plans start at a one-time $1,500, with no monthly fees; see the Card API page.
Yes. You can buy prepaid cards in the store from the dashboard, one per team or vendor, with no code and no KYC to buy.
Load each prepaid card with the amount that purpose needs; it cannot spend more. Per-card limits by API are planned for Card API v2.
Live webhook feeds are a planned Card API v2 feature. Today you can review card spend in your Gpaynow dashboard.
No. Card API v2 is in early access, and no payment is taken until your access is approved.