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:46] robinc [Examples for a Request] Added ND008 example |
developer:api_specification:xml_payment_features [2020/03/05 15:22] robinc [Examples for a Request] removed 'configurable by customer support' |
||
---|---|---|---|
Line 313: | Line 313: | ||
**ND008 - 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. The COF tags are required for the following usage: |
- | + | ||
- | 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). | * * 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. | + | 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. | To provide a transaction with COF, your request needs to add the Credential on File component and its fields, as described below. | ||
Line 679: | Line 676: | ||
\\ | \\ | ||
- | **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. The COF tags are required for the following usage: |
- | + | ||
- | 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). | * * 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 adds them to the transaction, but does not show it for the customer. | + | 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 1073: | Line 1067: | ||
**ND008 - Credential on File** | **ND008 - Credential on File** | ||
- | This feature is current available to TSYS Saratoga terminals. | + | This feature is current available to TSYS Saratoga terminals. The COF tags are required for the following usage: |
- | + | ||
- | 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) | * * 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, if sent, and adds them to the transaction, but does not show it for the customer. | + | The fields will have the following behavior: Hidden - the gateway accepts, if sent, and adds them to the transaction, but does not show it for the customer. |
To provide a transaction with COF, your request needs to add the Credentials on File component and its fields, as described below. | To provide a transaction with COF, your request needs to add the Credentials on File component and its fields, as described below. | ||
Line 1145: | Line 1136: | ||
| 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> | ||
\\ | \\ |