On This Page

Check a Request Status

You can retrieve the status of a pending sale or refund by sending a check status request.

When a pending status updates, a check status response includes the transaction's new status. Thunes sometimes needs to review a service request, which causes a transaction to initially respond with a pending status. The check status request requires you to include the request ID from the pending transaction response you are checking the status of. The request ID is located in the

requestID

response field. Cybersource recommends that you send a check status request hourly until the status updates from pending.

Endpoints

Set the

apCheckStatusService_run

field to

true

, and send the request to one of these endpoints:

Production:

https://ics2ws.ic3.com/commerce/1.x/transactionProcessor

Test:

https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Statuses

Cybersource responds to your check status request with one of these statuses in the

apCheckStatusReply_status

field:

Check Status Responses for a Sale: ABANDONED
: The customer did not complete the payment using the redirect URL.
FAILED
: The service request failed. A failed request can be due to either Twint rejecting the transaction or a technical error.
FUNDED
: The settled amount is funded to the merchant bank account.
PENDING
: The service request is accepted but is not completed. Request the check status service to retrieve status updates.
SETTLED
: The sale request is settled for the requested amount.
Check Status Responses for a Refund: FAILED
: The service request failed. A failed request can be due to either Twint rejecting the transaction or a technical error.
REFUNDED
: The settled amount is successfully refunded.

The check status service also responds with a reason code in the

apCheckStatusReply_reasonCode

field.

For more information about reason codes, see Reason Codes and Response Codes.

Required Fields for Checking Status

apCheckStatusService_checkStatusRequestID: Set to the request ID included in the service response.
apCheckStatusService_run: Set to
true
.
apPaymentType: Set to
TWN
.
merchantID
merchantReferenceCode

Example: Checking a Request Status

Request

<requestMessage xmlns="urn:schemas-cybersource-com:transaction-data-1.215">
	<merchantID>test_merchant</merchantID>
	<merchantReferenceCode>refnum-1234</merchantReferenceCode>
	<apPaymentType>TWN</apPaymentType>
	<apCheckStatusService run="true">
		<checkStatusRequestID>6953229557336619903008</checkStatusRequestID>
	</apCheckStatusService>
</requestMessage>

Response to a Successful Request

<replyMessage xmlns:c="urn:schemas-cybersource-com:transaction-data-1.215">
	<merchantReferenceCode>refnum-1234</merchantReferenceCode>
	<requestID>6989529700616633303007</requestID>
	<decision>ACCEPT</decision>
	<reasonCode>100</reasonCode>
	<requestToken>AxjnrwSTeuc1xphoz7/fANgZYiy6laewnTZ9honkFw7xbfpC/oGdUMmkmXoxX6rUJN65zUbdKW/6eQAA/i7C</requestToken>
	<apCheckStatusReply>
		<reasonCode>100</reasonCode>
		<reconciliationID>XEKTVO0NMOX4</reconciliationID>
		<paymentStatus>pending</paymentStatus>
		<processorResponse>00001</processorResponse>
		<processorToken>348476012838</processorToken>
	</apCheckStatusReply>
</replyMessage>