# Customizations

### <mark style="color:$primary;">Overview</mark>

Vendors are able to request customizations to be created for any transactions made to them. These customizations will require the payer to enter specific information before being able to approve a transaction to this vendor.

### <mark style="color:$primary;">How it Works</mark>

Vendors may request customizations in the form of:

* **Required transaction formats:** Payers must input their transactions in a specific format using the information provided by the vendor. This may include items such as a specific Airway Bill prefix or Invoice numbers.
* **Additional transaction details:** Vendors may add additional transaction details to be requested, such as account numbers or transaction numbers related to the vendor.
* **Transaction Lines:** Vendors may require clients to enter the transaction lines for a transaction to indicate the fees the payment they are making will apply to.
* **Set Amounts For Payments:** If a payer selects to pay a specific type of transaction to the vendor, this amount may be a fixed amount set by the vendor in order to prevent any misinput of the amount when making a payment.

By having a customization, both vendors and payers are able to confidently ensure that the transactions they are paying for are applied to the intended bill.

### <mark style="color:$primary;">Key Benefits</mark>

<i class="fa-check">:check:</i> **Reduced errors in payments:** Required formats, fixed amounts, and predefined transaction lines minimize the risk of entering incorrect invoice numbers, references, or payment amounts.

<i class="fa-check">:check:</i> **Confidence payments are applied correctly:** Standardized formats and required fields ensure payments contain all necessary information for correct application.

<i class="fa-check">:check:</i> **Simplified payment experience:** Structured inputs guide payers through the process, reducing guesswork and the need to understand complex billing details.

<i class="fa-check">:check:</i> **Faster issue resolution:** When disputes or questions arise, detailed transaction data makes it easier to identify and resolve issues quickly.

### <mark style="color:$primary;">Related Questions</mark>

<details>

<summary>I do not know the information that is being asked to be entered. How do I make my payment?</summary>

Please contact the vendor you are attempting to make a payment to in order to retrieve the required information needed for your payment.

</details>

<details>

<summary>The fixed amount shown is not the amount I wish to pay. How do I change this amount?</summary>

The fixed amount is an amount requested by the vendor to be set in place for the type of transaction you are attempting to pay. Please review the type of payment you are selecting when paying this vendor. If the payment type you selected is the one requested to be paid, please reach out to the vendor regarding this amount.

</details>

<details>

<summary>I put in the correct information, but I cannot click to enter an amount to pay. How would I enter the amount I want to pay?</summary>

Your transaction may require you to enter the amount you wish to pay as a transaction line. This field may appear as a table with fields at the bottom or side of the transaction details.

</details>


---

# 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://support.paycargo.com/integrations-and-customizations/customizations.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.