708 – Check transaction details

Returns current transaction details including rebill child transactions.

708 Request Data description:

NODE
INCLUDE IN CHECKSUM (IN THIS ORDER)
REQUIRED
DATA TYPE
DESCRIPTION

apiUser

YES (1)

YES

Character max 50.

The API user assigned by the Gateway to the merchant. Can be obtained from the website inside your merchant account.

apiPassword

YES (2)

YES

Character max 50.

The API password assigned by Gateway to the merchant. Can be obtained from the website inside your merchant account.

apiCmd

YES (3)

YES

708

3 digit numeric transaction code must be 708

merchanttransid

YES (4)

COND

Character max 50.

Unique merchant transaction id received in the request 700. Required if gatetransid not provided. Otherwise ignored.

gatetransid

Yes (4)

COND

Character max 50.

Unique gateway internal transaction id refers to charge transaction for which the status check has been requested. Required if merchanttransid not provided.

checksum

YES

Character no limit

SHA-1 calculated using the fields specified by the transaction plus the API key assigned by gateway to the merchant. This field must be calculated using the fields marked as “Include in checksum” (in the order indicated) plus the API key at the end.

708 Response Data description

To modify the transaction status on your end, utilize the 'state' field value to correspond with the transaction status. Any additional information, such as the status code, can be included as extra data.

NODE
REQUIRED
DATA TYPE
DESCRIPTION

result

YES

Character

Result indicates the result of the transaction. SUCCESS: Transaction was found and current state is returned. NOTFOUND: Transaction was not found. ERROR: Transaction state change failed.

transaction

YES

Xml Node

Section containing authorization type

transaction->gatetransid

Cond

Character

Gateway transaction ID

transaction->merchanttransid

Cond

Character

Merchant transaction ID provided during execution of 700 command

transaction->created

Cond

digits

Transaction date in format : YYYY-MM-DD HH:MM:SS

transaction->amount

Cond

Number with decimal point

Full amount to charge in currency specified.

transaction->curcode

Cond

Character 3

Transaction currency

transaction->state

Cond

Character

Current status of the transaction. AUTHORIZED: Funds from Customers Credit Card account have been “reserved” but not charged to the account. CAPTURED: Customer’s Credit Card account has been charged with the amount of the transaction. DECLINED: transaction was declined. PENDING: Transaction is in pending state CANCELED: authorization of the transaction was canceled ERROR: An error occurred during transaction processing REVERSED: Transaction was reversed REFUNDED: Transaction was refunded REFUND PENDING: Refund is waiting for staff confirmation CHARGEBACK: means that a charge back for the transaction was received by the gateway.

transaction->merchantspecific1

Cond

Character max 200

Merchant specific data for merchant use only, provided during 700 command.

transaction->merchantspecific2

Cond

Character max 200

Merchant specific data for merchant use only, provided during 700 command.

transaction->merchantspecific3

Cond

Character max 200

Merchant specific data for merchant use only, provided during 700 command.

transaction->merchantspecific4

Cond

Character max 200

Merchant specific data for merchant use only, provided during 700 command.

transaction->merchantspecific5

Cond

Character max 200

Merchant specific data for merchant use only, provided during 700 command.

errorcode

NO

Character 3

Error Code of the transaction or 000 if no error condition found.

errormessage

NO

Character max 100

Full description of the error.

transaction

YES

Xml Node

Section containing authorization type

customer->firstname

Character max 50.

First name of the Customer.

customer->lastname

Character max 50.

Section containing authorization type

customer->birthday

Number 1-2 digits

Day of birth of the Customer (1-31) Important Note: If Merchant cannot provide such data, he/she should contact Sales Account Manager. Tag will be set as “Optional” only with GPN’s Sales Account Manager approval.

customer->birthmonth

Number 1-2 digits

Month of birth of the customer (1-12) Important Note: If Merchant cannot provide such data, he/she should contact GPN’s Sales Account Manager. Tag will be set as “Optional” only with Sales Account Manager approval.

customer->birthyear

Number 4 digits

Year of birth of the customer (1900-2100) Important Note: If Merchant cannot provide such data, he/she should contact GPN’s Sales Account Manager. Tag will be set as “Optional” only with Sales Account Manager approval.

customer->email

Character max 100.

Email of the Customer.

customer->countryiso

Character exactly 3.

3 letter ISO country code of the Customer. Full list of codes can be obtained from the website inside your merchant account.

customer->stateregioniso

Character max 3.

1-3 character ISO 3166 state/region/province code of the Customer. Full list of codes can be obtained from the website inside your merchant account.

customer->zippostal

Character max 15.

Customer’s Zipcode or postal code.

customer->city

Character max 50.

Customer’s City

customer->address1

Character max 75.

Customer’s address line 1

customer->address2

Character max 75.

Customer’s address line 2

customer->phone1phone

Character max 20.

Customer’s phone number, including country code and area code. Digits only, without (+) character

customer->phone2phone

Character max 20.

Customer’s phone number, including country code and area code. Digits only, without (+) character

customer->accountid

Character max 50.

Customer unique account id used inside the merchant organization.

customer->ipaddress

Character max 15.

Full IP address of the customer used for this transaction

creditcard

YES

Xml Node

Section containing authorization type

creditcard->brand

Character max 50.

Card Brand: Visa MasterCard Maestro Amex JCB DinnersClub UnionPay

creditcard->last4

Number digit 4

Last 4 number of the card

creditcard->nameoncard

Character max 50.

Full name as it appears on card.

creditcard->billingcountryiso

Character exactly 3.

3-digits ISO country code of the Customer. Full list of codes can be obtained from the website inside your merchant account.

creditcard->billingstateregioniso

Character max 5.

ISO 3166 state/region/province code of the Customer. Full list of codes can be obtained from the website inside your merchant account.

creditcard->billingzippostal

Character max 15.

Customer’s Zip code or postal code.

creditcard->billingcity

Character max 50.

Customer’s City

708 Request Sample

The query can utilize either merchanttransid or gatetransid to identify the transaction, but only one is required. Consequently, the checksum calculation will only include one of these fields based on which is used in the request.

  <?xmlversion="1.0" encoding="utf-8" ?>
	<transaction>
		<apiUser> </apiUser>
		<apiPassword> </apiPassword>
		<apiCmd> </apiCmd>
		<merchanttransid> </merchanttransid>
		<notify> </notify>
		<checksum> </checksum>		
	</transaction> 
							  

708 Response

The response to a 708 – Check transaction status is a plain xml un-encoded that contains the following data:


	<?xmlversion="1.0" encoding="utf-8" ?>
	<transaction>
		<result> </result>
	<transaction>
		<gatetransid> </gatetransid>
		<merchanttransid> </merchanttransid>
		<amount> </amount>
		<created> </created>
		<curcode> </curcode>
		<state> </state>
		<merchantspecific1> </merchantspecific1>
		<merchantspecific2> </merchantspecific2>
		<merchantspecific3> </merchantspecific3>
		<merchantspecific4> </merchantspecific4>
		<merchantspecific5> </merchantspecific5>
		<description> </description>
		<errorcode> </errorcode>
		<errormessage> </errormessage>
	</transaction> 
	<customer> 
			<firstname> </firstname>
			<lastname> </lastname>
			<birthday/> 
			<birthmonth/> 
			<birthyear/> 
			<email> </email>
			<zippostal/> 
			<address1/> 
			<address2/> 
			<phone1phone/> 
			<phone2phone/> 
			<city> </city>
			<countryiso> </countryiso>
			<stateregioniso/> 
		</customer>
		<creditcard> 
			<brand> </brand>
			<last4> </last4>
			<name> </name>
			<billingaddress1/> 
			<billingaddress2/> 
			<billingcity/> 
			<billingzippostal/> 
			<billingcountryiso/> 
		</creditcard> 
		
	</transaction> 

Last updated