Skip to main content
Processes a payment using a previously saved card token. This endpoint is primarily used for recurring payments (MIT or CIT transactions). This endpoint may be exposed server-to-server for two-factor authentication flows, potentially requiring changes to authentication mechanisms. Recurring payment calls will originate only from the server. Fiscalization and eReceipt processes should also be operated during this flow

​
Request

Requests are performed to the /charge-token endpoint. 
{
  "basicInfo": {
    "requestType": 0,
    "entryMode": 1,
    "amount": 25.5,
    "currency": "EUR",
    "countryCode": "DE",
    "tokenModel": 1,
    "cvc": null,
    "token": "NAYAXTOK12345",
    "merchantRequestId": "MERCHANT_MIT_001",
    "transactionId": null,
    "transactionTimeUtc": null,
    "isSaveTokenWithoutConsent": false
  },
  "machineInfo": {
    "machineId": "0434334921100366"
  },
  "cardHolderInfo": {
    "cardholderEmail": "customer@example.com",
    "cardHolderUniqId": "unique_customer_id_123"
  },
  "additionalInfo": {
    "additionalData": "{\"loyaltyPoints\": 100}",
    "additionalReceiptData": "[{\"key\":\"product\", \"value\":\"Premium Service\"}]"
  },
  "validationKey": "AUTH_VALID_KEY_XYZ"
}

​
Request Parameters

The table below describes the parameters of the request:
ParameterLocationTypeDescriptionRequired
requestTypebasicInfoInt32Defines the transaction type (e.g., 0 for Sale/Charge).Yes
entryModebasicInfoInt32Defines how card data was obtained (e.g., 1 for E-commerce/MIT).Yes
amountbasicInfoDecimalThe monetary amount to be charged.Yes
currencybasicInfoStringThe three-letter ISO currency code.Yes
countryCodebasicInfoStringTwo-letter ISO country code of transaction origin.Yes
tokenModelbasicInfoInt32The specific tokenization scheme used. Token Type Behavior: A token’s type (subscription/COF/top-up) is set during its initial creation and stored in our system. If a subsequent Charge Token request includes a different token type parameter, it is ignored. The system always uses the original token type from the initialization request, regardless of what is provided in later charge requests.Yes
cvcbasicInfoStringnullCVC/CVV (usually null for tokenized MIT).Yes
tokenbasicInfoStringThe unique token representing the card to be charged.Yes
merchantRequestIdbasicInfoStringUnique ID generated by the merchant for this request.Yes
isSaveTokenWithoutConsentbasicInfoBooleanFlag for new token saving (usually false).Yes
machineIdmachineInfoStringUnique identifier for the transaction machine/terminal.Yes
cardholderEmailcardHolderInfoStringThe customer’s email address.Yes
cardHolderUniqIdcardHolderInfoStringA unique merchant ID for the cardholder.Yes
additionalDataadditionalInfoStringCustom data as a JSON string (e.g., loyalty info).No
validationKeyRootStringCryptographic key (HMAC) to authenticate the request.Yes

​
Response

A successful validation returns a 200 OK status and a body containing the validated merchant details: 
{
  "status": {
    "verdict": "Approved",
    "code": 0,
    "statusMessage": "Payment processed successfully."
  },
  "basicInfo": {
    "amount": 25.5,
    "currency": "EUR",
    "merchantRequestId": "MERCHANT_MIT_001",
    "transactionId": "NAYAXTRANS98765",
    "transactionTimeUtc": "2025-08-28T10:30:00Z"
  },
  "paymentInfo": {
    "amount": 25.5,
    "currency": "EUR",
    "nayaxTokenId": "NAYAXTOK12345",
    "siteId": 1,
    "providerTransactionId": "PSP_TRANS_ABC",
    "decimalPlace": 2
  }
}

​
Response Parameters

The table below describes the parameters of the response:
ParameterLocationTypeDescription
verdictstatusString’Approved’ or ‘Declined’. The final decision.
codestatusInt32Response code: 0 for Approved, otherwise the relevant decline code.
statusMessagestatusStringA descriptive message about the transaction outcome.
amountbasicInfoDecimalThe transaction amount processed.
currencybasicInfoStringThe currency of the transaction.
merchantRequestIdbasicInfoStringThe unique ID from the original request.
transactionIdbasicInfoStringThe unique transaction ID assigned by the Nayax system.
transactionTimeUtcbasicInfoDateTimeThe UTC timestamp when the transaction was completed.
nayaxTokenIdpaymentInfoStringThe token ID used for the charge.
siteIdpaymentInfoInt32The site ID associated with the payment.
providerTransactionIdpaymentInfoStringThe unique ID assigned by the Payment Service Provider (PSP).
decimalPlacepaymentInfoInt32The number of decimal places used for the currency/amount.