RFR Transactions (Batch Only)
An RFR (Request For Response) transaction enables you to request a response file for a previously submitted Batch. You make the request by submitting either the cnpSessionId of the Batch, or in the case of a request for an Account Updater file, the accountUpdateFileRequestData element.
The use of RFR transactions for Account Updater files apply only to the legacy Account Updater solution.
RFR Request
You must specify the RFR request as follows.
<RFRRequest>
<cnpSessionIdaccountUpdateFileRequestData>
</RFRRequest>
Example: RFR Request for Payment Transaction Batch
The following example shows an RFR request for the response, with 7766554321 as the value of the <cnpSessionId> element.
<cnpRequest version="12.0" xmlns="http://www.vantivcnp.com/schema" id="123" numBatchRequests="0">
<authentication>
<user>userName</user>
<password>password</password>
</authentication>
<RFRRequest>
<cnpSessionId>7766554321</cnpSessionId>
</RFRRequest>
</cnpRequest>
Example: RFR Request for an Account Updater File
<cnpRequest version="12.0" xmlns="http://www.vantivcnp.com/schema" id="123" numBatchRequests="0">
<authentication>
<user>userName</user>
<password>password</password>
</authentication>
<RFRRequest>
<merchantId>100</merchantId>
<postDate>2017-01-15</postDate>
</RFRRequest>
</cnpRequest>
RFR Response
When using an RFR request to obtain the response file for a payment transaction Batch, the RFR response is exactly the same as the original session response associated with the <cnpSessionId> you submitted in the RFR request. The session ID returned in the response will be the session ID of the original session.
When using an RFR request in an Account Updater scenario, you will receive either an Account Updater Completion response, if the file is ready, or an Account Updater RFR “not ready” response, as shown in the example below.
Example: Account Updater RFR “not ready” Response
<cnpResponse version="12.0" xmlns="http://www.vantivcnp.com/schema">
<RFRResponse response="1" message="The account update file is not ready yet. Please try again later.">
</RFRResponse>
</cnpResponse>