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:06] robinc [Examples for a Request] Added ND004 |
developer:api_specification:xml_secure_card_features [2019/12/13 10:12] robinc [Response Body Fields] Added BRANDTXIDENTIFIER field |
||
---|---|---|---|
Line 109: | Line 109: | ||
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. | ||
+ | |||
+ | <searchtable> | ||
+ | ^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^ | ||
+ | | STOREDCREDENTIALTXTYPE | N | Possible values: FIRST_TXN, SUBSEQUENT_MERCHANT_INITIATED_TXN or SUBSEQUENT_CARDHOLDER_INITIATED_TXN| | ||
+ | | STOREDCREDENTIALUSE | N |Possible values: UNSCHEDULED, INSTALLMENT or RECURRING | | ||
+ | </searchtable> | ||
+ | \\ | ||
<code xml> | <code xml> | ||
Line 139: | 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> | ||
\\ | \\ |