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_secure_card_features [2019/12/13 10:23] robinc [Response Body Fields] Added STOREDCREDENTIALUSE, STOREDCREDENTIALTXTYPE, BRANDTXIDENTIFIER |
developer:api_specification:xml_secure_card_features [2019/12/13 10:47] robinc [Response Body Fields] Added BRANDTXIDENTIFIER field |
||
|---|---|---|---|
| Line 533: | Line 533: | ||
| | DATETIME | Y | Request date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | | DATETIME | Y | Request date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | ||
| | HASH | Y | 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 | Y | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**, in the next section. | | ||
| + | | CREDENTIALONFILE | YN | Component of the request that can be added in case Credential on File feature is in use for the terminal. See **ND003 - Credential on File**. | | ||
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||
| Line 575: | Line 576: | ||
| \\ | \\ | ||
| + | |||
| + | **ND003 - Credential on File** | ||
| + | |||
| + | This feature is currently available to TSYS Saratoga terminals and is configurable by customer support. The Credential on File details will be included in the response if an empty CREDENTIALONFILE tag is sent in request. | ||
| + | |||
| + | Quick example: | ||
| + | |||
| + | <code xml> | ||
| + | <?xml version="1.0" encoding="UTF-8"?> | ||
| + | <SECURECARDSEARCH> | ||
| + | <MERCHANTREF>CSV_84828896</MERCHANTREF> | ||
| + | <TERMINALID>2366006</TERMINALID> | ||
| + | <CREDENTIALONFILE/> | ||
| + | <DATETIME>19-09-2019:12:21:52:441</DATETIME> | ||
| + | <HASH>054d6301a9d78d703772e7f44bca256f</HASH> | ||
| + | </SECURECARDSEARCH> | ||
| + | </code> | ||
| ==== Response Body Fields ==== | ==== Response Body Fields ==== | ||
| Line 589: | Line 607: | ||
| | DATETIME | Response date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | | DATETIME | Response date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | ||
| | 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 if Credential on File is sent in request.| | ||
| + | | STOREDCREDENTIALUSE | Possible vales: UNSCHEDULED, INSTALLMENT or RECURRING. Returned if Credential on File sent in request. | | ||
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||
| Line 674: | Line 694: | ||
| | DATETIME | Y | Request date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | | DATETIME | Y | Request date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | ||
| | HASH | Y | 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 | Y | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**, 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. See **ND003 - Credential on File**. | | ||
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||
| Line 718: | Line 739: | ||
| </WRAP> | </WRAP> | ||
| \\ | \\ | ||
| + | |||
| + | |||
| + | **ND003 - Credential on File** | ||
| + | |||
| + | This feature is currently available on TSYS Saratoga terminals and is configurable by customer support. The Credential on File details will be included in the response if an empty CREDENTIALONFILE tag is sent in request. | ||
| Line 729: | Line 755: | ||
| | DATETIME | Response date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | | DATETIME | Response date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS. | | ||
| | 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 if Credential on File is sent in request.| | ||
| + | | STOREDCREDENTIALUSE | Possible values: UNSCHEDULED, INSTALLMENT or RECURRING returned if Credential on File sent in request.| | ||
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||