Products
Seven products, one set of rules.
Each product answers one job. They share the mandate, the review queue and the payment history.
Spending rules
Budgets, rate limits and approvals, checked before the call runs.
Payments run within your mandate. Requests matching your approval rules wait for review; requests outside hard limits are blocked.
- Per-transaction limitA boleto above it waits for approval in the Dashboard.
- Hard budgetA hard limit for the day, week or month. Requests that would exceed it are blocked.
- Allowed recipientsWho the agent can pay, listed in the mandate.
- Rate limitHow many payments the agent can make in a window.
- 01Write the ruleSet caps, budget, recipients and limits for each agent.
- 02Check every requestEach payment is checked on the server before it is sent.
- 03Get a clear decisionAllow, stop or wait for a person. Every outcome is recorded.
Try a test payment against your rulesSimulated demo · no real money
review_above R$ 3,000
hard_budget R$ 20,000 / month
allowed compute, suppliers
Approvals
A person decides before money moves.
Requests matching your approval rules wait for review. The reviewer sees the request, the rule it matched and when it expires.
- Approval rulesWhich payments need a person: a boleto above the mandate's per-transaction limit, or a call your approval rules name.
- ExpiryRequests expire at the time you set.
- Status and historyPending, approved, denied or expired, kept in the audit trail.
- Verified approverrolling outThe approver's identity checked before the decision counts.
How a request is reviewed
- A rule stops the paymentThe request matches an approval rule.
- The request is heldNothing is sent. The reviewer sees the amount, the rule and the expiry.
- An admin approves or deniesA person decides before money moves.
- The result is recordedThe decision goes into the audit trail.
Payment records
A signed receipt for every settled spend.
Every governed action is recorded in a hash-chained audit trail. Every settled spend gets a signed receipt.
Demo data
- Signed receiptOne per settled spend, verifiable with a public key.
- Audit trail exportExport the chain as a signed manifest.
- CSV exportrolling outPayment history as a spreadsheet.
- Reconciliationrolling outMatch payments against your accounts.
- 01RecordEach step is written as it happens.
- 02TrackFollow a payment from the mandate to the delivery.
- 03Export or queryPull the audit trail or look up one payment.
What is recorded
Mandate, quote, payment and delivery, for every settled spend.
Two records, kept apart
The audit trail records every governed action. The signed receipt covers each settled spend.
Who uses it
Finance closes the month. Operations answers "what happened". Security checks who allowed what.
What the platform covers
The parts every payment goes through.
Identity and mandates
Agents and the signed spend authority each one runs under: cap, scope, expiry. Revocable.
DocsPayment methods
Pix, boleto, card and USDC. One call; CodeSpar picks the payment method that fits.
DocsApprovals
Requests matching your approval rules wait for review. An admin approves or denies; requests expire at the time you set.
Docs