# General Info & Utilities

<figure><img src="/files/OPkpKWNGisTRODxR9jdP" alt=""><figcaption></figcaption></figure>

## <mark style="color:blue;">GetCardUpdates</mark>

**Endpoint URL:**\
[**https://secure.ftipgw.com/Admin/ws/TrxDetail.asmx?op=GetCardUpdates**](<https://secure.ftipgw.com/Admin/ws/TrxDetail.asmx?op=GetCardUpdates&#xA;&#xA;>)\
\
**Method:**\
Supports both **SOAP POST** and **HTTP GET/POST** (form‑encoded)\
\
**Description**\
Retrieves details of all card updates processed for a merchant within a specified date range, including updates like expiration date or account number changes reported by card updater services\
\
**Request Parameters**<br>

| Parameter       | Type   | Required | Description                                                                                                                                                                                                  |
| --------------- | ------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **UserName**    | string | Yes      | User name assigned by the payment gateway [frontstream.com+1secure.ftipgw.com+1](https://www.frontstream.com/developers/secure-electronics-payments-api/documentation/getcardupdates?utm_source=chatgpt.com) |
| **Password**    | string | Yes      | Corresponding password                                                                                                                                                                                       |
| **MerchantKey** | string | Yes      | Merchant’s key; the query runs against this merchant account                                                                                                                                                 |
| **BeginDt**     | string | Yes      | Start of date range (`MM/DD/YYYY`); auto‑converted to `T00:00:00.0000AM`                                                                                                                                     |
| **EndDt**       | string | Yes      | End of date range (`MM/DD/YYYY`); auto‑converted to `T12:59:59.9999PM`                                                                                                                                       |
| **ExtData**     | string | No       | Optional XML string for extended data                                                                                                                                                                        |

\
**Notes**<br>

* **Response Format:**
  * Returns an XML payload containing one `<Table>` node per card update event [secure.ftipgw.com+2frontstream.com+2secure.ftipgw.com+2](https://www.frontstream.com/developers/secure-electronics-payments-api/documentation/getcardupdates?utm_source=chatgpt.com).
* **Response Fields:**
  * Includes fields like `<Card_Info_Key>`, `<AccountLastFour>`, `<Updated>` (boolean), `<ExpDate>`, `<UpdatedExpDate>`, and `<ResponseCodeTxt>`, among others [frontstream.com](https://www.frontstream.com/developers/secure-electronics-payments-api/documentation/getcardupdates?utm_source=chatgpt.com).
* **Response Codes:**
  * Codes such as `000` (New Card), `201` (Expiration Updated), `202` (Account Number Updated), `203` (Account Closed), etc. A complete code‑to‑text mapping is available in the documentation [frontstream.com](https://www.frontstream.com/developers/secure-electronics-payments-api/documentation/getcardupdates?utm_source=chatgpt.com).
* **Date Handling:**
  * Input dates are normalized with explicit AM/PM boundaries (`BeginDt` at midnight start, `EndDt` just before midnight end).
* **Multiple Records:**
  * You may receive multiple `<Table>` entries—make sure parsing logic handles arrays of updates.
* **ExtData Usage:**
  * While optional, `ExtData` can be used to filter or enhance the request/response. Its exact format is provider‑specific XML.
* **Protocol Flexibility:**
  * This endpoint can be invoked via SOAP or simple HTTP GET/POST — choose based on your integration context

**SOAP 1.1**\
The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.

```
POST /Admin/ws/TrxDetail.asmx HTTP/1.1
Host: secure.ftipgw.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://demo.tpisoft.com/Admin/ws/GetCardUpdates"

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetCardUpdates xmlns="http://demo.tpisoft.com/Admin/ws">
      <username>string</username>
      <password>string</password>
      <merchantKey>string</merchantKey>
      <beginDt>string</beginDt>
      <endDt>string</endDt>
      <extData>string</extData>
    </GetCardUpdates>
  </soap:Body>
</soap:Envelope>
```

```
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetCardUpdatesResponse xmlns="http://demo.tpisoft.com/Admin/ws">
      <GetCardUpdatesResult>string</GetCardUpdatesResult>
    </GetCardUpdatesResponse>
  </soap:Body>
</soap:Envelope>
```

**HTTP POST**\
The following is a sample HTTP POST request and response. The placeholders shown need to be replaced with actual values.

```
POST /Admin/ws/TrxDetail.asmx/GetCardUpdates HTTP/1.1
Host: secure.ftipgw.com
Content-Type: application/x-www-form-urlencoded
Content-Length: length

username=string&password=string&merchantKey=string&beginDt=string&endDt=string&extData=string

```

```
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<string xmlns="http://demo.tpisoft.com/Admin/ws">string</string>
```

## <mark style="color:blue;">GetCardType</mark>

**Endpoint URL:**\
`https://secure.ftipgw.com/ArgoFire/validate.asmx?op=GetCardType`

**Method:**\
SOAP (Action: `GetCardType`)

**Description:**\
Determines the type of a credit card (e.g., Visa, MasterCard, Discover, Amex) based on the card number provided. Intended for validation or routing decisions within ArgoFire-integrated flows.

**Request Parameters:**

| Name         | Type   | Required | Description                    |
| ------------ | ------ | -------- | ------------------------------ |
| CcAccountNum | string | Yes      | Credit card number to evaluate |

**Notes:**

* Returns a string indicating the card brand (e.g., `"Visa"`, `"MC"`, `"Amex"`).
* No transaction or tokenization is performed — this is strictly a metadata lookup.
* Often used for UI display or to conditionally apply rules before submission.
* Ensure the card number is never logged or stored during this request.
* This endpoint is part of the **ArgoFire validation suite**, and may differ slightly in behavior from the legacy version under `/recurring.asmx`.

#### SOAP 1.1

The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.

```
POST /ArgoFire/validate.asmx HTTP/1.1
Host: secure.ftipgw.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://localhost/SmartPayments/GetCardType"

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetCardType xmlns="http://localhost/SmartPayments/">
      <CardNumber>string</CardNumber>
    </GetCardType>
  </soap:Body>
</soap:Envelope>
```

```
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetCardTypeResponse xmlns="http://localhost/SmartPayments/">
      <GetCardTypeResult>string</GetCardTypeResult>
    </GetCardTypeResponse>
  </soap:Body>
</soap:Envelope>
```

#### SOAP 1.2

The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values.

```
POST /ArgoFire/validate.asmx HTTP/1.1
Host: secure.ftipgw.com
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <GetCardType xmlns="http://localhost/SmartPayments/">
      <CardNumber>string</CardNumber>
    </GetCardType>
  </soap12:Body>
</soap12:Envelope>
```

```
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <GetCardTypeResponse xmlns="http://localhost/SmartPayments/">
      <GetCardTypeResult>string</GetCardTypeResult>
    </GetCardTypeResponse>
  </soap12:Body>
</soap12:Envelope>
```

#### HTTP POST

The following is a sample HTTP POST request and response. The placeholders shown need to be replaced with actual values.

```
POST /ArgoFire/validate.asmx/GetCardType HTTP/1.1
Host: secure.ftipgw.com
Content-Type: application/x-www-form-urlencoded
Content-Length: length

CardNumber=string
```

```
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<string xmlns="http://localhost/SmartPayments/">string</string>
```

## <mark style="color:blue;">GetInfo</mark>

**Endpoint URL:**\
`https://secure.ftipgw.com/ArgoFire/transact.asmx?op=GetInfo`

**Method:**\
SOAP (Action: `GetInfo`)

**Description:**\
Retrieves full details about a previously submitted transaction using its `TransRefID`. This is often used for reconciliation, auditing, or checking the status and metadata of a payment after the fact.

**Request Parameters:**

| Name       | Type   | Required | Description                                |
| ---------- | ------ | -------- | ------------------------------------------ |
| Username   | string | Yes      | API credential username                    |
| Password   | string | Yes      | API credential password                    |
| TransRefID | string | Yes      | Unique transaction reference ID to look up |

**Notes:**

* Returns a full record of the transaction, including status, amounts, timestamps, card type, and custom fields.
* The `TransRefID` is returned by most ArgoFire transaction calls (e.g., `ProcessCreditCard`, `ProcessCheck`).
* This endpoint does **not** return sensitive card data (e.g., PAN or CVV).
* Commonly used by backend systems to confirm success, capture metadata, or display results to admins.
* Must be called with valid API credentials — not tied to a session or tokenization flow.

#### SOAP 1.1

The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.

```
POST /ArgoFire/transact.asmx HTTP/1.1
Host: secure.ftipgw.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://TPISoft.com/SmartPayments/GetInfo"

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetInfo xmlns="http://TPISoft.com/SmartPayments/">
      <UserName>string</UserName>
      <Password>string</Password>
      <TransType>string</TransType>
      <ExtData>string</ExtData>
    </GetInfo>
  </soap:Body>
</soap:Envelope>
```

```
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <GetInfoResponse xmlns="http://TPISoft.com/SmartPayments/">
      <GetInfoResult>
        <Result>int</Result>
        <RespMSG>string</RespMSG>
        <Message>string</Message>
        <Message1>string</Message1>
        <Message2>string</Message2>
        <AuthCode>string</AuthCode>
        <PNRef>string</PNRef>
        <HostCode>string</HostCode>
        <HostURL>string</HostURL>
        <ReceiptURL>string</ReceiptURL>
        <GetAVSResult>string</GetAVSResult>
        <GetAVSResultTXT>string</GetAVSResultTXT>
        <GetStreetMatchTXT>string</GetStreetMatchTXT>
        <GetZipMatchTXT>string</GetZipMatchTXT>
        <GetCVResult>string</GetCVResult>
        <GetCVResultTXT>string</GetCVResultTXT>
        <GetGetOrigResult>string</GetGetOrigResult>
        <GetCommercialCard>string</GetCommercialCard>
        <WorkingKey>string</WorkingKey>
        <KeyPointer>string</KeyPointer>
        <ExtData>string</ExtData>
      </GetInfoResult>
    </GetInfoResponse>
  </soap:Body>
</soap:Envelope>
```

#### SOAP 1.2

The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values.

```
POST /ArgoFire/transact.asmx HTTP/1.1
Host: secure.ftipgw.com
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <GetInfo xmlns="http://TPISoft.com/SmartPayments/">
      <UserName>string</UserName>
      <Password>string</Password>
      <TransType>string</TransType>
      <ExtData>string</ExtData>
    </GetInfo>
  </soap12:Body>
</soap12:Envelope>
```

```
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
  <soap12:Body>
    <GetInfoResponse xmlns="http://TPISoft.com/SmartPayments/">
      <GetInfoResult>
        <Result>int</Result>
        <RespMSG>string</RespMSG>
        <Message>string</Message>
        <Message1>string</Message1>
        <Message2>string</Message2>
        <AuthCode>string</AuthCode>
        <PNRef>string</PNRef>
        <HostCode>string</HostCode>
        <HostURL>string</HostURL>
        <ReceiptURL>string</ReceiptURL>
        <GetAVSResult>string</GetAVSResult>
        <GetAVSResultTXT>string</GetAVSResultTXT>
        <GetStreetMatchTXT>string</GetStreetMatchTXT>
        <GetZipMatchTXT>string</GetZipMatchTXT>
        <GetCVResult>string</GetCVResult>
        <GetCVResultTXT>string</GetCVResultTXT>
        <GetGetOrigResult>string</GetGetOrigResult>
        <GetCommercialCard>string</GetCommercialCard>
        <WorkingKey>string</WorkingKey>
        <KeyPointer>string</KeyPointer>
        <ExtData>string</ExtData>
      </GetInfoResult>
    </GetInfoResponse>
  </soap12:Body>
</soap12:Envelope>
```

#### HTTP POST

The following is a sample HTTP POST request and response. The placeholders shown need to be replaced with actual values.

```
POST /ArgoFire/transact.asmx/GetInfo HTTP/1.1
Host: secure.ftipgw.com
Content-Type: application/x-www-form-urlencoded
Content-Length: length

UserName=string&Password=string&TransType=string&ExtData=string
```

```
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length

<?xml version="1.0" encoding="utf-8"?>
<Response xmlns="http://TPISoft.com/SmartPayments/">
  <Result>int</Result>
  <RespMSG>string</RespMSG>
  <Message>string</Message>
  <Message1>string</Message1>
  <Message2>string</Message2>
  <AuthCode>string</AuthCode>
  <PNRef>string</PNRef>
  <HostCode>string</HostCode>
  <HostURL>string</HostURL>
  <ReceiptURL>string</ReceiptURL>
  <GetAVSResult>string</GetAVSResult>
  <GetAVSResultTXT>string</GetAVSResultTXT>
  <GetStreetMatchTXT>string</GetStreetMatchTXT>
  <GetZipMatchTXT>string</GetZipMatchTXT>
  <GetCVResult>string</GetCVResult>
  <GetCVResultTXT>string</GetCVResultTXT>
  <GetGetOrigResult>string</GetGetOrigResult>
  <GetCommercialCard>string</GetCommercialCard>
  <WorkingKey>string</WorkingKey>
  <KeyPointer>string</KeyPointer>
  <ExtData>string</ExtData>
</Response>
```

## <mark style="color:blue;">CaptureAll</mark>

**Endpoint URL:**\
`https://secure.ftipgw.com/SmartPayments/transact.asmx?op=ProcessCreditCard`

(Same as other `ProcessCreditCard` operations.)

**Description:**\
The **CaptureAll** operation closes and settles all approved credit card transactions in the merchant’s current open batch. It is used to submit the entire batch for settlement with a single call, rather than capturing individual transactions one by one.

#### Request Parameters

| Parameter   | Required | Description                  |
| ----------- | -------- | ---------------------------- |
| `UserName`  | Yes      | The merchant’s API username. |
| `Password`  | Yes      | The merchant’s API password. |
| `TransType` | Yes      | Must be set to `CaptureAll`. |

#### Sample Request

```
<Request>
  <UserName>test</UserName>
  <Password>123</Password>
  <TransType>CaptureAll</TransType>
</Request>
```

#### Sample Response

```
<Response xmlns:xsd="http://www.w3.org/2001/XMLSchema"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xmlns="https://secure.ftipgw.com/ArgoFire/">
  <Result>0</Result>
  <RespMSG>Approved</RespMSG>
  <Message>ACCEPTED</Message>
  <AuthCode>GB00029 ACCEPTED</AuthCode>
  <ExtData>Net_Count=5,Net_Amount=275.00,Settle_DT=2004-04-13 15:36:26</ExtData>
</Response>
```

* **Result** `0` = successful batch settlement
* **RespMSG / Message** = confirmation that batch was closed and accepted
* **AuthCode** = settlement confirmation reference
* **ExtData** = provides batch statistics: total transaction count, total settled amount, and settlement date/time

## <mark style="color:blue;">ArgoFire Response Codes</mark>

The list below contains result codes returned in the Result response field of the API or GUI AuthCode field.   A decline returned by the payment processor for the API response field is value twelve (12) or thirteen (13). An approval is value zero (0). Any other value is an error code, which is returned by ArgoFire and not by the payment processor. Please note that when programmatically validating a transaction’s result, from the API, this value should be used instead of any response message describing the result. I.e. do *not* use RespMSG or Message response fields, as these values may vary. Please note that this list is subject to change without prior notice.

| Value | Description                                                                              |
| ----- | ---------------------------------------------------------------------------------------- |
| -100  | Transaction NOT Processed; Generic Host Error                                            |
| 0     | Approved                                                                                 |
| 1     | User Authentication Failed                                                               |
| 2     | Invalid Transaction                                                                      |
| 3     | Invalid Transaction Type                                                                 |
| 4     | Invalid Amount                                                                           |
| 5     | Invalid Merchant Information                                                             |
| 7     | Field Format Error                                                                       |
| 8     | Not a Transaction Server                                                                 |
| 9     | Invalid Parameter Stream                                                                 |
| 10    | Too Many Line Items                                                                      |
| 11    | Client Timeout Waiting for Response                                                      |
| 12    | Decline                                                                                  |
| 13    | Referral                                                                                 |
| 14    | Transaction Type Not Supported In This Version                                           |
| 19    | Original Transaction ID Not Found                                                        |
| 20    | Customer Reference Number Not Found                                                      |
| 22    | Invalid ABA Number                                                                       |
| 23    | Invalid Account Number                                                                   |
| 24    | Invalid Expiration Date                                                                  |
| 25    | Transaction Type Not Supported by Host                                                   |
| 26    | Invalid Reference Number                                                                 |
| 27    | Invalid Receipt Information                                                              |
| 28    | Invalid Check Holder Name                                                                |
| 29    | Invalid Check Number                                                                     |
| 30    | Check DL Verification Requires DL State                                                  |
| 40    | Transaction did not connect (to NCN because SecureNCIS is not running on the web server) |
| 50    | Insufficient Funds Available                                                             |
| 99    | General Error                                                                            |
| 100   | Invalid Transaction Returned from Host                                                   |
| 101   | Timeout Value too Small or Invalid Time Out Value                                        |
| 102   | Processor Not Available                                                                  |
| 103   | Error Reading Response from Host                                                         |
| 104   | Timeout waiting for Processor Response                                                   |
| 105   | Credit Error                                                                             |
| 106   | Host Not Available                                                                       |
| 107   | Duplicate Suppression Timeout                                                            |
| 108   | Void Error                                                                               |
| 109   | Timeout Waiting for Host Response                                                        |
| 110   | Duplicate Transaction                                                                    |
| 111   | Capture Error                                                                            |
| 112   | Failed AVS Check                                                                         |
| 113   | Cannot Exceed Sales Cap                                                                  |
| 201   | FPRejected\_Floor                                                                        |
| 202   | FPRejected\_Ceiling                                                                      |
| 203   | FPRejected\_IP                                                                           |
| 204   | FPRejected\_BIN                                                                          |
| 205   | FPRejected\_Velocity                                                                     |
| 1000  | Generic Host Error                                                                       |
| 1001  | Invalid Login                                                                            |
| 1002  | Insufficient Privilege or Invalid Amount                                                 |
| 1003  | Invalid Login Blocked                                                                    |
| 1004  | Invalid Login Deactivated                                                                |
| 1005  | Transaction Type Not Allowed                                                             |
| 1006  | Unsupported Processor                                                                    |
| 1007  | Invalid Request Message                                                                  |
| 1008  | Invalid Version                                                                          |
| 1010  | Payment Type Not Supported                                                               |
| 1011  | Error Starting Transaction                                                               |
| 1012  | Error Finishing Transaction                                                              |
| 1013  | Error Checking Duplicate                                                                 |
| 1014  | No Records To Settle (in the current batch)                                              |
| 1015  | No Records To Process (in the current batch)                                             |

*AVS Response Codes*

The following table contains the possible response values returned for address verification (AVS).

| Value | Description                                                                                                         |
| ----- | ------------------------------------------------------------------------------------------------------------------- |
| X     | Exact: Address and nine-digit Zip match                                                                             |
| Y     | Yes: Address and five-digit Zip match                                                                               |
| A     | Address: Address matches, Zip does not                                                                              |
| Z     | 5-digit Zip: 5-digit Zip matches, address doesn’t                                                                   |
| W     | Whole Zip: 9-digit Zip matches, address doesn’t                                                                     |
| N     | No: Neither address nor Zip matches                                                                                 |
| U     | Unavailable: Address information not available                                                                      |
| G     | Unavailable: Address information not available for international transaction                                        |
| R     | Retry: System unavailable or time-out                                                                               |
| E     | Error: Transaction unintelligible for AVS or edit error found in the message that prevents AVS from being performed |
| S     | Not Supported: Issuer doesn’t support AVS service                                                                   |
| B     | \* Street Match: Street addresses match for international transaction, but postal code doesn’t                      |
| C     | \* Street Address: Street addresses and postal code not verified for international transaction                      |
| D     | \* Match: Street addresses and postal codes match for international transaction                                     |
| I     | \* Not Verified: Address Information not verified for International transaction                                     |
| M     | \* Match: Street addresses and postal codes match for international transaction                                     |
| P     | \* Postal Match: Postal codes match for international transaction, but street address doesn’t                       |
| 0     | \*\* No response sent                                                                                               |
| 5     | Invalid AVS response                                                                                                |

\* These values are Visa specific. \*\* These values are returned by ArgoFire and not the processor.

*CV Response Codes*

The following table contains the possible response values returned for a CVV2/CVC2/CID check.

| Value | Description                                                                                                                                  |
| ----- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| M     | CVV2/CVC2/CID Match                                                                                                                          |
| N     | CVV2/CVC2/CID No Match                                                                                                                       |
| P     | Not Processed                                                                                                                                |
| S     | Issuer indicates that the CV data should be present on the card, but the merchant has indicated that the CV data is not present on the card. |
| U     | Unknown / Issuer has not certified for CV or issuer has not provided Visa/MasterCard with the CV encryption keys.                            |
| X     | Server Provider did not respond                                                                                                              |

&#x20;


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developers.frontstream.com/argofire/full-endpoint-reference-and-tools/general-info-and-utilities.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.