Cutover
Last updated: 04-Dec-2024
This command runs the End of Day Cutover report. Cutover response is received for a batch close request (host capture cut over). The totals include only ones for the device.
Note
The host/gateway/integrator should support this command - First Data Rapid Connect at time of publication.
Device UI Required: No
Request Packet
| Field | Rule | Type | Minimum | Maximum | Value(s) | Description |
|---|---|---|---|---|---|---|
| FUNCTION_TYPE | Required | Static value | N/A | N/A | REPORT | Type of function |
| COMMAND | Required | Static value | N/A | N/A | CUTOVER | Command name |
| PITSTOP | Optional | Binary |
|
For PITSTOP solution, if this field is sent as TRUE, then the command will be sent to the host with the terminal ID (TID) of the PITSTOP device. If this is sent as empty or sent with FALSE value, then IPP terminal ID will be used. NOTE: As of this publication, this is applicable for FDRC. Also, this field is applicable only when ANYWHERECARDENABLED parameter (Device/PINPad Parameters) is enabled. Example: <PITSTOP>TRUE</PITSTOP>. |
||
| COUNTER | Required | Numeric | 1 | 10 | COUNTER is used for a given MAC label. Each COUNTER should be higher than the last one. This is sed to authenticate the POS. Example: 100 | |
| MAC | Required | Base64 Encoded Data | N/A | N/A | Message Authentication Code. This is used to authenticate the POS. | |
| MAC_LABEL | Required | Character | 1 | 50 | Associated label that tells the device which MAC_KEY to use to decrypt the value of MAC. This is used to authenticate the POS. Example: REG1 |
Example
Following is an example of request packet
<TRANSACTION>
<FUNCTION_TYPE>REPORT</FUNCTION_TYPE>
<COMMAND>CUTOVER</COMMAND>
<COUNTER>1</COUNTER>
<MAC> … </MAC>
<MAC_LABEL>REG2</MAC_LABEL>
</TRANSACTION>
Response Packet
| Field | Type | Value | Description |
|---|---|---|---|
| RESPONSE_TEXT | Character | Processor response text. Example: Cutover Successful | |
| RESULT | Character | This indicates the Result details. Example: APPROVED | |
| RESULT_CODE | Numeric | Expected result codes: 5 | This indicates the result code. |
| TERMINATION_STATUS | Character | SUCCESS and FAILURE | This indicates the transaction termination status. This is the overall status of the transaction irrespective of approved or declined. Like, if the output is generated then the status is SUCCESS and if no output is generated then the status will be FAILURE. |
| COUNTER | Numeric | Echoes COUNTER sent in the request. Example: 100 | |
| HOST_RESPCODE | Numeric | Host response code. This will be sent if included in the SSI response. Example: 000 | |
| FUNCTION_TYPE | Character | REPORT | Returns the type of function. |
| MAX_NUM_RECORDS_RETURNED | Numeric | Returns maximum number of records. Example: 5 | |
| NET_SETTLE_AMT | Floating point number | The exact amount of the merchant’s settlement for the business day being reported. Example: 1234.00 | |
| RECORDS | See RECORD below for elements. |
RECORD Child Elements
| Field | Type | Value(s) | Description |
|---|---|---|---|
| SumPymtTypeTag | Character | Returns the tag for the payment type. Example: AllCredit | |
| ITEMCOUNT | Numeric | The total count of items. Example: 32 | |
| ITEMAMOUNT | Floating point number | The amount for the items. Example: 00000005508.55 |
Example
Following is an example of response packet
<RESPONSE>
<RESPONSE_TEXT>Cutover Successful</RESPONSE_TEXT>
<RESULT>APPROVED</RESULT>
<RESULT_CODE>5</RESULT_CODE>
<COAMMAND>CUTOVER</COMMAND>
<TERMINATION_STATUS>SUCCESS</TERMINATION_STATUS>
<HOST_RESPCODE>000</HOST_RESPOCODE>
<MAX_NUM_RECORDS_RETURNED>1</MAX_NUM_RECORDS_RETURNED>
<FUNCTION_TYPE>REPORT</FUNCTION_TYPE>
<RECORDS>
<RECORD>
<SumPymtTypeTag>AllCredit</SumPymtTypeTag>
<ITEMCOUNT>0132</ITEMCOUNT>
<ITEMAMOUNT>00000005508.55</ITEMAMOUNT>
</RECORD>
</RECORDS>
</RESPONSE>
Rate this article:
