Payments, Billing & Commerce

A double-entry payments core, metered billing, wallets and a provider marketplace.

The commerce plane: PayCore runs a double-entry ledger with payment instructions, settlement, payouts, rail routing and SCA; Billing meters usage, finalises invoices, runs dunning and tax; Wallets holds balances with holds and captures; and the Provider Marketplace onboards providers with reservations, settlements and reconciliations.

Auth is one model across every service here — an SS-01 bearer token plus X-Tenant-Id on every /api/v1 route. Public base https://api.nexocloud.io/api/v1.

4 real backends, 119 operations.

Every path below is a real route from services/<svc>/openapi.json. Each service lists a representative slice of its full contract.

PayCore SS-22

47 operations

Payments core — a double-entry ledger, payment instructions (authorize/capture/refund), settlement, payouts, rail routing and SCA.

POST/api/v1/instructionsCreate a payment instruction.
POST/api/v1/instructions/{id}/captureCapture an authorized instruction.
POST/api/v1/settlementsSettle a batch.
POST/api/v1/payouts/runRun a payout batch.
POST/api/v1/sca/evaluateEvaluate strong-customer-authentication requirements.
GET/api/v1/ledgerRead the double-entry ledger.

Billing SS-10

34 operations

Metered billing — usage ingestion, invoice finalize, dunning, credits, tax and entitlements.

POST/api/v1/usageIngest a usage event.
POST/api/v1/invoices/finalizeFinalize draft invoices.
POST/api/v1/dunning/{invoice}/startStart a dunning cycle on an overdue invoice.
GET/api/v1/entitlements/{item}Read an entitlement's current state.
POST/api/v1/subscribeSubscribe an account to a plan.

Wallets SS-50

16 operations

Wallets — balances, credit/debit, holds with capture/release and freeze/unfreeze.

POST/api/v1/walletsCreate a wallet.
POST/api/v1/wallets/{id}/debitDebit a wallet.
POST/api/v1/wallets/{id}/holdsPlace a hold on a wallet.
POST/api/v1/wallets/{id}/holds/{hold}/captureCapture a hold.

Provider Marketplace SS-58

22 operations

Provider marketplace — catalog items, provider onboarding, reservations, settlements and reconciliations.

POST/api/v1/providersOnboard a provider.
POST/api/v1/reservationsReserve marketplace capacity.
POST/api/v1/settlements/{id}/finalizeFinalize a provider settlement.
POST/api/v1/reconciliations/{id}/disputeDispute a reconciliation.

Authorize, capture, settle — on a ledger you can audit

A payment moves through the double-entry ledger; usage meters into an invoice; a wallet hold is captured — every transition is journalled and reconcilable.

AuthorizePOST/api/v1/instructions

PayCore records the instruction and reserves funds.

CapturePOST/api/v1/instructions/{id}/capture

Capture posts balanced debit/credit entries to the ledger.

SettlePOST/api/v1/settlements

Batch settlement routes over the healthiest rail.

Meter & invoicePOST/api/v1/invoices/finalize

Billing finalises the usage-based invoice for the period.

Where it sits in the platform.

Payments, Billing & Commerce does not reimplement the platform — it composes it. These are the services it leans on and the seams between them.

PayCore (SS-22)

The double-entry ledger, rail routing, settlement, payouts and SCA — 47 operations.

Billing (SS-10)

Usage metering, invoicing, dunning, tax and entitlements.

Wallets (SS-50)

Balances with holds and captures for prepaid and stored value.

Provider Marketplace (SS-58)

Onboards providers with reservations, settlements and reconciliations.