enterprise | a·card
enterprise

Agentic spend under governance.

Departments, org policy, an audit trail of every decision, a compliance stack that gates money movement in real time, and a per-merchant API for the systems you already run.

Talk to us Read the docs
Chess piece
01control

When finance asks why an agent spent $40,000 in March, the answer is one query.

Every card is scoped: total limit, per-transaction ceiling, velocity window, merchant category allow-list, approval threshold, expiry. Above the card sit the controls no card can override.

ORG POLICY
Blocked merchant categories and an org-wide approval threshold, evaluated before per-card rules, so no card configuration can route around them.
DEPARTMENTS
Monthly budgets checked in the same hot path as every other rule, not reconciled at month-end when it's too late.
APPROVALS
A grant matched to card, merchant and amount, consumed by the retried authorization and then spent. One approval, one purchase.
AUDIT LOG
Every authorization, approved, declined or held, with its exact reason code.
ACCESS
Role-based access control, SSO and MFA, read-only API keys that resolve to exactly the viewer role.
KILL SWITCH
Close any card or freeze any agent with one call. Held funds return to the wallet immediately.
02the ledger

Scale horizontally without racing your own ledger.

A real double-entry ledger. Every movement is balanced: debits equal credits, in the same currency. Spend is two-phase, an authorization places a hold, later captured or released.

CONCURRENCY PROOF · WALLET ROOM FOR 3
AUTH A · $5,000APPROVED
AUTH B · $5,000APPROVED
AUTH C · $5,000APPROVED
AUTH D · $5,000INSUFFICIENT_FUNDS
AUTH E · $5,000INSUFFICIENT_FUNDS
EXACTLY AS MANY AS FIT · EVERY TIME
03the authorization path

One path, one order, every client.

Dashboard, API or agent, there is no privileged caller. The path is synchronous and allocation-light, with no network calls, so it answers inside the issuer's real-time window.

01Exactly-onceGuard on the issuer authorization id. A retry returns the original decision and can never double-charge.
02Card resolutioncard_not_found
03Org policymerchant_category_blocked_by_policy
04Card statecard_closed
05Currencycurrency_mismatch
06Categorymerchant_category_not_allowed
07Per transactionper_transaction_limit_exceeded
08Card totalcard_total_limit_exceeded
09Velocityvelocity_limit_exceeded
10Approval thresholdpending_human_approval
11Department budgetdepartment_budget_exceeded
12Atomic holdinsufficient_funds
04supply & procurement

Verified suppliers, structured catalogues, and a freshness timestamp on every offer.

Offers return as fresh, aging or stale. Merchants see their own catalogue health, item count, how many are fresh, and the median age of their inventory data, so keeping it current is a visible, competitive act rather than an invisible chore.

RELIABILITY
Earned from real orders: fulfilment rate, punctuality against promised times, dispute rate. New merchants score neutral, never punished for being new, and a merchant who delivers without ever promising a time scores neutral on punctuality rather than perfect.
OPERATING HOURS
A first-class field. A merchant who hasn't declared hours reads as open, we don't hide supply on an assumption, but one who has isn't ranked as available at 2am.
05orders & fulfilment

A cancelled order cannot quietly become delivered.

Discovery isn't the deliverable. A-MERCHANT carries the full commercial loop, with a typed state machine that permits only legal transitions.

PLACEDAgent commits to an offer; it hits the merchant's queue and POS
ACCEPTEDMerchant confirms, with a promised fulfilment time
FULFILLINGPicking, packing, preparing
DISPATCHEDTracking reference attached, buyer notified
DELIVEREDCloses the loop and feeds reliability
CANCELLED / DISPUTEDRecorded with a reason, reflected in reliability

Alongside orders, every card purchase at a listed merchant raises a purchase notice the merchant can acknowledge or dispute, so a sale at the till and a sale through an agent land in the same inbox.

06merchant API

Your till knows about the sale before your staff do.

Merchants aren't expected to live in a dashboard. Each one mints machine credentials for its own POS, ERP or stock system and runs A-MERCHANT as a back-office integration.

SCOPED KEYS
Read-only or read-write, named per integration, revocable one at a time. Secrets shown once, stored only as hashes.
PUSH, NOT POLL
Orders, status changes and purchase notices pushed as signed webhooks, with delivery health and consecutive-failure count visible.
CATALOGUE SYNC
Upsert items and restate stock in bulk from the system that already knows the truth.
HOURS
Declare when you're open. Buying outside them doesn't become an order you can't fill.
07settlement · AFP

One intent in, the right rail out.

AFP scores every eligible rail on cost, speed and finality, then routes down the one that fits, and returns the reasoning.

CARDLIVE
Merchant purchases · reversal window
x402BUILT, GATED
Machine-to-machine micropayments · instant
STABLECOINBUILT, GATED
Cross-border without correspondent banking · instant
BANK / EFT / ACHPLANNED
Invoiced suppliers, larger payments · settlement delay
Rails that move value outside the card network carry Travel Rule messaging and counterparty wallet screening, wired in before the rail can be enabled, not bolted on after the first transfer.
08compliance

Compliance is not a screen at signup.

Money movement is gated on a check computed at the moment of the request, never cached. A sanctions hit blocks money even on an otherwise-approved identity, unless a named human has attributed an override.

KYC
Identity verification against government and commercial identity sources in each market.
KYB
Company registry sources, extending to directors and ultimate beneficial ownership.
AML
Sanctions, OFAC, PEP and adverse-media screening, with ongoing monitoring that keeps re-screening after approval.
MONITORING
Cumulative volume, rapid in-and-out movement, high-risk jurisdictions, sanctioned counterparties, and agent-specific patterns such as credential fan-out.
CASES
Alerts become cases with an owner, a decision and a note.
BLOCKLISTS
Org-level and platform-level blocks on identities, emails and counterparties, checked before money moves.

The provider's decision and a human override are stored as separate fields. An override never overwrites the original. You can always tell an automated approval from a human one, and who made it.

09security & assurance

Credentials we can't read.

Scrypt-hashed passwords; session tokens and API secrets stored only as hashes.
Issuer-hosted card credentials, so raw card numbers never enter our environment.
Signed webhooks with timing-safe verification and a replay window.
Private subnets, WAF, encrypted database, TLS enforced, CloudTrail and GuardDuty on from the first deploy.
Enterprise SSO and MFA, role-based access control throughout.
459 automated tests. 396 run on every change; 63 more run against a live Postgres to prove the multi-writer paths behave under real locking.
Deploy the whole stack to AWS with one command, or point it at your own Postgres and run it yourself.

Architected to SOC 2 and PCI DSS principles: least-privilege access, full audit logging, encryption in transit and at rest, change control, card data held outside our environment. Report a vulnerability to hello@a-card.cc, acknowledged within one business day. We do not pursue good-faith researchers.

10markets & regulation

Two markets, one ledger.

UNITED STATES
BSA/AML-aligned program design: customer identification, OFAC screening, ongoing monitoring, recordkeeping, under a sponsoring US financial institution.
SOUTH AFRICA
FICA-aligned customer due diligence, record-keeping and monitoring, built to operate under a sponsoring licensed institution while our own permissions are finalised.
CURRENCIES
USD and ZAR native on one ledger; NGN and KES supported. Currency is a field, not a fork.
RECORDS
Verification, transaction and screening records retained at least five years, the period both FICA and the Bank Secrecy Act require.
AICPA SOC 2
SOC 2 Type II
IN PROGRESS
PCI DSS
PCI DSS SAQ D
IN PROGRESS
11pricing

Companies

$2,800
/ month

No per-user or per-card fees. Are you a startup? Talk to us.

Effectively unlimited card issuance, uncapped per-card ceiling, unlimited merchant API keys, departments and org policy, SSO and MFA, dedicated support and a contractual SLA with service credits.

Cards

Issue new Agentcards or connect the cards your users already have.

One-time or multi-use cards
Accepted at Visa merchants worldwide
$0 per issued or connected card

Purchases API

DoorDash, Good Eggs, Uber Eats, Ticketmaster, and 100+ more.

No per-order fees on covered purchases
$0 per order, no metered fees

Compliance

The regulated surface is ours, not yours.

KYC in seconds, inside your flow
Fraud, disputes, and chargebacks handled
$0 included
revenue streams
Interchange on every settled purchase
1%
Markup on every transaction, set from the dashboard
your call

Self-serve plans run $0, $8 and $28 a month with per-card caps of $50, $500 and $1,000. The per-card cap is a hard platform ceiling above, and independent of, the limits you set yourself. Enterprise is uncapped. Interchange and rail fees are passed through at cost and disclosed before a payment executes. Merchants list and sell at no subscription cost.

12start

Tell us what your agents need to buy, and we'll show you the shortest path to it.

We onboard enterprise teams personally. Scoped pilot in a week.

Get started now enterprise@a-card.cc
Departments, SSO, SLA, security review and control documentation under NDA.
Merchants: enterprise@a-card.cc to list your business and connect your POS.