720 – Credit Request
Allows the merchant to submit a request for credit to the cardholder’s Credit Card.
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
720
3 digit numeric transaction code must be 720
transaction
YES
Xml Node
Section containing Transaction Information
transaction->merchanttransid
YES (4)
YES
Character max 50.
Merchant transaction id must be included in the request. Merchant transaction id must be unique for each transaction.
transaction->amount
YES (5)
YES
Number with point decimal
Full amount to charge in currency specified. The amount must be specified as a number with decimal point and 2 digits to the right of the decimal point. Decimal separator must be point (.). example: 3500.25 = Three thousand five hundred units of currency and twenty five hundredths of a single unit of currency.
transaction->curcode
YES (6)
YES
Character 3.
May only use currencies specified in the Merchant Agreement.
transaction->statement
YES
Character max 100.
Purpose of the credit. When available, that descriptor may be used in the billing statement of the card holder.
transaction->description
YES
Character max 100.
Description of the charge. When available, that description may be used in the billing statement of the card holder.
transaction->merchantspecific1
OPT
Character max 200.
Merchant specific data for merchant use only. Data sent in this field will be stored and sent in any communication or response to the merchant.
transaction->merchantspecific2
OPT
Character max 200.
Merchant specific data for merchant use only. Data sent in this field will be stored and sent in any communication or response to the merchant.
transaction->merchantspecific3
OPT
Character max 200.
Merchant specific data for merchant use only. Data sent in this field will be stored and sent in any communication or response to the merchant.
transaction->merchantspecific4
OPT
Character max 200.
Merchant specific data for merchant use only. Data sent in this field will be stored and sent in any communication or response to the merchant.
transaction->merchantspecific5
OPT
Character max 200.
Merchant specific data for merchant use only. Data sent in this field will be stored and sent in any communication or response to the merchant.
customer
YES
Xml Node
Section containing Customer Information
customer->firstname
YES
Character max 50.
First name of the Customer.
customer->lastname
YES
Character max 50.
Last name of the Customer.
customer->accountid
YES
Character max 50.
Customer unique account id used inside the merchant organization.
customer->ipaddress
YES
Character max 15.
Full IP address of the customer used for this transaction
customer->email
YES
Character max 100.
Email of the Customer.
customer->countryiso
YES
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
COND
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
YES
Character max 15.
Customer’s Zipcode or postal code.
customer->city
YES
Character max 50.
Customer’s City
creditcard
COND
Xml Node
Section containing sepa bank account Information. Required for sepa transactions, forbidden for credit card transactions.
creditcard->ccnumber
YES (7)
YES
Character max 16.
Full credit card number without dashes or separators. Only numbers.
checksum
YES
Character 3
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.
720 – Response
Response Data description:
result
YES
Character
Indicates the result of the transaction. SUCCESS: Customer’s Credit Card account has been credited with the amount of the transaction. DECLINED: transaction was declined. ERROR: An error has been detected in the request. The transaction has NOT been accepted by the Gateway and thus No processing has taken place and No record for the transaction has been created. PENDING: Depending on the Acquiring Bank and/or the Merchant Account Agreement, the requested credit has been successfully submitted, but has not been released to the Issuing Bank. Once the credit request has been successfully processed by the Acquiring Bank, an 820 Notification will be sent to Merchant.
merchanttransid
YES
Character max 50.
Unique merchant transaction id received in the request.
transref
OPT
Integer
System transaction reference number. Will be sent in the response only if the result is not ERROR. In the case of ERROR, a guid based identification number will be sent instead of an integer. Merchant should save this reference number for support and troubleshooting. The transaction ID used for Refunds and other transaction activity will be sent in the Merchant Notification to the URL furnished by the Merchant and specified in the Merchant Profile.
errorcode
YES
Character 3
Error Code of the transaction or 000 if no error condition found.
errormessage
OPT
Character max 100
Full description of the error.
description
OPT
Character no limit
Optional details of the transaction except in the case of DECLINED and then the reason for the decline. May be null.
720 Credit Request Sample
The 720 response is plain xml un-encoded that contains the following data:
Last updated