Overview
What Platform is, how you sign in with your Noryo identity, what the workspace created when you open it contains, and who can do what depending on their role.
Platform, at https://platform.noryo.app, is where you manage your account for Noryo's APIs: Merchant API and Transaction Intelligence. You create and revoke keys there, read usage, fill in what each step requires, and follow your production access requests and billing. How the APIs work is described on this portal; Platform answers a different question: where your account stands.
Platform's screens are in French. This guide quotes their labels as displayed, with their meaning in English.
1. Sign in
Platform has no sign-in page of its own, and no password is ever typed there. Open https://platform.noryo.app and follow Continuer vers la connexion (continue to sign-in): you identify yourself with your Noryo identity on the authentication portal, https://auth.noryo.app, which then brings you back to the page you asked for.
2. Open Platform on your identity
If your Noryo identity does not have access to Platform yet, the page says so and offers Ouvrir Developer Platform (open Developer Platform). There is no second account to create and no second password: only an access to add to your identity, on the authentication portal.
3. Find your workspace
When that access is opened, if you are not yet a member of any organisation, Platform creates one for you, with a workspace of the same name, and makes you its owner. The organisation is given a default name, "Mon organisation" (my organisation): the real name is set in the developer profile. No key is created at that point; a key is always a deliberate action.
If you are already a member of an organisation, nothing new is created. An account that is a member of no organisation sees the "Aucun espace marchand" (no merchant workspace) page: it is not a fault.
Organisation, workspace, members
An organisation is the API customer. A workspace belongs to an organisation: it carries the keys, the usage, the profiles, the production access requests, the accepted contract and the billing. The Overview page shows, at the top, the organisation's name, the workspace's name, the environment (Sandbox) and your role.
You are a member of an organisation with a role, and that role applies to its workspaces. Platform offers no screen to invite a member or change a role.
Who can do what
There are five roles: owner, admin, developer, billing and viewer. Every member can see the pages, the keys, the usage and the states; actions depend on the role.
| Action | owner | admin | developer | billing | viewer |
|---|---|---|---|---|---|
| Create or revoke a Merchant API sandbox key | yes | yes | yes | yes | yes |
| Enable the Transaction Intelligence sandbox | yes | yes | no | no | no |
| Create or revoke a Transaction Intelligence sandbox key | yes | yes | yes | no | no |
| Fill in the developer profile | yes | yes | no | no | no |
| Fill in the legal identity, answer a supporting-item request | yes | yes | no | no | no |
| Accept the Transaction Intelligence contract | yes | yes | no | no | no |
| Submit, complete or withdraw the Transaction Intelligence production access request | yes | yes | no | no | no |
| Create a Transaction Intelligence production key | yes | yes | no | no | no |
| Submit the Merchant API production request | yes | yes | yes | yes | yes |
| Add or replace the payment method | yes | yes | yes | yes | yes |
| Pass on an end-user correction | yes | yes | yes | yes | yes |
Every action is checked by the server, from your identity and your membership; the workspace identifier a page carries only selects, it never authorises. A page only offers an action to someone the server would grant it to, and any refusal is shown exactly as the server words it.
The pages of Platform
| Page | What you do there |
|---|---|
| Vue d'ensemble (overview) | The organisation, the workspace, your role, the Merchant API sandbox allowance, recent calls and the Merchant API production state |
| Clés d'API (API keys) | Enable the Transaction Intelligence sandbox, create and revoke keys. See API keys |
| Usage | Read each product's usage. See Usage |
| Retours (feedback) | Pass on a correction reported by one of your users. See Feedback and corrections |
| Facturation (billing) | Pricing, billing identity, payment method, invoices and amounts due. See Billing |
| Profil développeur (developer profile) | The profile that opens the Transaction Intelligence sandbox. See Developer profile |
| Identité juridique (legal identity) | Who accepts the contract, from which address, and the supporting items requested. See Legal identity and contract |
| Contrat (contract) | The Transaction Intelligence contract in force and its acceptance |
| Mode Production (production mode) | The Merchant API production request. See Production access |
| Production Transaction Intelligence | The Transaction Intelligence production access request and its conditions |
When the workspace is unavailable
If the workspace, or the organisation it belongs to, is not active, Platform says so and names the cause, organisation first: a suspended organisation makes all of its workspaces unavailable, and fixing the workspace would change nothing. Actions are then refused, existing keys stay listed, and a request made with an intact key receives 403 account_inactive. This is not a revocation, and creating a new key changes nothing: it is resolved with Noryo. See account_inactive.
Further reading
- Developer profile: what it contains and what it opens.
- API keys: the life cycle of a key, for both products.
- Merchant API quickstart and Transaction Intelligence quickstart: from the key to the first call.
Published on 2026-10-09 10:17 UTC (version 1).