Skip to main content

Go live

You build and test your whole integration in the sandbox, Nodu's test environment, before you use production. Nodu gives you access to production after you have onboarded a customer and made at least one transfer in the sandbox with the integration flow agreed with Nodu.

Build the agreed integration flow in the sandbox​

First, agree with Nodu on the final functionality that your integration will use:

  • Onboarding. The onboarding model. With API onboarding, also the exact list of the fields and documents that an application needs.
  • Currencies and rails. The currencies and the payment rails on each side of a transfer: see Payment channels.
  • Other features. For example, Nodu wallets and relays.

Build the agreed integration flow in the sandbox. Before requesting production access, complete this checklist:

Use the sandbox to find and resolve problems before real customers and funds are involved.

Build the handling of failed transfers, and of the customer statuses suspended and blocked, from their descriptions: see Track and cancel a transfer and Suspended and blocked customers.

Make requests safe to repeat​

  • Idempotency keys. Send an Idempotency-Key header with every POST request that creates an object or moves money. Store the key and the exact body before you send the request: see Idempotency.
  • Client reference ids. Send your own identifier as clientReferenceId when you create a customer, an external account, a counterparty, a relay or a wallet. It helps you match API objects to your records and complements idempotency handling: see Idempotency.
  • Timeouts. Repeat a request that timed out with the same key and the same body. A new key can create a second object.
  • Errors. Handle errors by status, code and rule. Do not compare the text of title or detail. Handle a rule that you do not know: see Errors and rule codes.

Handle webhooks​

Receive and verify webhooks explains each of these items.

  • Signatures. Verify the signature of every webhook before you act on it.
  • Duplicates and order. Record the id of each event. Skip an event that you have already processed. Events can arrive more than once. They can also arrive out of order.
  • Unknown types. Return 2xx for an event type that you do not handle.
  • Reconciliation. Do not depend on webhooks alone. Compare your records with the API from time to time: see Reconcile with the list.

Handle every status and state​

Request access to production​

When your integration works in the sandbox:

  1. Ask Nodu for a production API key. Store it in a secret manager, and call the API from your backend only: see Environments and API keys and Authentication.
  2. Give Nodu the URL of your production webhook endpoint, and the list of event types that you act on. Nodu registers the endpoint. You receive its signing secret separately. Store the secret as carefully as an API key.

Production starts empty: none of your sandbox customers, external accounts, transfers or other objects exist there. You can keep using the sandbox for later tests and development.

A suggestion for production: start with one customer and one transfer of a small amount. Follow the transfer to its outcome before you offer this transfer flow to all your customers.

Next steps​