Issue cards that post straight to the ledger.
Debit and credit, physical and virtual, with programmable spend controls and authorization logic. Every authorization and settlement posts in real time.
const card = await aureus.cards.create({
account: "acct_8842",
type: "virtual",
spend: { limit: 500000, interval: "monthly" },
});
console.log(card.last4); // "4417"- Debit & credit
- Virtual & physical
- Spend controls
- Auth streams
- Rewards
Debit and credit, physical and virtual
Spin up virtual cards instantly or ship physical cards, drawing on operating accounts or credit lines modeled on the ledger.
- Virtual in milliseconds
- Physical fulfillment
- Draw on account or credit line
- Tokenization for wallets
Programmable authorization
Approve or decline in your own logic — by merchant, amount, interval, or any rule you write. Controls run before the authorization clears.
- Limits
- Per card, interval, and merchant
- Auth
- Real-time approve / decline hooks
- MCC
- Category allow / block lists
- Stream
- Webhook on every authorization
Authorizations post in real time
Every authorization, clearing, and reversal posts to the ledger as it happens, so available balances and spend reflect reality to the cent.
- Real-time postings
- Holds & releases modeled
- Reversals as entries
- Rewards accrual
Answers, plainly.
Both. Debit draws on an operating account; credit draws on a line modeled directly on the ledger, so balances and exposure stay accurate.
Yes. Authorization hooks let you approve or decline in real time on any rule — merchant, amount, interval, or your own risk signal.
Cards issue on major networks through partner programs, with tokenization for mobile wallets out of the box.
As ledger entries. A hold reserves available balance; a clearing or reversal posts a balanced transaction that references it.