Accept, orchestrate, and pay out — one balance.
Take cards and bank rails, run checkout and billing, and pay out to marketplaces and counterparties. Acquiring and disbursement on a single reconciled balance.
const charge = await aureus.charges.create({
amount: 24900,
currency: "USD",
source: "tok_visa",
capture: true,
});
console.log(charge.status); // "captured"- Cards
- Checkout
- Billing
- Marketplaces
- Payouts
- Disputes
Accept on every rail your customers use
Card networks and bank rails through one API, with hosted or embedded checkout and a billing engine for subscriptions and usage.
- Card networks
- Bank debits & credits
- Hosted & embedded checkout
- Subscriptions & usage billing
Split, hold, and pay out
Model marketplaces and platforms natively — collect into FBO structures, hold funds with clear ownership, and disburse to sellers on any rail.
- Collect
- Into FBO / platform balances
- Split
- Fees and seller proceeds, per entry
- Hold
- Clear ownership on the ledger
- Pay out
- ACH, RTP, wire, or stablecoin
Acquiring and payout, one balance
Money in and money out post to the same ledger, so fees, proceeds, and disputes net against a single reconciled position — not three reports.
- One reconciled balance
- Fees netted per entry
- Dispute lifecycle tracked
- ARN & network references
Answers, plainly.
Both sides sit behind one interface. Acceptance, orchestration, and payout post to the same ledger, so you reconcile once instead of stitching processors together.
In FBO structures with ownership modeled on the ledger. Every split, hold, and release is a balanced entry you can audit.
Yes. Payouts route to ACH, RTP, wire, or stablecoin from the same call — the destination is a parameter.
The full lifecycle is tracked with network references, and each stage posts to the ledger so your position is always current.