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:10] robinc [Examples for a Request] |
developer:api_specification:xml_secure_card_features [2019/12/13 10:17] robinc [Request Body Fields] Added CREDENTIALONFILE |
||
---|---|---|---|
Line 146: | Line 146: | ||
| 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 for Acquirer to the merchant in the response if Credential on File is used. | | ||
</searchtable> | </searchtable> | ||
\\ | \\ | ||
Line 236: | Line 237: | ||
| 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 processing the payment. See **ND004 - Credential on File**.| | ||
</searchtable> | </searchtable> | ||
\\ | \\ |