Neo Wallet Developers

Appearance

Changelog ​

Additive changes land under /api/v1; a breaking change ships as /api/v2 alongside it, with at least 90 days' notice. See Versioning.

v1 ​

Initial release.

  • Access — every request is signed with your API key and Ed25519 key; scopes decide what each route allows; every write takes an Idempotency-Key and an X-Request-Id; every error has the same shape.
  • Customers — onboard a customer with its main wallet; read the summary; manage identifiers, agreement acceptances and KYC level changes.
  • Wallets — balance and statement.
  • Money movement — wallet credits, wallet debits (customer present, or on a standing mandate), payouts, top-up intents and fee quotes.
  • Mandates — create, list, read and revoke.
  • Operations — list, status with timeline, and receipt.
  • Webhooks — 16 signed event types, retried for about 38 hours.

Added since the initial release:

  • Wallet profiles — POST /customers takes an optional rulesProfileKey, the wallet profile to open the customer's wallet on; omit it for your account's default. The customer responses return the rulesProfileKey the wallet opened on. A profile, KYC level (kyc.tierCode) or payment provider (railCode) your account is not approved for is refused with 422.
  • One person, several businesses — a 409 on POST /customers now means you already hold a customer with that verified identifier. The same person onboarded by another business on Neo Wallet is a separate customer there, and is not a conflict for you.