Table of Contents

Namespace NuvTools.Payment.Omie.ApiClient

Classes

DependencyInjection

Extensions to register the Omie API client in the DI container.

OmieFaultClassifier

Classifies Omie failure messages so callers can react programmatically (e.g. switch an OS create to an update when the integration code already exists) instead of string-matching Omie text themselves. This component surfaces faults as failed IResult (it deliberately does not throw — see the comment on OmieApiClient._staticClient), so the markers live here in one place.

VERIFY (Omie test app): confirm the exact faultstring wording for the duplicate-integration-code and not-found cases against the current Omie responses and adjust the markers below if needed.

OmieOrderStage

The service order stage (cEtapa) in Omie. The API documents five values — 10, 20, 30, 40 and 50 (invoice) — but an account may have its own Kanban columns, and the query returns the real stage (60 has been seen). Echoing that stage back on a change means sending a value outside the domain the API accepts; since cEtapa is optional on AlterarOS, the right move is to omit it and leave the order where it is.

OmiePaymentTerm

The payment term code (cCodParc) of a service order in Omie. It is not a preference: it tells Omie whether the installments come from a registered payment condition or from the request itself.