Skip to main content
POST
/
charge-token
curl --request POST \
  --url https://api.nayax.com/sdk/charge-token \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "basicInfo": {
    "amount": 25.5,
    "currency": "EUR",
    "countryCode": "DE",
    "requestType": 0,
    "entryMode": 1,
    "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"
}
'
{
  "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
  }
}
Processes a payment using a previously saved card token. This endpoint is primarily used for recurring payments (MIT or CIT transactions). Important: This endpoint might be exposed server-to-server for two-step flows, potentially requiring changes in authentication mechanisms. Recurring payment calls will originate from the server only. Fiscalization and eReceipt processes should also be operated during this flow. 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 from the server only. Fiscalization and eReceipt processes should also be operated during this flow.
Integration URLWhen performing your integration to the API use the stable URL, such as:
  • https: //stable-sdk-api.nayax.com/charge-token

Authorizations

​
Authorization
string
header
required

JWT RSA token required for authentication. The token should be included in the Authorization header as Bearer <token>. Nayax will issue tokens to the VAS, signed by a private key, and decrypt them using a public key.

Body

application/json

Request to charge a saved token for a payment.

Request body for processing a transaction (charge token, close transaction).

​
basicInfo
object

Basic transaction details.

​
machineInfo
object

Information about the machine/terminal.

​
validationKey
string | null

Validation key from the authentication flow.

Example:

"AUTH_KEY_FROM_VALIDATE"

​
cardHolderInfo
object

Cardholder details.

​
additionalInfo
object

Additional information for the transaction and receipt.

​
originalTransactionId
integer<int32>

Required for second-step transactions (e.g., refund, void). The original Nayax transaction ID.

Example:

123456

​
paymentInfo
object

Payment-related information.

Response

Success

Response body for a transaction (charge token, close transaction).

​
status
object

Transaction status.

​
basicInfo
object

Basic information about the transaction, including amount, currency, and merchant request ID.

​
paymentInfo
object

Payment-related information, including Nayax token ID if applicable.