# Adjustments

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

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

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

**Method:**\
Supports **SOAP POST** and **HTTP POST** (form-encoded)

**Description:**\
Processes a "forced" credit card transaction by manually submitting a pre-authorized approval code. This is used when a merchant receives authorization through external means (e.g., phone approval) and must now force the transaction into the batch for settlement.

***

### Request Parameters

| Parameter    | Type   | Required | Description                                             |
| ------------ | ------ | -------- | ------------------------------------------------------- |
| UserName     | string | Yes      | Admin username                                          |
| Password     | string | Yes      | Admin password                                          |
| Vendor       | string | Yes      | Merchant numeric key                                    |
| TransType    | string | Yes      | Should be `FORCE`                                       |
| Amount       | string | Yes      | Transaction amount                                      |
| AuthCode     | string | Yes      | Authorization code manually provided by the card issuer |
| CcAccountNum | string | Yes      | Credit card number                                      |
| CcExpDate    | string | Yes      | Card expiration date (MMYY)                             |
| CcNameOnCard | string | No       | Cardholder name                                         |
| CcStreet     | string | No       | Billing street address                                  |
| CcZip        | string | No       | Billing ZIP/postal code                                 |
| Invoice      | string | No       | Optional invoice number                                 |
| CustomerID   | string | No       | Optional merchant-defined customer ID                   |
| ExtData      | string | No       | Optional XML-formatted metadata                         |

***

### Notes

* **Use `FORCE` as TransType:**\
  This is required to indicate that the transaction is a post-authorization force-through. The gateway bypasses the real-time authorization request and uses the provided `AuthCode`.
* **Common use cases:**
  * Recovery from a system or communications failure after voice authorization
  * Submitting a transaction when the original authorization was received outside the gateway
  * Consolidating manually approved sales into daily settlement
* **Critical field: `AuthCode`**\
  You must supply a valid authorization code that was previously issued by the card network or issuer. This tells the gateway to treat the transaction as already approved.
* **Force transactions skip risk checks:**\
  Since no authorization is performed, gateway-level fraud screening, CVV validation, or AVS are not applied. Merchants should exercise extra caution.
* **Settlement timing:**\
  Forced transactions are eligible for inclusion in the current day’s open batch and will settle normally unless flagged by downstream processing rules.


---

# 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/adjustments.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.