Denaro is the payment and transaction layer used by approved DDG portfolio services to process, record, reconcile, and support payments — one ledger, one set of rails, one place to audit.
Each portfolio service integrates the same way and gets the same guarantees. No bespoke reconciliations, no per-service ledgers drifting out of sync.
Charge, refund, transfer, payout. Idempotent endpoints with predictable error shapes.
Append-only ledger. Every state transition has an event, every event has a hash.
Match against processor settlements automatically. Surface only what humans must resolve.
One operator console across services. Refund, retry, dispute, annotate — with an audit trail.
Signed webhooks, scoped API keys, request-level provenance for every dollar moved.
Throughput, success rates, settlement lag — per service, per method, per route.
Portfolio services call Denaro. Denaro calls the processor. The ledger is written first, then settled, then exposed downstream.
# Portfolio service initiates a charge POST https://api.denaro.money/v1/charges service: "preceptor.network" idempotency_key: "chg_2026-05-15_ab12cd" amount: 4900 # cents, USD customer_ref: "pn_user_8421" descriptor: "PRECEPTOR · membership" # Denaro responds — ledger entry exists before processor call returns 201 charge_id: "ch_01HVZQ..." ledger_id: "le_01HVZQ..." state: "authorized" events_url: "/v1/charges/ch_01HVZQ.../events" # Processor settles → webhook → state advances EVENT charge.captured → state: "captured", settlement_eta: "2026-05-17" EVENT charge.settled → state: "settled", reconciled_at: "2026-05-17T14:02Z"
Denaro is not a public payment processor. Access is granted per service after a compliance and integration review. If you operate a DDG portfolio service and need a payment rail, request access below.