> ## Documentation Index
> Fetch the complete documentation index at: https://devzone.nayax.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Prepaid Card

Find quick answers and step-by-step guides for the most common questions about **Nayax API integration**, device configuration, transaction tracking, and deployment processes. Navigate the categories below to find solutions and best practices.

### Are all of the calls directed to the same TCP port?

<Accordion title="Answer" icon="info-circle">
  Yes, that is the most common and standard setup for this type of integration.

  All communication calls discussed (e.g., StartSession, Sale, Authorization, etc.) are typically directed to the same TCP port on your server, as specified in the base URL provided to Nayax.
</Accordion>

### How can we direct the calls to a particular port?

<Accordion title="Answer" icon="info-circle">
  You direct the calls to a specific port by appending the port number, preceded by a colon (`:`), to the customer's base URL.

  | Component          | Example            |
  | :----------------- | :----------------- |
  | **Customer URL**   | `XXX.com`          |
  | **Desired Port**   | `1234`             |
  | **Full URL Setup** | **`XXX.com:1234`** |

  This format ensures all calls (e.g., `StartSession`, `SaleEndNotification`, etc.) are directed to that specific port on the customer's server.
</Accordion>

### How can we track a transaction?

<Accordion title="Answer" icon="info-circle">
  Your primary identifier for tracking a transaction on your system is the **Transaction ID** field.

  You can send us any Transaction ID you desire, provided it meets the following criteria:

  * It must be made up of **36 numeric characters**.
  * It must be included and encrypted in the `StartSession` response body. (For full details, please refer to the [Start Session authentication process](/docs/cortina/start-session/cortina-auth#/)).

  To see which Nayax internal ID matches your Transaction ID, refer to the subsequent requests, such as the `Sale` request.

  > **Example:** In the `Sale` request, you will find:
  >
  > * Your Transaction ID (in your system's context).
  > * Nayax's matching Transaction ID.

  <Frame>
    <img src="https://mintcdn.com/nayax-44d6e37b/1pW0jXOF4OhjjY4f/images/docs/cortina-prepaid-faq/image1.png?fit=max&auto=format&n=1pW0jXOF4OhjjY4f&q=85&s=22eba9c85ad33b93115be418ddd9add5" width="554" height="74" data-path="images/docs/cortina-prepaid-faq/image1.png" />
  </Frame>
</Accordion>

### How do I identify which of my machines the transaction is coming from?

<Accordion title="Answer" icon="info-circle">
  You can identify the machine from which the transaction originated by checking the **`Sale` request** data.

  ### 1. Recommended Method: `MachineInfo`

  The best method is to use the **`Id` field** found within the **`MachineInfo`** object in the request.

  * This `Id` represents your **virtual machine's ID**.
  * **Recommendation:** We suggest matching by the virtual machine ID because it is less likely to change than the physical device (e.g., if you swap a payment terminal).

  > **Action Item:** We recommend adding a column to your internal tracking table that correlates the `MachineInfo.Id` with the physical location of the device.

  ### 2. Alternative Method: `DeviceInfo`

  You can also identify the source using the physical device's serial number, which is sent within the **`DeviceInfo`** object. This is a less reliable long-term key if device swaps are common.

  <Frame>
    <img src="https://mintcdn.com/nayax-44d6e37b/1pW0jXOF4OhjjY4f/images/docs/cortina-prepaid-faq/image2.png?fit=max&auto=format&n=1pW0jXOF4OhjjY4f&q=85&s=dba43bfa53d32aa7d2d03f448722a283" width="451" height="439" data-path="images/docs/cortina-prepaid-faq/image2.png" />
  </Frame>

  <Frame>
    <img src="https://mintcdn.com/nayax-44d6e37b/1pW0jXOF4OhjjY4f/images/docs/cortina-prepaid-faq/image3.png?fit=max&auto=format&n=1pW0jXOF4OhjjY4f&q=85&s=cafabf5a841243b41109b4468ca05d88" width="439" height="558" data-path="images/docs/cortina-prepaid-faq/image3.png" />
  </Frame>
</Accordion>

### What are the endpoints for each of the commands?

<Accordion title="Answer" icon="info-circle">
  Each method has its own endpoint, as specified in the URL provided to Nayax.
  The structure is: `(customer's URL)/Cortina/ followed by the command/integration path`.

  ### 1. Simple Commands (Session & Notification)

  These commands use a direct path structure:

  | Command                 | Endpoint Example                               |
  | :---------------------- | :--------------------------------------------- |
  | **StartSession**        | `(customer's URL)/Cortina/StartSession`        |
  | **SaleEndNotification** | `(customer's URL)/Cortina/SaleEndNotification` |

  ***

  ### 2. PrePaid Integration Commands

  These commands include the integration type (`PrePaid`) in the path:

  | Command           | Endpoint Example                                 |
  | :---------------- | :----------------------------------------------- |
  | **Authorization** | `(customer's URL)/Cortina/PrePaid/Authorization` |
  | **Settlement**    | `(customer's URL)/Cortina/PrePaid/Settlement`    |
  | **Cancel**        | `(customer's URL)/Cortina/PrePaid/Cancel`        |
  | **Sale**          | `(customer's URL)/Cortina/PrePaid/Sale`          |
  | **Void**          | `(customer's URL)/Cortina/PrePaid/Void`          |
</Accordion>

### Where do I get the consumer's card details?

<Accordion title="Answer" icon="info-circle">
  The consumer's card details are found within the **`CardData`** object, which is included in the **`Sale` request**.

  <Frame>
    <img src="https://mintcdn.com/nayax-44d6e37b/1pW0jXOF4OhjjY4f/images/docs/cortina-prepaid-faq/image4.png?fit=max&auto=format&n=1pW0jXOF4OhjjY4f&q=85&s=52e03c25f9f3ff028d69070b22c64ac2" width="299" height="699" data-path="images/docs/cortina-prepaid-faq/image4.png" />
  </Frame>
</Accordion>

<br />

<br />