Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
developer:api_specification:xml_payment_features [2019/12/16 15:35] robinc [Examples for a Request] |
developer:api_specification:xml_payment_features [2020/01/17 13:32] vinayh [Notes and Details About the Request] |
||
|---|---|---|---|
| Line 525: | Line 525: | ||
| | ENHANCED_DATA_TEMPLATE | N | Enhanced Data template name to be used when creating the transaction. It fills up any not provided transaction's enhanced data fields. \\ Note that if you use a template, but inform the data during the request, the gateway is just going to use the template to fill the gaps of whatever you didn't inform in your original request. Also, if you inform at least one item in LEVEL_3_DATA component, no item from the template is going to be applied. \\ This field should only be used if you desire to use one of your Enhanced Data Templates (see **[[merchant:existing_merchant:selfcare_system:settings:enhanced_data_templates|Enhanced Data Templates]]** for more details.) \\ This field is only available for terminals with **Transaction Enhanced Data** feature enabled. | | | ENHANCED_DATA_TEMPLATE | N | Enhanced Data template name to be used when creating the transaction. It fills up any not provided transaction's enhanced data fields. \\ Note that if you use a template, but inform the data during the request, the gateway is just going to use the template to fill the gaps of whatever you didn't inform in your original request. Also, if you inform at least one item in LEVEL_3_DATA component, no item from the template is going to be applied. \\ This field should only be used if you desire to use one of your Enhanced Data Templates (see **[[merchant:existing_merchant:selfcare_system:settings:enhanced_data_templates|Enhanced Data Templates]]** for more details.) \\ This field is only available for terminals with **Transaction Enhanced Data** feature enabled. | | ||
| | APPROVALCODE | Y | Approval code provided by the Acquirer for the specific transaction | | | APPROVALCODE | Y | Approval code provided by the Acquirer for the specific transaction | | ||
| - | | CREDENTIALONFILE | Y | Component of the request that can be added in case Credential on File feature is in use for the Terminal processing the Payment. See ND005 - Credential on File. | | + | | CREDENTIALONFILE | Y | Component of the request that can be added in case Credential on File feature is in use for the Terminal processing the Payment. See **ND008 - Credential on File**. | |
| </searchtable> | </searchtable> | ||
| Line 679: | Line 679: | ||
| \\ | \\ | ||
| - | **ND006 - Credential on File** | + | **ND008 - Credential on File** |
| This feature is currently available to TSYS Saratoga terminals. | This feature is currently available to TSYS Saratoga terminals. | ||
| Line 689: | Line 689: | ||
| These fields will only be used on a payment if you have secure card storage enabled. The fields will have the following behavior: Hidden - the gateway accepts the fields, if sent, and adds them to the transaction, but does not show it for the customer. | These fields will only be used on a payment if you have secure card storage enabled. The fields will have the following behavior: Hidden - the gateway accepts the fields, if sent, and adds them to the transaction, but does not show it for the customer. | ||
| - | (new table below note ND006) | + | (new table below note ND008) |
| ^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^ | ^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^ | ||
| Line 1095: | Line 1095: | ||
| **REMEMBER** to change the Terminal ID and Terminal Secret for valid values. Consult the **[[developer:integration_docs|Integration Docs]]** for examples or contact our support team. | **REMEMBER** to change the Terminal ID and Terminal Secret for valid values. Consult the **[[developer:integration_docs|Integration Docs]]** for examples or contact our support team. | ||
| </WRAP> | </WRAP> | ||
| - | |||
| \\ | \\ | ||
| + | Quick Example: | ||
| + | <code xml> | ||
| + | <?xml version="1.0" encoding="UTF-8"?> | ||
| + | <PAYMENT> | ||
| + | <ORDERID>CSV_99769707</ORDERID> | ||
| + | <TERMINALID>2366006</TERMINALID> | ||
| + | <AMOUNT>6.00</AMOUNT> | ||
| + | <DATETIME>11-09-2019:14:02:49:708</DATETIME> | ||
| + | <CARDNUMBER>4444333322221111</CARDNUMBER> | ||
| + | <CARDTYPE>VISA</CARDTYPE> | ||
| + | <CARDEXPIRY>1224</CARDEXPIRY> | ||
| + | <CARDHOLDERNAME>na</CARDHOLDERNAME> | ||
| + | <HASH>f048c44d0340af522d5796110675fb1a</HASH> | ||
| + | <CURRENCY>USD</CURRENCY> | ||
| + | <TERMINALTYPE>1</TERMINALTYPE> | ||
| + | <TRANSACTIONTYPE>1</TRANSACTIONTYPE> | ||
| + | <AUTOREADY>Y</AUTOREADY> | ||
| + | <CVV>123</CVV> | ||
| + | <ADDRESS1>ads</ADDRESS1> | ||
| + | <ADDRESS2>ads2</ADDRESS2> | ||
| + | <POSTCODE>123</POSTCODE> | ||
| + | <CREDENTIALONFILE> | ||
| + | <ORIGINALBRANDTXIDENTIFIER>1234567890</ORIGINALBRANDTXIDENTIFIER> | ||
| + | <STOREDCREDENTIALTXTYPE>SUBSEQUENT_MERCHANT_INITIATED_TXN</STOREDCREDENTIALTXTYPE> | ||
| + | <STOREDCREDENTIALUSE>UNSCHEDULED</STOREDCREDENTIALUSE> | ||
| + | </CREDENTIALONFILE> | ||
| + | </PAYMENT> | ||
| + | </code> | ||
| ==== Response Body Fields ==== | ==== Response Body Fields ==== | ||
| Line 1118: | Line 1145: | ||
| | DATETIME | Response date and time for the transaction, created by the bank. Format: YYYY-MM-DDTHH:MM:SS. Note that this is intentionally in a different format to the request timestamp to highlight the fact that it is a different time.| | | DATETIME | Response date and time for the transaction, created by the bank. Format: YYYY-MM-DDTHH:MM:SS. Note that this is intentionally in a different format to the request timestamp to highlight the fact that it is a different time.| | ||
| | HASH | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**, in the next section. | | | HASH | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**, in the next section. | | ||
| + | | BRANDTXIDENTIFIER | The gateway returns the transaction identifier received from Acquirer to the merchant in the response if Credential on File is used. | | ||
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||