Skip to main content

How Nodu works

Nodu moves money for your customers between bank accounts and crypto wallets, and converts it between currencies on the way. Every integration involves three parties and a few API objects. It also makes two choices: how you onboard customers, and which money flows you offer.

The parties​

PartyRole
YouThe company that integrates with Nodu. You build the interface that your customers use. Your backend calls the Nodu API. It also receives webhooks from Nodu.
Your customersThe people and businesses that you onboard and move money for. They use your interface. In some integrations, they also use pages that Nodu hosts.
NoduNodu verifies each customer, unless it relies on your own checks. It receives payments. It reviews each transfer. It converts the funds. It pays the recipient.

The objects​

ObjectWhat it isWhere to read more
CustomerThe person or business that you onboard and move money for.How onboarding works, and customer statuses
Payment channelA currency and rail on which a customer can pay in or be paid out. A rail is a bank payment scheme or blockchain network that carries the money.Payment channels
External accountA bank account or crypto wallet outside Nodu that you register for transfers. It belongs to the customer (a first-party account) or to someone else (a third-party account).External accounts and counterparties
TransferA movement of money for one customer, from a source to a destination.How transfers work
Nodu walletA balance held at Nodu, in one or more currencies.Nodu wallets: balances and wallet scopes

How the objects connect​

This sequence shows a pay-as-you-go transfer to an external account. Nodu wallets separate funding from payouts; relays provide reusable deposit instructions.

  1. You create a customer. The customer accepts Nodu's Terms of Service. Nodu verifies the customer, or relies on your own checks. The customer can transact when the customer has status=active.
  2. The customer's payment channels show the currencies and rails that the customer can use.
  3. You register an external account for the customer. It is the bank account or crypto wallet that a transfer pays out to.
  4. You create a quote. You show the customer the amounts and the fees. The customer confirms.
  5. You create a transfer with a source and a destination. Nodu returns deposit instructions, which say where the customer sends the money.
  6. The customer pays. Nodu reviews the transfer. If the source and destination currencies differ, Nodu converts the funds. Nodu then sends the payout.

Nodu sends a webhook event when a customer, a payment channel or a transfer changes: see Receive and verify webhooks.

The two choices​

An onboarding model​

An onboarding model decides where the customer accepts the terms and completes verification:

  • Hosted onboarding. The customer uses pages that Nodu hosts. You redirect the customer to them.
  • API onboarding. The customer stays in your interface. You collect the information and documents. You then send them to Nodu.

In both models, Nodu reviews the customer and makes its own decision. Under a respondent agreement, Nodu relies on your own checks instead: see Respondent onboarding. Onboarding models compares the models.

The money flows​

With pay-as-you-go transfers, each payment funds one transfer. Nodu wallets extend this flow by letting you hold a balance and fund payouts from it. An integration can use both. The available capabilities, currencies and rails depend on your integration agreement with Nodu.

Pay-as-you-go​

Each transfer is funded by its own payment. The customer pays Nodu, and Nodu pays the recipient:

  • On-ramp: fiat in, stablecoin out. The customer sends a bank payment. Nodu pays a stablecoin to a crypto wallet.
  • Off-ramp: stablecoin in, fiat out. The customer sends a stablecoin. Nodu pays fiat money to a bank account.
  • Crypto swap: crypto in, crypto out. The customer sends crypto. Nodu pays crypto to a crypto wallet.
  • Fiat cross-border: fiat in, fiat out. The customer sends a bank payment. Nodu pays fiat money to a bank account, for example in another currency.

How transfers work explains these flows.

Using Nodu wallets​

A Nodu wallet is a balance held at Nodu. It works as an intermediate account between payments in and payouts. A transfer can pay into a Nodu wallet, and a transfer can pay out from it:

  • A payment in adds to the balance of the Nodu wallet.
  • A payout draws from the balance. It does not wait for a payment of its own.

A payment in and a payout therefore do not need to match one to one. A Nodu wallet can be attached to your company or to one customer, and this allows different arrangements. For example, one Nodu wallet of your company can hold the funds of all your customers, an arrangement often called an omnibus or pooled account. Or each customer can have a Nodu wallet of their own, which keeps that customer's funds apart. Agree the arrangement that suits your business with Nodu.

See Nodu wallets: balances and wallet scopes and Fund and pay out from a Nodu wallet.

Two more topics affect what you build:

What is available to you​

The onboarding models, the types of customer, the currencies, the rails and the other features that you can use depend on your integration agreement with Nodu. The API returns what is available to a customer. For example, List payment channels returns the customer's currencies and rails.

Guides and the API reference​

The guides explain which calls you make, in what order, and why. The API reference describes every operation, field and value.

Next steps​