Billing

The Facturation (billing) page gathers everything to do with money for the workspace. The sandbox is free and asks for nothing: no sandbox request enters the accounts. A payment method is only needed for production; for Merchant API, it is required before your request is reviewed, since Noryo does not open a production it could not collect payment for.

The price of a Merchant API call in production is described in Merchant API billing. The sections below follow the order of the page.

Applicable pricing

Transaction Intelligence pricing is read, never written in advance: the page shows the customer pricing in force if there is one, and otherwise says why no amount is announced to you.

Two notices may follow. While the engine's accuracy is not certified, your production requests are served and recorded but are not billable. While Transaction Intelligence billing is not open, nothing is recorded for a customer workspace, nothing is collected, and no production key is issued.

Billing identity

This is the identity that appears on an invoice: company name or name of the person, address, and nature (legal entity or individual). It reuses the workspace's legal identity and is edited on the legal identity page, not here. See Legal identity and contract.

Payment method

Any member of the organisation can register or replace the payment method, in two steps.

11. Open the entry page

Click Ajouter un moyen de paiement (add a payment method), or Remplacer le moyen de paiement (replace the payment method) if one already exists. You are sent to a page hosted by our payment provider: the card is entered there, never on Platform.

22. Come back to Platform

When you return, the server rereads the session with the provider and checks that it concerns this workspace before saving anything. If you interrupt the entry, nothing is saved.

Noryo keeps no card number and shows no provider identifier. The page only says whether a payment method is registered, when it was observed, and the collection mode: automatic debit or on invoice.

Ability to bill

Below the payment method, the page says whether the system can establish and collect an amount due for this workspace, or why it cannot yet: billing not open, no billing identity with the provider, no payment method, automatic debit not enabled, legal identity incomplete, no applicable pricing, billing suspended. This ability is one of the conditions for a Transaction Intelligence production key. See Production access.

Current period

For production, the page shows when the period started, the number of billable requests, the units and the accumulated amount, including any carry-over from the previous period: a remainder below one cent is not lost, it is carried over. This amount is neither an invoice nor a debt. It only becomes an amount due when the period closes, and the closing is what counts.

If production requests that were served could not be entered in the accounts, the page gives their number and the date of the last one: they appear neither in these figures nor on an invoice.

Invoices and amounts due

Factures (invoices) lists the invoices issued for the workspace: period, amount, state with the provider and issue date.

Sommes dues (amounts due) gives the total outstanding, then the most recent amounts with their remaining amount, their initial amount, their status (open, partly settled, settled, overdue, deferred, written off, disputed), their dates and the last collection attempt. A failed debit settles nothing: the amount is still due.

What you will see on your statement

Very small amounts are not collected immediately: our payment provider defers them and collects them with the first invoice above its own minimum. An invoice may therefore appear settled in a month when nothing left your account. The total collected is still exactly the sum of what you used.

Further reading

• Usage: what is counted, without being billed.
• Merchant API billing: what is billable, and how to read usage.
• Production access: where the ability to bill comes in.