Output parameters for the GETTXSTATUS call:

The fields in the response to the GETTXSTATUS call are the same as in the response to the TRANSACTION call, except any transient output parameters and the additional fields that reflect the status of the GETTXSTATUS call itself.

FieldTypeDescription
REQUESTSTATUSasciiPossible values:

SUCCEEDED: the transaction status values reflect the status of the referenced transaction.

FAILED: the GETTXSTATUS call failed. Check ERRMSG for details.
REQUESTFAILREASONasciiOnly returned if REQUESTSTATUS has FAILED. See REQUESTFAILREASON for possible values.
STATUSasciiThe outcome of the request. Possible values:

PENDING
SUCCEEDED
FAILED
TXIDasciiUnique transaction identifier.

Allowed characters: [a-zA-Z0-9.,-_], 20 characters maximum.

In case of severe errors (e.g. authentication not possible) this will return “0”, otherwise always a valid transaction identifier is assigned.
MERCHANTTXIDasciiYou can send the value of the merchanttxidparameter in the initial TRANSACTION request.
FUNDSSTATUSasciiFunds status of the transaction. Possible values:

NOT_EXPECTED
WAITING
RECEIVED
MISSING

For payment methods that don’t expect funds, this is always NOT_EXPECTED.
ERRMSGutf-8Human-readable error message. Maximum of 128 characters.
REDIRECTURLasciiURL to redirect the consumer (see Redirecting the consumer). Only available in PENDING asynchronous transactions. Maximum 255 characters.
REDIRECTSECRETasciiRandom string used in creating hashes (see Redirecting the consumer. Maximum 64 characters.
FAILREASONasciiReturned only if STATUS is FAILED. Possible values:

UNKNOWN: transaction failed for unknown reasons (also default in reporting for succeeded transactions).

INPUT_DATA: a problem occurred with the data that you passed.

USER_ABORT: the consumer aborted the payment process.

TIMEOUT: there was a timeout while waiting for the transaction result.

LOCAL_ERROR: local system error. Contact Payment Gateway support.

REMOTE_ERROR: a remote processing error occurred. If this situation persists, contact Payment Gateway support.

LOCAL_DECLINE: the Payment Gateway declined the transaction, for example, due to risk management.

REMOTE_DECLINE: a remote system declines the transaction, for example, due to failed payment process authentication.

CANCELED: the transaction was canceled on the client's request (see CANCELTX).
CHANNELasciiThe channel used for the transaction (equals the input data).
TAGasciiThe tag within the channel used for the transaction (equals the input data).

SUCCEEDED Response

The response in this example shows a transaction that has succeeded.

REQUESTSTATUS=SUCCEEDED
&STATUS=SUCCEEDED
&TXID=123887123
&ERRMSG=
&REDIRECTSECRET=dcn94nd2oud8eedhg38dkhed
&CHANNEL=testchannel
&TAG=giropay
&MERCHANTTXID=sale1002
&FUNDSSTATUS=RECEIVED
&RAND2034500137=cce3ce30fc977edc435e29105da93bb788850f14

PENDING Response

It is common that a transaction is still pending after redirecting the consumer to merchantredirectURL. The response in this example shows a pending transaction. Be patient, and don’t forget to use notifications.

RAND4657253453=375ff3f1b2321a6137b1e96161e76fe0fb5c1e86
&REQUESTSTATUS=SUCCEEDED
&STATUS=PENDING
&TXID=123887123
&ERRMSG=
&REDIRECTURL=https%3A%2F%2Fr%2Egirogate%2Ede%2Fprocess%3Ftx%3D123887123%26rs%3D12h2
&REDIRECTSECRET=dcn94nd2oud8eedhg38dkhed
&CHANNEL=testchannel
&TAG=giropay
&MERCHANTTXID=sale1002
&FUNDSSTATUS=NOT_EXPECTED

FAILED Response

The response in this example shows a failed transaction.

REQUESTSTATUS=SUCCEEDED
&STATUS=FAILED
&TXID=12398874
&ERRMSG=Channel%20not&20found
&REDIRECTSECRET=
&FAILREASON=INPUT_DATA
&CHANNEL=nonexistentchannel
&TAG=giropay
&MERCHANTTXID=sale1002
&RAND8735624512=5483b800c23e5005bd1c3cc11c9c2a310dc77725a
&FUNDSSTATUS=NOT_EXPECTED

GETTXSTATUS call failed

This example shows a failed GETTXSTATUS call.

REQUESTSTATUS=FAILED
&REQUESTFAILREASON=TX_NOT_FOUND
&STATUS=FAILED
&TXID=0
&ERRMSG=Transaction%20not%20found
&RAND21524356542=b5bd9cd217485a43412f20d98e4c589fdd9bd0f2