Merchant API
Turn a bank transaction descriptor into a merchant identity: three routes, measured behaviour.
Noryo developer documentation
Guides, references and resources to build Noryo APIs into your products.
APIs
Pick an API: each one has its guide, a reference generated from OpenAPI, and its errors.
Transaction Intelligence
Enrich transactions: counterparties, types, relationships, recurring series and coverage.
Let's get you started
First steps, from a sandbox key to your first authenticated call.
Merchant APIQuickstartOne enrichment end to end in Sandbox: create, replay, read back, refresh, then trigger an error, with the API's real responses.Merchant APIAuthenticationHow to present an API key, what the server checks, why every refused key gets the same 401, and which scopes open which routes.Transaction IntelligenceQuickstartFrom a Noryo identity to a first enrichment read back: enable the sandbox, create a key, call the API with curl and TypeScript, then check usage on Platform.Transaction IntelligenceSandbox, usage and productionWhat the sandbox offers and does not promise, what Platform counts and how to manage keys, then how production access is requested.
Use cases
The integrations the documentation covers today, guide by guide.
Enrich a transactionSend a raw transaction to POST /transactions/v1/enrichments and read what the response asserts, ignores or refuses.Counterparties and entitiesHow identity resolution names a counterparty, what the entity graph keeps apart (brand, legal entity, intermediary) and what is deliberately left unresolved.Recurring seriesWhat a series (
series[]) is, why its identifier stays stable, and how to read status, cadence, calendar_pattern and history_coverage.RelationshipsHow Noryo links two transactions of the same workspace through a refund_of, reversal_of or transfer_pair relationship, and how to read its role, its corroborations and its abstentions.Observation coverageDeclare what you supplied for an account over a period, so that a missing due date can be read as a miss rather than as an unknown.Production accessThe sandbox opens on its own once your developer profile is complete; production is requested, reviewed by Noryo and decided. What the request contains, what an approval does, and the three conditions that come after.Useful resources
The machine contract, your workspace, service status and help.
OpenAPI specificationsThe machine contracts of Noryo APIs, as served in production. They power this portal's reference.Developer PlatformAPI keys, usage, production access(opens in a new tab)Service statusAvailability and incidents(opens in a new tab)Help centreContact and support(opens in a new tab)