Gateways/processors support a vast array of different features, and in some cases
a single API will perform several different functions based on the state of the request.
To fully support this and maintain a consistent API, this extensible enumeration of request types
are provided to aid the gateway's implementations determination of the correct request to construct
(in the case that the current implementation supports it).
1. Certain gateways support the idea of a "Transparent Redirect" request.
Within that set, only certain ones support the idea of a transparent redirect tokenization only request.
In order to utilize the same
a particular request type, (e.g.
can be put on the
to distinguish which request to construct.
2. Certain gateways support the idea of a "Detached Credit" also referred to as a "blind credit"
In some cases, the gateways implementation utilizes the same "refund" api as a normal credit.
can be passed to an implementation's
method to distinguish what type of refund to construct.
3. Some gateway implementations allow you to pass a manual authorization code received from the bank.
For example, a customer service representative can take orders over the phone and call the bank directly
to get an authorization code for the customer's card. In this scenario, if your gateway supports
can be passed into an implementation's
method to distinguish what type of authorization to construct.