Output parameters for the TRANSACTION call:

Field	Type	Description
STATUS	ascii	The outcome of the request. Possible values: • `PENDING` • `SUCCEEDED` • `FAILED`
TXID	ascii	Unique 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.
MERCHANTTXID	ascii	You can send the value of the `merchanttxid`parameter in the initial TRANSACTION request.
FUNDSSTATUS	ascii	Funds status of the transaction. Possible values: • `NOT_EXPECTED` • `WAITING` • `RECEIVED` • `MISSING` For payment methods that don’t expect funds, this is always `NOT_EXPECTED`.
ERRMSG	utf-8	Human-readable error message. Maximum of 128 characters.
REDIRECTURL	ascii	URL to redirect the consumer (see Redirecting the consumer). Only available in `PENDING` asynchronous transactions. Maximum 255 characters.
REDIRECTSECRET	ascii	Random string used in creating hashes (see Redirecting the consumer. Maximum 64 characters.
FAILREASON	ascii	Returned 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).
CHANNEL	ascii	The channel used for the transaction (equals the input data).
TAG	ascii	The tag within the channel used for the transaction (equals the input data).

SUCCEEDED Response

The transaction was successful, you can deliver the goods or services.

RAND1166524744=b0d98c1725f4293e2cfb9c394c223a17bda77093
&STATUS=SUCCEEDED
&TXID=123887123
&ERRMSG=
&REDIRECTSECRET=dcn94nd2oud8eedhg38dkhed
&CHANNEL=testchannel
&TAG=giropay
&MERCHANTTXID=sale1002
&FUNDSSTATUS=WAITING
&SPECOUT%2EPAYMENTPURPOSE=1AB66FE%20Testshop
&TRANSIENTOUT%2ESTEPS=%3Col%3E%3Cli%3EPlease+pay+%3Cstrong%3E1%2E23+USD%3C%2Fstrong%3E+to+the+clerk%2E%3C%2Fli%3E%3C%2Fol%3E

PENDING Response

With REDIRECTURL

At this point, the next step is to redirect the consumer to the URL given in REDIRECTURL.

Without REDIRECTURL

At this point, tell the consumer that the payment request was received and - depending on your risk management policy - deliver the goods. You will be informed about the transaction outcome through a notification.

STATUS=PENDING
&TXID=123887123
&ERRMSG=
&REDIRECTSECRET=dcn94nd2oud8eedhg38dkhed
&CHANNEL=testchannel
&RAND9283526354=a8237620721f1a7ef4a4462de71dfa76
&TAG=sepaddmodela
&MERCHANTTXID=sale1002
&FUNDSSTATUS=NOT_EXPECTED

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

FAILED Response

At this point, tell the consumer that the transaction couldn’t be initialized due to a scheme failure.

STATUS=FAILED
&TXID=12398874
&ERRMSG=Remote%20System%20Error
&REDIRECTSECRET=
&FAILREASON=REMOTE_ERROR
&CHANNEL=testchannel
&TAG=giropay
&MERCHANTTXID=sale1002
&FUNDSSTATUS=NOT_EXPECTED
&RAND1234876576=76f76ef76s87aaaabba4462d12835144