Instant Card Issuance
Create and fund virtual cards for AI agents instantly.
•••• •••• 4417
procurement-agent
Equip autonomous agents with controlled spending, virtual cards, payment policies and real-time transaction visibility from one platform.
[agent]procurement-agent → authorization requested[agent]payee api.openai.com · amount $20.00[payence]per-call ceiling ............... within limit[payence]merchant allowlist ............. match[payence]monthly budget ................. $2,411 left[card]virtual card •••• 4417 authorized in 31 ms[ok]captured $20.00 · openai.com[audit]auth_3b71de written to the ledger[agent]payee aws.amazon.com · amount $48.00[payence]all policy checks .............. pass[ok]captured $48.00 · aws.amazon.com[agent]payee unknown-vendor.io · amount $99.00[payence]merchant allowlist ............. no match[deny]declined at the network · pol_procure_2500Every request checked against policy. Every charge written to the ledger.
Payence
Agent issued5412 •••• •••• 4417
Example card. Type your own name on it, pick a network and a colour.
Merchant: the card clears at this payee and nowhere else.
Card protection
Freeze instantly to block every agent payment.
An agent can read a contract, pick a vendor and file the ticket. Then it reaches the payment screen and stops, because the only options are a shared company card or a key in an environment variable. Payence replaces both with a card the agent owns, bounded by a policy it cannot argue with.
agent activity
Liveprocurement-agent
openai.com · $20.00
research-agent
aws.amazon.com · $48.00
ops-agent
unknown-vendor.io · $310.00
billing-agent
vercel.com · $29.00
Sample activity
openai.com
$20.00
aws.amazon.com
$48.00
unknown-vendor.io
$310.00
merchant not in allowlist → declined at the network
Create and fund virtual cards for AI agents instantly.
•••• •••• 4417
procurement-agent
Restrict merchants, control budgets and enforce spending boundaries.
Monitor every transaction across agents and virtual cards.
Track every transaction back to the agent, task, policy and approval.
Two calls to put a bounded card in an agent's hands. Idempotent REST, typed SDKs, signed webhooks, and a sandbox that returns the same errors production does.
const agent = await payence.agents.create({ name: "procurement-agent"}); const card = await payence.cards.issue({ agent: agent.id, limit: 2500, merchant: "openai.com"});31 ms
issue
REST
+ webhooks
TS · PY · GO
sdks
MCP
server
A card exists the moment the agent does, funded from the balance you already keep.
procurement-agent
•••• 4417
research-agent
•••• 8820
ops-agent
•••• 1093
Cards clear at the merchants you named and nowhere else.
A ceiling per agent, per card and per authorization.
Above the line you set, a person signs before the money moves.
One task, one card, expired the moment the task closes.
One call freezes every card the fleet holds.
Agent, task, policy and approver, chained to every charge.
Give autonomous systems the financial infrastructure they need to complete the work.
transactions · today
LiveOpenAI API
procurement-agent · 12:04:21
-$20
AWS
research-agent · 11:52:09
-$48
Vercel
billing-agent · 11:31:44
-$29
Datadog
ops-agent · 10:58:17
-$12
$2,391
of $2,500 monthly cap
Sample figures
A policy is a document, not a paragraph in a system prompt. It decides what an agent may spend, which card it holds, where that card clears, what needs a human, and who sees the charge, and it is evaluated on our side, every single time.
pol_procure_2500
v4 · activelast decision · 12:03:52 · declined unknown-vendor.io · merchant not in allowlist
Every agent gets a policy: a ceiling per month and per authorization, a list of merchants it may pay, and a threshold above which a person signs off. The policy is evaluated on our side before the charge clears, so an agent cannot talk its way past it.
Build autonomous systems that can spend safely.
Sandbox keys in one email. No card required.
Last updated 1 January 2026
Template copy for a fictional product. Not legal advice. Replace it with text reviewed by counsel before launch.
These terms govern your use of Payence, a platform that issues virtual payment credentials to software agents you operate.
By creating an account, issuing a card or calling the API, you agree to these terms on behalf of yourself and any organisation you represent. If you do not agree, do not use the service.
You must be able to enter a binding contract, and the organisation you bind must be lawfully constituted.
Payence issues virtual cards, evaluates the spending policies you configure, authorises or declines transactions against them, and records the result. Funds are held and settled by our regulated banking and card-network partners, not by Payence.
We are the authorisation and record layer. We are not a bank, and we do not provide credit, investment or tax advice.
You are responsible for your API keys, for the agents you authorise, and for the policies you set for them. An agent acting inside the limits you configured is acting with your authority, and the resulting charges are yours.
Keep credentials out of prompts, model context and public repositories. Tell us without delay if a key is exposed, and rotate it.
Do not use the service for fraud, money laundering, sanctions evasion, or any purpose prohibited by the card networks or by applicable law.
Do not attempt to circumvent merchant restrictions, spending ceilings or approval thresholds, whether directly or by instructing an agent to do so. Do not use cards issued to another party without authority.
We may suspend an agent, a card or an account that we reasonably believe is being used this way, and we will tell you why when we lawfully can.
The paid plan is charged as a percentage of settled volume, at the rate shown on the pricing page at the time the transaction settles. There is no per-seat fee and no minimum commitment.
Fees are billed monthly in arrears and are exclusive of tax. Network and interchange costs passed through by our partners are itemised separately.
We aim for high availability on the authorisation plane and publish our status page, but the service is provided without a guarantee of uninterrupted operation unless a separate service level agreement is signed.
We may perform maintenance, and will give notice of planned work that affects authorisation.
You may close your account at any time. We may terminate for material breach, for legal or network-compliance reasons, or on notice if we discontinue the service.
On termination, cards are frozen, pending authorisations are allowed to settle, and your records remain available for export for thirty days.
Neither party is liable for indirect or consequential loss, or for lost profit or lost data. Our total liability in any twelve-month period is limited to the fees you paid us in that period.
Nothing here limits liability that cannot lawfully be limited, including for fraud or death and personal injury caused by negligence.
We may change these terms. Material changes take effect thirty days after we notify you by email or in the console; continuing to use the service after that means you accept them.
These terms are governed by the laws of the jurisdiction named in your order form, and the courts of that jurisdiction have exclusive jurisdiction over any dispute.
Questions about these terms: legal@payence.example.
Last updated 1 January 2026
Template copy for a fictional product. Not legal advice. Replace it with text reviewed by counsel before launch.
This policy explains what Payence collects when you and your agents use the platform, why we hold it, and what you can ask us to do with it.
Account data: the name, work email and billing details of the people who administer your organisation.
Transaction data: the agent identifier, the card, the amount, the merchant, the policy applied, the decision and its reason, and the timestamp.
Technical data: API request metadata, IP address, and diagnostic logs needed to run and secure the service.
We do not receive your agents' prompts, model context, retrieved documents or reasoning. An agent sends us an authorisation request, not its transcript.
We do not sell personal data, and we do not use your transaction data to train models.
To authorise payments and enforce the policies you configured; to prevent fraud and abuse; to bill you; to provide support; and to meet the financial record-keeping obligations that apply to payments.
The lawful bases we rely on are performance of our contract with you, our legitimate interest in operating and securing the service, and compliance with legal obligations.
Our issuing bank, card networks and settlement partners, to the extent needed to move the money. Infrastructure providers who host the service under written data-processing terms. Authorities, where the law requires it.
A current list of subprocessors is available on request.
Transaction records are retained for the period required of regulated payment records, currently seven years. Diagnostic logs are retained for ninety days. Account data is deleted within thirty days of account closure, except where we must keep it.
Depending on where you live, you may ask for a copy of your personal data, ask us to correct or delete it, object to or restrict processing, or receive it in a portable format.
Write to privacy@payence.example and we will respond within thirty days. You may also complain to your local data protection authority.
Data is encrypted in transit and at rest. Card credentials are held in a segregated environment and are never returned in full through the API. Access is scoped, logged and reviewed, and we test the platform independently.
We use strictly necessary cookies to keep you signed in, and analytics cookies to understand how the console is used. You can refuse analytics cookies without losing any functionality.
Where we move personal data across borders, we do so under an adequacy decision or standard contractual clauses, with the additional measures those clauses require.
Please accept to continue
Template copy for a fictional product. Not legal advice. Replace it with text reviewed by counsel before launch.
Payence issues virtual payment cards to software agents you operate, evaluates the spending policies you configure, and authorises or declines each transaction against them. These terms cover your use of this site and of the sandbox behind it.
Every figure, agent, card, merchant and transaction shown on this page is sample data. Nothing here moves real money, and no card shown is a live credential. Accepting these terms does not open an account or create any payment obligation.
You are responsible for your API keys, for the agents you authorise and for the policies you set for them. An agent spending inside the limits you configured is acting with your authority, and the resulting charges are yours. Keep credentials out of prompts, model context and public repositories.
Do not use the service for fraud, money laundering or sanctions evasion, and do not attempt to circumvent merchant restrictions, spending ceilings or approval thresholds, whether directly or by instructing an agent to do it for you. We may suspend an agent, a card or an account we reasonably believe is being used this way.
The free plan covers the sandbox and your first agents at no cost. The paid plan is charged as a percentage of settled volume, at the rate shown on the pricing page when the transaction settles. No per-seat fee, no minimum commitment, and no charge until money actually moves.
We keep account details, and the metadata of each authorisation: the agent, the amount, the merchant, the policy applied and the decision. We never receive your agents' prompts, model context or reasoning, we do not sell personal data, and we do not train models on your transactions. The full Privacy Policy is linked in the footer.
We may update these terms. Material changes take effect thirty days after we tell you, and continuing to use the service after that means you accept them.
Accept to carry on using the site. Decline and the site will close. Nothing is stored, and you can come back and accept at any time.
PAYENCE
Payence needs your agreement before you can use the site. Nothing was stored, and you can accept whenever you like.
Payence can keep one first-party entry in this browser that remembers the card you design here: its name, colour and network, so your card is still yours when you come back. No analytics, no third parties, nothing leaves this browser.