Request Fields
| Field Name | Mandatory? | Description |
|---|---|---|
| xref | Yes | Reference to initial CIT or previous MIT transaction. |
| type | Yes[1] | The type of transaction. Possible values are: 1 – E-commerce (ECOM) (CIT). 2 – Mail Order/Telephone Order (MOTO), (CIT) or Card Not Present (CNP)(MIT). 9 – Continuous Authority (CA) (MIT). |
| rtAgreementType | Yes[2] | Consumer/Merchant agreement type. Possible values are: cardonfile – credential storage agreed (CIT/MIT). recurring – recurring type agreed (CIT/MIT). instalment – instalment type agreed (CIT/MIT). unscheduled – ad hoc COF payment (MIT). incremental[3] – authorisation amount increment (MIT). resubmission – failed authorisation retry (MIT). reauthorisation – expired authorisation refresh (MIT). delayedcharges – post authorisation charges (MIT). noshow – missed reservation penalty (MIT). |
| rtSequenceCount | No[4] | Number of transactions in a recurring sequence if known. |
| rtSequenceNumber | No[4] | Transaction number in a recurring sequence if known. |
| rtAmountFixed | No | Indicate if payment amounts will be fixed or variable. Possible values are: N – amounts will be variable (default). Y – amounts will be fixed. |
| initiator | No[5] | Indicate who initiated the transaction. Possible values are: consumer – consumer initiated (CIT) merchant – merchant initiated (MIT) |
For backwards compatibility, the Gateway will try to automatically identify if a transaction is CIT or MIT from the values provided for the action, type and rtAgreementType fields. You may also pass the initiator field in the request to force a classification. If, however, the requested classification is incompatible with the provided request fields then the transaction will fail with a responseCode of 66944 (INVALID INITIATOR). The initiator field will be returned in the response with either the value passed in the request or the automatically identified value.