Skip to main content
Cortina uses the SaleEndNotificationcommand to notify the integrator about the completion of the transaction request with the Cortina payment provider.

Request

Nayax’s servers send a POST request to your configured SaleEndNotificationendpoint, which would be of the following format: (customer's URL)/Cortina/SaleEndNotification The payload includes the following details:
{
  "BasicInfo": {
    "TransactionId": "N99O4XURDQYJZIK4OTCAWF1RHHA40TZWVCRB",
    "NayaxTransactionId": 3584697384,
    "Amount": 5,
    "CurrencyCode": "ILS",
    "CurrencyNumeric": "376",
    "SiteId": 1,
    "MachineAuTime": "071221132914",
    "TimeoutMS": 15000,
    "IsProductSelected": true,
    "PaymentMethodID": 1,
    "BillingProviderId": 1,
    "AuditNumber": 342,
    "NayaxRRN": "111111",
    "IsDeferredAuthorization": true,
    "AgeLimitation": 18,
    "IsSoftDeclineCompletion": true,
    "TransitElement": {
      "TransitTransactionType": 1,
      "DenyListIndication": 0
    }
  },
  "PaymentInfo": {
    "SrvTranId": "3584697388",
    "AuthCode": "333333",
    "AuthAmount": 5.5,
    "SettAmount": 5.5,
    "RRN": "111111",
    "Token": "string",
    "AuthDateTime": "071221133300",
    "SettDateTime": "071221133330",
    "TraceNumber": "4444",
    "AuthSource": "string",
    "AdditionalData": "string",
    "IsGatewayTimeout": false,
    "ProviderExternalData": "string",
    "InitiateTranReference": 11223344,
    "IsRevalueCard": false
  },
  "DynamicURL": "string",
  "CustomData": {
    "DirectActor": "String",
    "Operator": "String",
    "Distributor": "String",
    "Actor": "String",
    "Machine": "String",
    "SoftDecline": "String"
  }
}

Request Parameters

The table below describes all the parameters of the request:
FieldTypeRequiredDescription
BasicInfoTransactionIdString(36)YesThe unique identifier for this transaction.If /StartSession has been used then this will echo the transaction Id encrypted in ‘TranIDCipher’.
If /StartSession was not Used - Nayax Engine shall generate this Value.
NayaxTransactionIdInt(64)YesNayax Internal Unique identifier for the transaction which will be echoed in further requests.
AmountDoubleYesDecimal (max 3 digits for cents)
The amount of the payment Example: 1 cent = 0.01, 20 cents = 0.20
  • Note: Currencies with no Decimal Place shall be represented as double as well.
    Example: 234 JYN = 234.0.
CurrencyCodeString(3)YesCurrency according to ISO4217 Attribute format: Alpha-3.
CurrencyNumericString(3)YesCurrency according to ISO4217 Attribute format: Numeric-3.
SiteIdInt(16)NoRegion of the Nayax server.
MachineAuTimeStringNoMachine Authorization Timestamp
TimeoutMSInt(32)NoNayax Server T/O configuration, in milliseconds
IsProductSelectedBoolNoindication if the product was pre-selected
PaymentMethodIDInt(32)NoNayax identifier of the payment provider
BillingProviderIdInt(32)NoNayax identifier of the billing provider
AuditNumberInt(64)NoFor Nayax internal use only.
NayaxRRNStringNoReference to generate Nayax Number, Used as External Transaction Identification for external parties (Usually Card schemes, or App service providers).
From support perspective - It is highly recommended that this ID shall be the one visible to the end consumer/Card holder and the card’s Issuer (e.g. Bank) or Application service provider (e.g. Alipay, WeChat).
If none of the above is applicable, the Integrator shall generate an additional String.
  • This Value shall be echoed in the /Inquiry request.
IsDeferredAuthorizationBoolNoFurther information is unavailable.
AgeLimitationInt(16)NoMinimum age required to allow the transaction.
IsSoftDeclineCompletionBoolNoFurther information is unavailable.
TransitElement inside BasicInfoTransitTransactionTypeInt(32)NoEnum: 1 2 3 71 - Prefunded2 - Realtime Authorization3 - Post-Authorization
Aggregated Transaction
7 - Debt Recovery
TransitElement inside BasicInfoDenyListIndicationInt(32)NoEnum: 0 1 20 - unknown/ no effect1 - Decline will cause consumer
to be added to the deny list
2 - Approval shall cause the consumer to be removed from deny list.
PaymentInfo SrvTranIdStringNoThe Integrator’s internal transaction id.Conditional, only if /StartSession was not Used.If /StartSession was used, this should be either empty or Echo the Transaction ID sent in the request.
AuthCodeString(40)NoExternal (usually Card issuer’s) Authorization Code
AuthAmountDoubleNoThe original amount requested in /Authorization requested.
SettAmountDoubleNoThe original amount requested in /Settlement or /Sale process.
RRNStringNoReference Retrieval Number, Used as External Transaction Identification for external parties (Usually Card schemes)
From support perspective - It is highly recommended that this ID shall be the one visible to the end consumer/Card holder.
TokenString(256)NoA unique token for the transaction. For Internal Nayax use only
AuthDateTimeStringNoThe date time string of when the /Authorization took place Format: ddMMyyHHmmss
SettDateTimeDoubleNoIrrelevant for the Authorization command.
TraceNumberStringNoTrace number. For Internal Nayax use only
AuthSourceString(5)NoFor Internal Nayax use only
AdditionalDataStringNoString in JSON format.
Contact Nayax TPOC on order define.
IsGatewayTimeoutBoolNoWas there was a gateway timeout (valid in response)
ProviderExternalDataStringNoString in JSON format.
InitiateTranReferenceInt(64)NoConditional, in case of re-attempt of using a prepaid loyalty card on a terminal in a given transaction, this field will reflect which transaction (Nayax Transaction ID) this attempt originally belongs to.
IsRevalueCardBoolNoIndication if card is allowed revalue
BasicInfoDynamicURLStringNoActor level URL configuration
CustomDataDirectActorStringNoDirect actor custom data (String in json format)
OperatorStringNoOperator custom data (String in json format)
DistributorStringNoDistributor custom data (String in json format)
ActorStringNoActor custom data (String in json format)
MachineStringNoMachine custom data (String in json format)
SoftDeclineStringNoSoft Decline custom data (String in json format)

Response

The SaleEndNotification Response that the customer’s payment method would send to Nayax’s servers.
The payload should look as follows:
{
  "Status": {
    "Verdict": "string",
    "Code": 0,
    "StatusMessage": "string",
    "CustomDeclineCode": "string"
  }
}

Request Parameters

The table below describes all the parameters of the request:
FieldTypeRequiredDescription
TranIDCipherString(36)YesThe Integrator Generates transaction ID of 36 Chars (or 288 bits). The Integrator then appends the char = and RandomNumber to create the ciphertext of 64 chars Format TransactionId=RandomNumber The integrator encrypts the ciphertexts with the Secret Token in AES ECB. The AES key will be the last (right most) 256 bits (or 32 chars) of the Secret Token the matches the TokenID provided in the request. Nayax will AES ECB decrypt and extract transaction id The transaction Id value will then be used for all further requests.Information regarding how to generate the TranIDCipher (via encrypting the token alongside the Random Number and the customer’s Transaction ID can be reviewed under Start Session authentication process
Verdict inside StatusStringYesConst string.
Status of the request (‘Approved’/‘Declined’)
Code inside StatusInt(32)NoConditional - Only if verdict value is declined.Valid decline codes (must be a code from this list):
1 - Insufficient funds
2 - Transaction ID unknown
3 - Cardholder exceeded daily / weekly / monthly transaction count limit
4 - Cardholder exceeded transaction amount limit
5 - Suspected Fraud
6 - General system failure
7 - Invalid amount
8 - Request cannot be parsed (format error)
9 - Transaction not allowed to cardholder
40 - For Nayax internal use only.
990 - CertificateFileName not found
991 - Failed to decipher message body
992 - Timeout exception
994 - Card Brand not supported
996 - Transaction ID Unknown / Duplicate Transaction ID (Start Session Error)
997 - Missing mandatory parameters
998 - Validation / request cannot be parsed
999 - General exception
1010 - Public Key Certificate not found
1011 - Method not Implemented
StatusMessage inside StatusString(255)NoTransaction status message free text field / additional varying data
CustomDeclineCode inside StatusStringNoThis field is used for specifying a custom decline code (i.e. Soft Decline or Switch Interface). The value might be the same as the acquirer’s response code or composed by other data.