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/05/31 16:33] vinayh [Notes and Details About the Request] |
developer:api_specification:xml_payment_features [2019/12/12 13:08] robinc [Request Body Fields] Added CREDENTIALONFILE |
||
|---|---|---|---|
| Line 68: | Line 68: | ||
| | 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. | | ||
| | FRAUDREVIEWSESSIONID | N | This field should contain the value of THEIR_SESSION_ID parameter that a merchant integration uses to configure its session with Fraud Solution. See the **ND003 - Using Fraud Solution**, in the next section. | | | FRAUDREVIEWSESSIONID | N | This field should contain the value of THEIR_SESSION_ID parameter that a merchant integration uses to configure its session with Fraud Solution. See the **ND003 - Using Fraud Solution**, in the next section. | | ||
| + | | CREDENTIALONFILE | N | 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 2370: | Line 2370: | ||
| | TERMINALID | Terminal to which the transaction was submitted. | | | TERMINALID | Terminal to which the transaction was submitted. | | ||
| | UNIQUEREF | Transaction's unique referenced. Same as provided at the request. | | | UNIQUEREF | Transaction's unique referenced. Same as provided at the request. | | ||
| - | | ORDERID | Transaction's order id, provided when the transaction was submitted. | | ||
| | TRANSACTION_STATUS | Current status of the transaction. | | | TRANSACTION_STATUS | Current status of the transaction. | | ||
| | TRANSACTION_DATE | Date time of the transaction's processing. | | | TRANSACTION_DATE | Date time of the transaction's processing. | | ||