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:20] robinc [Examples for a Request] Added ND008 |
||
|---|---|---|---|
| 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 309: | Line 309: | ||
| \\ | \\ | ||
| + | |||
| + | |||
| + | **ND008 - Credential on File** | ||
| + | |||
| + | This feature is currently available to TSYS Saratoga terminals. | ||
| + | |||
| + | Two usages: | ||
| + | * Processing transaction with Secure Card (stored in Nuvei Gateway) but using the same Secure Card for different usage. | ||
| + | * Processing transaction in clear card but token vaulted externally (outside Nuvei Gateway). | ||
| + | |||
| + | 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 add them to the transaction, but does not show it to the customer. | ||
| + | |||
| + | To provide a transaction with COF, your request needs to add the Credential on File component and its fields, as described below. | ||
| + | |||
| + | ^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^ | ||
| + | | ORIGINALBRANDTXIDENTIFIER | N | String, max length is 64, Merchant sends the transaction identifier if received from acquirer. | | ||
| + | | STOREDCREDENTIALTXTYPE | N | Possible values: FIRST_TXN_SUBSEQUENT_MERCHANT_INITIATED_TXN or SUBSEQUENT_CARDHOLDER_INITITATED_TXN | | ||
| + | | STOREDCREDENTIALUSE | N | Possible values: UNSCHEDULED, INSTALLMENT or RECURRING. | | ||
| + | |||
| + | \\ | ||
| + | |||
| + | Quick example: | ||
| ==== Response Body Fields ==== | ==== Response Body Fields ==== | ||
| Line 2370: | Line 2392: | ||
| | 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. | | ||