# Adjustments

<figure><img src="https://1759075701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIS9AkCawNWrhCXwEyUbh%2Fuploads%2FOgmHAPtT5nzsLmavRnqf%2Fmedium.png?alt=media&#x26;token=0f8a4ca4-c1dc-4c0b-a09b-0b71576f08e4" 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.