---
title: "View echeck token details"
method: GET
path: "/pay/v3/vault/echeck/{echeckToken}"
tags: ["Ecommerce"]
---

# View echeck token details

`GET /pay/v3/vault/echeck/{echeckToken}`

## Request

- Base URL: `https://api.nexiopaysandbox.com`
- URL: `https://api.nexiopaysandbox.com/pay/v3/vault/echeck/{echeckToken}`
- Auth: HTTP basic

Allows you to view details of a specific echeck token. 

Echeck tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency.

<!-- theme: warning -->
> ⚠️ Try It
> 
> To use the Try It feature for this endpoint, you can use the credentials for your [Sandbox API user](doc:sandbox-environments).<br/><br/>You can also use the following test account. Copy the value and paste it into the appropriate space in the Try It section to the right.
> username: `docs@nexiopay.com`
> password: `JZdzoXpdDeH6VA`<br/><br/>Include a saved echeck token in the path parameter of the request.

<div style="display:none;">

## Request parameters
- echeckToken

## Response parameters
- bank
- bank.accountHolderName
- bank.routingNumber
- tokenex
- tokenex.lastFour
- tokenex.token
- data
- data.customer
- data.customer.orderNumber
- data.customer.invoice
- data.customer.customerRef
- data.customer.companyName
- data.customer.firstName
- data.customer.lastName
- data.customer.birthDate
- data.customer.email
- data.customer.phone
- data.customer.billToAddressOne
- data.customer.billToAddressTwo
- data.customer.billToCity
- data.customer.billToState
- data.customer.billToPostal
- data.customer.billToCountry
- data.customer.billToPhone
- data.customer.shipToAddressOne
- data.customer.shipToAddressTwo
- data.customer.shipToCity
- data.customer.shipToState
- data.customer.shipToPostal
- data.customer.shipToCountry
- data.customer.shipToPhone
- dateCreated
- dateLastModified
- merchantId

</div>

## Path parameters

- `echeckToken` string, required

## Response `200`

Success.

- object
  - `bank` object: The account holder's bank information.
    - `accountHolderName` string: The bank account holder's name, whether a person or a business. This value is saved in the echeck token. If a person's name is indicted here, the company name may be indicated in the `data.customer.companyName` parameter. Or, if a business name is indicated here, the person's name may be indicated in the `data.customer.firstName` and `data.customer.lastName` parameters.
    - `routingNumber` string: The checking account's routing number. This value is saved in the echeck token.
  - `tokenex` object: The echeck token information. This object only gets returned if the token is a saved echeck token.
    - `lastFour` string: The last four digits of the account number. This value is saved in the echeck token.
    - `token` string: The TokenEx echeck token. This is the saved echeck token. Echeck tokens can be used to process through any MID on your account. They are not restricted to a specific merchant account or currency.
  - `data` object: Additional data attached to the echeck token
    - `customer` object: Customer information to be used in checking fraud or sent to the processing gateway, when applicable.
      - `orderNumber` string: The order number. You can send this in the request, but the system does not save it to the saved echeck token. Instead, you should include it in the request to [Create one-time-use token](ref:createonetimeusetoken) or when running the transaction (see [Run echeck transaction](ref:runechecktransaction) or [Run echeck transaction with iframe](ref:runechecktransactioniframe)).
      - `orderDate` string: The date of the customer's order. The format returned matches the format used in the request.
      - `invoice` Invoice (unresolved $ref)
      - `customerRef` CustomerRef (unresolved $ref)
      - `companyName` CompanyName (unresolved $ref)
      - `firstName` FirstName (unresolved $ref)
      - `lastName` LastName (unresolved $ref)
      - `birthDate` BirthDate (unresolved $ref)
      - `email` Email (unresolved $ref)
      - `phone` Phone (unresolved $ref)
      - `billToAddressOne` BillToAddressOne (unresolved $ref)
      - `billToAddressTwo` BillToAddressTwo (unresolved $ref)
      - `billToCity` BillToCity (unresolved $ref)
      - `billToState` BillToState (unresolved $ref)
      - `billToPostal` BillToPostal (unresolved $ref)
      - `billToCountry` BillToCountry (unresolved $ref)
      - `billToPhone` BillToPhone (unresolved $ref)
      - `shipToAddressOne` ShipToAddressOne (unresolved $ref)
      - `shipToAddressTwo` ShipToAddressTwo (unresolved $ref)
      - `shipToCity` ShipToCity (unresolved $ref)
      - `shipToState` ShipToState (unresolved $ref)
      - `shipToPostal` ShipToPostal (unresolved $ref)
      - `shipToCountry` ShipToCountry (unresolved $ref)
      - `shipToPhone` ShipToPhone (unresolved $ref)
  - `merchantId` MerchantId (unresolved $ref)
  - `dateCreated` string: The date and time when the record of this echeck was created, formatted as an [ISO-8601](https://www.iso.org/iso-8601-date-and-time-format.html) date expressed in UTC.
  - `dateLastModified` string: The date and time at which the record of this echeck was last modified, formatted as an [ISO-8601](https://www.iso.org/iso-8601-date-and-time-format.html) date expressed in UTC.
  - `random` RandomNnnn (unresolved $ref)

## Other responses

- `401`: Unauthorized. For help with this error and other error codes, see [Common errors](doc:common-errors) in the Guides area.
- `404`: Not Found.

## Changes

- **2026-11-03** `d20a0473c611`: 1 info
  - added the optional property `error` to the response with the `401` status

[Operation history](https://skmtc.dev/nexiopay/apis/payments-api-reference/changes/pay/v3/vault/echeck/:echeckToken/get.md)

---

[API](https://skmtc.dev/nexiopay/apis/payments-api-reference.md) - [All operations](https://skmtc.dev/nexiopay/apis/payments-api-reference/llms.txt) - [OpenAPI document](https://skmtc.dev/nexiopay/apis/payments-api-reference/revisions/d20a0473c611?raw)