> For the complete documentation index, see [llms.txt](https://developer.convergegate.com/legacy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.convergegate.com/legacy/card-server-to-server/api-commands/720-credit-request.md).
# 720 – Credit Request
| 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 | 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:
| NODE | REQUIRED | DATA TYPE | 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. |
{% tabs %}
{% tab title="CURL" %}
720 Credit Request Sample
```
```
The 720 response is plain xml un-encoded that contains the following data:
```
```
{% endtab %}
{% tab title="PHP" %}
720 Request Sample
```
require_once 'autoload.php';
use Omnipay\GPNDataEurope\GPNGateway;
set_time_limit(0);
$gpnGateway = new GPNGateway();
$gpnGateway->setApiKey('APIKEY');
$gpnGateway->setApiPassword('APIPASS');
$gpnGateway->setApiUser('APIUSER');
$gpnGateway->setMode(GPNGateway::PROD_MODE);
$gpnGateway->setPROD('https://txtest.txpmnts.com/api/transaction/');
$params = [
'ptid' => '651C6D7D-D360-D29A-AFEE-13CA0F15A0FA', // previous transaction ID
'currency' => 'USD',
'amount' => '10.00',
'description' => 'Description of item',
'firstName' => '',
'lastName' => '',
'email' => '',
'clientIp' => '',
'country' => '', // Country ISO Code
'city' => '',
'TransactionId' => '', // new Merchant Transaction ID
];
try {
// Credit 720
$response = $gpnGateway->credit($params)->send();
printf("%s-%s\n", $response->getCode(), $response->getMessage());
echo 'GPN Ref. No : '; print_r($response->getData()->getrefer());
echo 'Description : '; print_r($response->getData()->getmessage());
echo 'Merchant Transaction ID : '; print_r($response->getData()->getmerchantTransId());
echo 'Status : '; print_r($response->getData()->getstatus());
echo 'Status Code : '; print_r($response->getData()->getstatusCode());
echo 'Gateway Transaction ID : '; print_r($response->getData()->gettransId());
} catch (Exception $exc) {
print_r($exc->getCode(), $exc->getMessage());
}
```
{% endtab %}
{% endtabs %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://developer.convergegate.com/legacy/card-server-to-server/api-commands/720-credit-request.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.