Register fires immediately after Sale approval, before the product is dispensed.
Flow
The following sequence shows howRegister fits into the single sale flow:
- Consumer presents a card and selects a product at a known price
- Nayax Engine processes the Sale via the Payment Provider
- Nayax Engine sends
POST /FisCortina/Registerto your server - Your server registers the transaction and returns a response (must include
Verdict,FiscalRrn, andFiscalId) - Product is dispensed
Exception handling
BecauseRegister fires before dispensing, a failed fiscal registration can optionally trigger a transaction cancellation (disabled by default; contact your Integration Engineer to enable):
Request field notes
PaymentInfo.AuthDateTime uses a 12-digit format for card transactions. MachineAuTime and MachineSeTime always use 17 digits:
BasicInfo.TransactionId is always present for card transactions. It may be short (11 digits) or long (36 digits, zero-padded):
Next steps
Void
Un-register a transaction when a product is not dispensed.
Request & Response Reference
Full field definitions and response codes for all endpoints.