> For the complete documentation index, see [llms.txt](https://developers.hyp.co.il/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.hyp.co.il/enterprise/advanced-considerations/request-validation-methods.md).

# Request Validation Methods

Request validation allows you, as a merchant, to specify the type of action you want to perform. Including a request validation parameter in your Hyp Enterprise API request clearly indicates your intent.

Since Hyp Enterprise acts as a bridge between merchants and major payment systems (such as Shva, acquirers and card issuers), it is important for each request to clearly state the desired action.

The XML element used to specify the validation method is either `<validation>` or `<mpiValidation>`. Read on to learn when to use each.

## Supported validation methods

The following are the most commonly used request validation methods (along with the codes they are often referred to as):

* `Verify` (J5). Places a temporary hold on funds to confirm availability but does not charge yet. Used in the first step of a [two-phase commit](https://developers.hyp.co.il/enterprise/two-phase-commits/overview.md).
* `AutoComm` (J4). Finalizes a payment and charges the customer's card. Used for most transactions, including regular [payment page](https://developers.hyp.co.il/enterprise/payment-page-integration/integrating-hyps-payment-page-and-accepting-payment.md) transactions, the second step of a [two-phase commit](https://developers.hyp.co.il/enterprise/two-phase-commits/overview.md), and server-to-server transactions such as [recurring payments](https://developers.hyp.co.il/enterprise/recurring-payments-and-subscriptions/overview-of-recurring-payments.md).
* `Token` (J102). Converts card details into a secure token for future use. No charge is made. Used in payment flows involving [short-term storage](https://developers.hyp.co.il/enterprise/additional-payment-scenarios/short-term-cc-data-storage.md).

There are also other methods, but they're not used nearly as often:

* `Normal` (J2). Performs a simple card validity check. No money is held or charged.
* `Dealer` (J6). Charges the customer's card and completes the payment in one step, bypassing terminal limits and shifting verification to the card issuer.
* `AutoCommHold` (J9). Starts a charge but holds it until the merchant confirms final processing with `AutoCommRelease`.
* `AutoCommRelease` (J109). Completes a transaction previously initiated with `AutoCommHold` and sends it for settlement.

There is also a special value, `TxnSetup`, which instructs Hyp Enterprise to generate a payment page where the customer can enter card details. The quirk with validation is that *you use different XML elements to express your intent* depending on whether a payment page is involved.

## Validation without a payment page

Consider the following `doDeal` request, which uses a saved credit card token (`cardId`) to perform a [recurring payment](https://developers.hyp.co.il/enterprise/recurring-payments-and-subscriptions/overview-of-recurring-payments.md). This request is server-to-server, with no payment page involved:

```xml
<ashrait>
    <request>
        <version>2000</version>
        <language>ENG</language>
        <command>doDeal</command>
        <doDeal>
            <terminalNumber>{terminalNumber}</terminalNumber>
            <cardId>1092880571131111</cardId>
            <cardExpiration>0328</cardExpiration>
            <total>10000</total>
            <transactionType>Debit</transactionType>
            <creditType>RegularCredit</creditType>
            <currency>ILS</currency>
            <transactionCode>Internet</transactionCode>
            <validation>AutoComm</validation>
        </doDeal>
    </request>
</ashrait>
```

The request validation method (`AutoComm`) is specified in the `validation` element.

## Validation in payment page requests

The following is also a `doDeal` request, but this time it is for a [payment page](https://developers.hyp.co.il/enterprise/payment-page-integration/integrating-hyps-payment-page-and-accepting-payment.md) to which the customer will be redirected:

```xml
<ashrait>
      <request>
          <version>2000</version>
          <language>ENG</language>
          <command>doDeal</command>
          <doDeal>
              <terminalNumber>{terminalNumber}</terminalNumber>
              <cardNo>CGMPI</cardNo>
              <total>10000</total>
              <transactionType>Debit</transactionType>
              <creditType>RegularCredit</creditType>
              <currency>ILS</currency>
              <transactionCode>Internet</transactionCode>
              <mid>{mid}</mid>
              <uniqueid>837683509-84983498539</uniqueid>
              <validation>TxnSetup</validation>
              <mpiValidation>AutoComm</mpiValidation>
              <successUrl>https://mymerchantwebsite.com/success/</successUrl>
              <errorUrl>https://mymerchantwebsite.com/error/</errorUrl>
          </doDeal>
      </request>
  </ashrait>
```

Here, the `validation` element is set to `TxnSetup`, which tells Hyp Enterprise to generate a payment page.

However, you still need a way to specify what should happen when the customer fills out their payment details and clicks **Pay**. Since `validation` is already set to `TxnSetup`, you need to use a different element to indicate your intent — this is what `mpiValidation` is for.

`mpiValidation` is used instead of `validation` when requesting a payment page and accepts all the validation methods listed above, except for `TxnSetup`. In this case, `mpiValidation` is set to `AutoComm`.

## FAQ

### What does MPI stand for?

MPI stands for Merchant Page Interface, the official name for Hyp Enterprise's payment page server.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.hyp.co.il/enterprise/advanced-considerations/request-validation-methods.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
