Authorization + Settlement

Authorization and settlement are separate calls. Register fires after Nayax confirms Settlement, after the product has already been dispensed.

Flow

The following sequence shows how Register fits into the authorization and settlement flow:

Consumer presents a card and selects a product; Nayax Engine sends an Authorization request
Authorization approved; product is dispensed
Nayax Device sends a Settlement Command; Nayax Engine confirms Settlement
Nayax Engine sends POST /FisCortina/Register to your server
Your server registers the transaction and returns a response (must include Verdict, FiscalRrn, and FiscalId)

Because Register fires after dispensing, a failed registration cannot cancel the transaction. Failures at this stage are queued for retry:

Scenario	Step	Resolution
Authorization failed	1	Nayax aborts the transaction. No `Register` call fires. Nayax does not dispense the product or charge the cardholder.
Vend failed (product not dispensed)	2	Nayax cancels the transaction. No `Register` call fires. Nayax does not dispense the product or charge the cardholder.
Settlement failed	3	Nayax logs for manual reconciliation. `Register` does not fire if Settlement does not confirm.
Registration declined	4–5	Registration fails with no fiscal processing unless Retry is enabled.
Registration timeout	4–5	Same as above. If Retry is enabled, FisCortina continues retrying within the configured window.

PaymentInfo.AuthDateTime uses a 12-digit format for card transactions. MachineAuTime and MachineSeTime always use 17 digits:

Field	Format	Digits	Example
`PaymentInfo.AuthDateTime`	`YYMMDDHHmmss`	12	`230226093406`
`BasicInfo.MachineAuTime`	`YYYYMMDDHHmmssfff`	17	`20260223093406383`
`BasicInfo.MachineSeTime`	`YYYYMMDDHHmmssfff`	17	`20260223093550020`

BasicInfo.TransactionId is always present for card transactions. It may be short (11 digits) or long (36 digits, zero-padded):

Format	Example
Short (11 digits)	`23083406429`
Long (36 digits)	`000000355897454624064012793151470385`