This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
developer:api_specification:xml_account_verification_features [2019/05/22 12:20] robinc [Request Body Fields] Added content |
developer:api_specification:xml_account_verification_features [2019/12/13 11:15] robinc [Response Body Fields] Added BRANDTXIDENTIFIER field |
||
---|---|---|---|
Line 28: | Line 28: | ||
| ADDRESS1 |N| The first address. Required for AVS.| | | ADDRESS1 |N| The first address. Required for AVS.| | ||
| ADDRESS2 |N| Second line of address. Required for AVS. Same as ADDRESS1| | | ADDRESS2 |N| Second line of address. Required for AVS. Same as ADDRESS1| | ||
- | | POSTCODE | N|Post cde for the address. Required for AVS. | + | | POSTCODE | N|Post cde for the address. Required for AVS.| |
| 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 give 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 give at the **ND001-Hash Formation**, in the next section.| | ||
+ | | CREDENTIALONEFILE |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**.| | ||
==== Notes and Details About the Request ==== | ==== Notes and Details About the Request ==== | ||
Line 78: | Line 78: | ||
**REMEMBER** to change the Terminal ID and Terminal Secret for valid values. Verify the [[developer:integration_docs|Integration Docs]] for viable examples or contact our support team. | **REMEMBER** to change the Terminal ID and Terminal Secret for valid values. Verify the [[developer:integration_docs|Integration Docs]] for viable examples or contact our support team. | ||
</WRAP> | </WRAP> | ||
+ | |||
+ | **ND004 - Credential on File** | ||
+ | |||
+ | This feature is currently available to TSYS Saratoga terminals. The field CREDENTIALONFILE is sent to get the BRANDTXIDENTIFIER in the response message. | ||
+ | |||
+ | ==== Examples for a Request ==== | ||
+ | |||
+ | * **Scenario**: Simple request to check a card. | ||
+ | * **Terminal**: <6491002 | ||
+ | * **Terminal Secret**: x4n35c32RT | ||
+ | |||
+ | <code xml> | ||
+ | <?xml version="1.0" encoding="UTF-8"?> | ||
+ | <ACCOUNT_VERIFICATION> | ||
+ | <TERMINALID>6491002</TERMINALID> | ||
+ | <CARDNUMBER>4916163721669613</CARDNUMBER> | ||
+ | <CARDEXPIRY>1122</CARDEXPIRY> | ||
+ | <CARDHOLDERNAME>acc verif</CARDHOLDERNAME> | ||
+ | <CVV>999</CVV> | ||
+ | <CREDENTIALONFILE/> | ||
+ | <ADDRESS1>addr 1</ADDRESS1> | ||
+ | <ADDRESS2>addr 2</ADDRESS2> | ||
+ | <POSTCODE>postcode</POSTCODE> | ||
+ | <DATETIME>23-01-2019:09:24:16:105</DATETIME> | ||
+ | <HASH>821cb691de21380b42efa97276ab0cc829c9fdfbcb28f5890492622c6a78093eeb28862b4d721e0e2f8db3a521eefda052da51979da6f66578a7b704b7c8aed5</HASH> | ||
+ | </ACCOUNT_VERIFICATION> | ||
+ | </code> | ||
+ | |||
+ | |||
==== Response Body Fields ==== | ==== Response Body Fields ==== | ||
Line 88: | Line 117: | ||
| DATETIME | Request date and time. Format: DD-MM-YYYY:HH:MM:SS:SSS | | | DATETIME | Request 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 in the response if Credential on File is used| | ||
==== Notes and Details on the Response ==== | ==== Notes and Details on the Response ==== |