Note: The check processor may allow MICR data to be sent in place of account and route or it may require both. This can be determined during certification.
Indicates whether the provided data was entered manually or retrieved from a reader; see the associated Type enumerations for specific values supported.
Note: SECCode is a required field when the check processor is Colonnade.
Note: For GETI, this will be used to validate information returned from GETI during the transaction. This validation is not done when EBRONZE is chosen.
Note: While all these are optional in the schema, the check processor may require some of these fields in specific circumstances. For additional information on this, please consult the requirements of the specific processor.
Unique key generated by PayPlan associated with a stored payment method
Note: When using PaymentMethodKey, the following fields should not be sent as part of the transaction as they will be obtained from previously stored data:
Token used to replace payment method data (route, account, and MICR).
Note: Multi-use tokens are not yet supported on check transactions. This is currently only used for single-use tokens. Single-use tokens are provided by the SecureSubmit product and are primarily used in eCommerce situations.
Source
<xs:elementname="Block1"type="CheckSaleReqBlock1Type"xmlns:xs="http://www.w3.org/2001/XMLSchema"><xs:annotation><xs:documentation><pxmlns="http://Hps.Exchange.PosGateway">Contains a series of required and optional elements</p></xs:documentation></xs:annotation></xs:element>