Constant transaction values

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:

Card type (cardType)

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

NameValue
Visa10
MasterCard20
Discover30
American Express40
Unknownnull

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.

ValueNameDescription
1InitialThe chargeback is in the first state.
2WonThe dispute was given in your favor.
3RepresentThe chargeback has gone through the first initial, won, and has been re-presented to the card brands by the customer.
4FinalThere is a final decision for the chargeback.
0CanceledThe dispute was canceled.

📘

Notes

  • Representment is when the chargeback is at the decision stage for the chargeback department. This does not only happen in the third stage: it can happen in the second or final stage, as well. It also does not mean the funds are for sure going to the customer. The merchant may have to wait for the chargeback department to update the chargeback, but they still have the possibility of winning it.
  • 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.

NameValue
Credit1
Debit2
Charge card3
Unknown4

Currency ID (currencyId)

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

NameValue
Australian Dollar036
Canadian Dollar124
Yuan156
Yen392
Won410
Mexican Peso484
Pound Sterling826
US Dollar840
Euro978

Payment type (paymentType)

A payment type indicates the type of transaction being processed using stored payment credentials. This field is important to properly flag initial and subsequent transactions. Please note that cardholder authentication (3D Secure) may be required depending on card issuer requirements.

You may 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.

Payment TypeDescription
initialScheduledIndicates a customer-initiated first transaction in a series of scheduled or recurring transactions. For subsequent transactions, use scheduled.
initialUnscheduledIndicates a customer-initiated first transaction that is not part of a series of scheduled or recurring transactions. For subsequent transactions, use either unscheduledCit or unscheduledMit.
scheduledIndicates a merchant-initiated subsequent transaction in a series of scheduled or recurring transactions.
unscheduledCitIndicates a customer-initiated subsequent transaction that is not part of a series of scheduled or recurring transactions.
unscheduledMitIndicates a merchant-initiated subsequent transaction that is not part of a series of scheduled or recurring transactions. Customer consent was provided at the time of the initial payment.
motoIndicates a merchant-initiated subsequent transaction that is not part of a series of scheduled or recurring transactions. Customer consent is provided at the time of the subsequent transaction.

Payment type flow

29782978

Payment Type Flow

Example request

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:

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

NameValue
Card10
Card Present11
Card Not Present12
APM (Alternative Payment Method)20
Echeck40
Credit50
Cash60

Transaction status (transactionStatus)

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

📘

Note

Card transaction status

StatusDescriptionNexio Dashboard StatusTransaction Service transactionStatusPayment Service transactionStatus
Auth Only PendingThe payment is asynchronous and may receive a webhook notice with a status of authOnly in the futureAUTHONLYPENDING3authOnlyPending
Authorized PendingThe payment is asynchronous. The payment is pending and may receive a webhook notice with status of settled in the futureAUTHORIZEDPENDING9authorizedPending
AuthorizedThe transaction has been successfully authorized and is pending settlementAUTHORIZED10pending
Auth OnlyThe payment is Auth Only and capturing is required to receive the funds. The transaction can also be voidedAUTHONLY11authOnly
DeclinedThe transaction was declinedDECLINED30declined
Fraud RejectThe transaction was declined by Kount prior to being submitted to the gatewayFRAUDREJECT32fraudReject
SettledThe transaction is settled. It can be refunded but not voidedSETTLED20settled
Void PendingThe payment is asynchronous and may receive a webhook notice with a status of voided in the futureVOIDPENDING39voidPending
VoidedThe payment has been voidedVOIDED40voided
ErrorAn error has occurredERROR50error

Echeck transaction status

StatusDescriptionNexio Dashboard StatusTransaction Service transactionStatusPayment Service transactionStatus
PendingThe transaction is pendingPENDING12pending
SettledThe transaction is settledSETTLED20settled
SubmittedThe payment was submitted to the bank for authorizationSUBMITTED13submitted
RejectedThe transaction was rejectedREJECTED33rejected

Transaction type (transactionType)

NameValue
Sale10
Refund20

Did this page help you?