When working with and querying transaction data, the following numerical values are returned which represent the corresponding constant value.

This page has the following reference tables for constant values:

• cardType
• chargebackCycle
• class
• currencyId
• paymentType
• processMethod
• recoveryStatus
• transactionStatus
• transactionType

Card type (cardType)

The Nexio cardType parameter is used with the View transactions endpoint in the request and returned as a number in the response. You can only send values for 10, 20, 30, 40, and 50. And in the response, you will only get those values or null, depending on the card used in the transaction.

Chargeback cycle (chargebackCycle)

The Nexio chargebackCycle parameter is used with the View a chargeback and View chargebacks endpoints.

This value includes what part of the cycle the chargeback is currently in.

📘

Note

To check the status of a chargeback, you should get in direct contact with the chargeback department. You can also get information in the Nexio dashboard, but it may not be as up-to-date.

Class (class)

The Nexio class parameter is used with the View transactions endpoint. It is part of the cardMetaData object and refers to the category of card used in the transaction.

Currency ID (currencyId)

The Nexio currencyId parameter is used with the View transactions endpoint.

Payment type (paymentType)

A payment type indicates the type of transaction being processed using stored payment credentials. This field is required to properly flag initial and subsequent transactions. Also, sending an incorrect value may result in fines to the merchant account from card schemes (Mastercard, Visa, and so forth). Please note that cardholder authentication (3D Secure) may be required depending on card issuer requirements.

Nexio defaults to initialUnscheduled for any of the following:

• When the security code is presented with the Run card transaction with iframe endpoint
• Retail keyed transactions (see Running a keyed transaction with the iframe)
• Retail terminal transactions (see Processing a transaction with a terminal)
• Virtual terminal transactions made in the Nexio Dashboard.

Nexio defaults to initialScheduled for any of the following:

• Initial transactions made through the Subscriptions service (see the Create a subscription endpoint)
• When the security code is presented with the Run card transaction endpoint
• When sending full card number (card.pan) with the Run card transaction endpoint

Nexio defaults to scheduled for the following:

• When no security code is presented with the Run card transaction endpoint
• When sending full card number (card.pan) and recurringId with the Run card transaction endpoint

🚧

Important

Because Nexio sends a default, if you do not pass the paymentType parameter and rely on the default value, any mislabeled paymentType that results in declines, non-compliance, and/or fines will be the responsibility of the merchant.

You indicate a payment type when you run a card transaction by including processingOptions.paymentType in the body of your request. See the table below for possible values and explanations.

Subsequent transactions

When we say "subsequent" transactions, we mean transactions that are meant to occur after a first transaction as part of a subscription or recurring situation where the customer is not present for that next transaction and you use a saved card token for that subsequent transaction.

This is not the same as a case where a customer would make a purchase once and then again in the future, whether with or without a saved card token. For those, each payment is either an initial transaction (initialUnscheduled or initialMoto) if getting the information from the customer directly each time, or an unscheduled transaction when using a saved card token after that first one (unscheduledCit if the customer selects their saved card or unscheduledMit if the merchant is running the transaction).

Otherwise, on subsequent transactions with a saved card token, use a paymentType of one of the following, depending on the situation:

• unscheduledMit - The cardholder calls in to make a payment with a "card on file", regardless of the paymentType used for the initial transaction.
• unscheduledMit - For situations like a cancellation or no-show fee that the merchant initiates.
• scheduled - When a cardholder enrolled in a series of payments.

Payment type flow

Example request

curl -X POST https://api.nexiopaysandbox.com/pay/v3/process \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json' \
  -H 'Authorization: Basic [Base64_encoded_login]'
  -d '{
  "data": {
    "amount": 1.15,
    "currency": "USD"
  },
  "tokenex": {
    "token": "6ee140a0-05d1-4958-8325-b38a690dbb9d"
  },
  "processingOptions": {
    "paymentType": "initialScheduled"
  }
}'

Process method (processMethod)

The processMethod parameter gets returned with these endpoints:

• View transaction by transaction ID
• View transaction by payment ID
• View transactions

The following table shows the possible values and what process method the code corresponds to:

Recovery status (recoveryStatus)

The table below describes the recovery statuses for transactions.

Transaction status (transactionStatus)

The tables below describe the transaction statuses for card and echeck transactions.

📘

Note

• The transactionStatus returned by the Payment service, including the Alternative payment method service will be a string.
• The transactionStatus returned by the Transaction service will be an integer.

Card transaction status

Echeck transaction status

Transaction type (transactionType)