Skip to main content
Duro talks to a single processor, Nomba, through one typed client (packages/nomba-client/src/client.ts) plus its token manager (packages/nomba-client/src/token-manager.ts). Every call goes through NombaClient.call (or callBill for the bills envelope), which attaches a cached bearer token, the accountId header, and a timeout. The list below is the exact set of Nomba endpoints Duro calls, one row per distinct endpoint (method + path counted distinctly).
Duro integrates 30 distinct Nomba API endpoints. Counting rule: the same path under two HTTP methods (for example GET vs DELETE on /v1/checkout/tokenized-card-data) counts as two; {...} path segments are one endpoint.

Auth (1)

Checkout & cards (6)

Transfers & payouts (3)

Direct-debit mandates (4)

Virtual accounts (2)

Transactions (2)

Bills / VAS (12)

Totals

Every one of these is a real call in NombaClient (or its token manager); no Nomba endpoint is documented here that Duro does not invoke.