Production access
Where each product's production access is requested on Platform, what you follow without being able to move it forward, and the nine conditions for a Transaction Intelligence production key.
On Platform, production is not obtained through any self-service action. Each product has its own request, which Noryo reviews and decides on; you follow its state and history without being able to move it forward yourself. Starting a review, asking for more information, approval, rejection, suspension and revocation are internal Noryo actions: they do not exist on your side. Approving one product's request does not approve the other's.
Two products, two requests
| Merchant API | Transaction Intelligence | |
|---|---|---|
| Page | Mode Production (production mode) | Production Transaction Intelligence |
| Who submits | Any member of the organisation | An owner or an admin |
| Prerequisite | A registered payment method, required before the review | A complete developer profile, required at submission |
| Draft | No: the request is submitted in one go | Yes: saving submits nothing |
| Evidence of the product | The product URL or, failing that, at least one screenshot given by its URL | The product or site URL, optional |
| Production key created on Platform | None | nry_txn_live_…, once the nine conditions are met |
| Request details | Going live | Production access |
Merchant API: the production mode request
On the Mode Production page, you submit a request: legal identity, contact email and phone, product URL or screenshots, estimated volume and use case. Once it is submitted, the form gives way to the request's state (submitted, in review, approved, rejected or suspended), its dates, the reason for the decision and the history of its steps. The payment method is registered on the Billing page. See Billing and Going live.
Transaction Intelligence: from request to production key
The Production Transaction Intelligence page opens with "Où en est cet espace de travail" (where this workspace stands), a single state derived from what the server returns, followed by the list of what still prevents a production key from existing.
1. Prepare the request
An owner or an admin fills in the form, once the developer profile is complete and the workspace is active: legal identity, product URL, production use case, expected volume and users, countries and markets, data sources, integration architecture and production contact. Enregistrer le brouillon (save the draft) keeps your work without submitting anything. The form accepts no document. What each field expects is described in Production access.
2. Submit the request
Déposer la demande (submit the request) sends it for review. What is submitted is frozen: it is what Noryo reviews, and the server refuses to change it. While the request is editable, as a draft or after a request for more information, the page also offers to withdraw it, with an optional reason.
3. Follow the review
The request moves through the following states: draft, submitted, in review, more information requested, approved, rejected or withdrawn. When Noryo asks for more information, its message is shown on the page and the request becomes editable again: complete it, then submit it again. The history lists each step with its date, in UTC, and its reason.
Decision reasons form a closed list: approved, identity not verifiable, product missing or inaccessible, use outside the contract, inconsistent volume, incompatible data sources, insufficient compliance, incomplete request, suspected fraud, other.
4. Meet the conditions that follow approval
An approval is one of the nine conditions for a production key, not the last one. The page lists them one by one, with a Y aller (go there) link when the condition is met on Platform, and the server rereads them at every issuing attempt.
| Condition | Where it is met |
|---|---|
| Access request approved | Noryo's decision on the request |
| Legal identity complete | Identité juridique (legal identity) |
| Contact phone verified | Profil développeur (developer profile), on the designated person's identity |
| Verification items settled | Identité juridique, "Justificatifs demandés" (supporting items requested) section |
| Applicable contract accepted | Contrat (contract), by an owner or an admin |
| Ability to bill | Facturation (billing): it is observed, not decided |
| Authorisation not suspended | A suspension is resolved with Noryo |
| Authorisation not revoked | A revocation cannot be undone: a new decision by Noryo is needed |
| Workspace and organisation active | Resolved with Noryo |
For an organisation, the verified phone is that of the production contact: a person in the organisation carries that number on their Noryo identity, has it verified there, then has it recorded from their developer profile. For an individual, it is their own number. A verification item already provided and under review blocks nothing. See Developer profile and Legal identity and contract.
5. Create the production key
The Créer une clé de production (create a production key) button only appears when the server confirms that production can open for this workspace: the nine conditions met, a live production authorisation, an owner or admin role, and the maximum number of active production keys not reached. Otherwise, the page names what stands in the way.
Creation follows the same rules as for a sandbox key: a name to help you find it, one intent per form, a secret shown only once. Every production request rereads the production authorisation: suspending it shuts traffic off immediately.
Today, Transaction Intelligence billing is not open: no customer workspace has the ability to bill, and no production key can be issued, whether or not the request is approved. The page says so plainly.
Further reading
- Legal identity and contract: two of the nine conditions.
- Billing: the ability to bill and the payment method.
- Transaction Intelligence production access: the request, the frozen snapshot, what an approval does.
- Merchant API going live: the request, the review and what changes in your code.
Published on 2026-10-09 10:17 UTC (version 1).