Schema Changes from V7.1 through V8.0
The table below specifies elements added in schema versions 7.1, 7.2, 7.3, and 8.0
TABLE 1-5 New Elements V7.1 to V8.0
New Element |
Parent of |
Child of |
Comments |
---|---|---|---|
|
|
|
|
|
|
|
Consult your Relationship Manager before using. |
|
|
|
Parent of Enhanced Auth information |
|
|
|
Enum Values:
|
|
|
|
Enum Values:
|
|
|
|
Parent of token information |
|
|
|
Request for token to replace card number |
|
|
|
Response for request for token to replace card number |
|
|
|
The token used to replace the card account number. |
|
|
|
Provides BIN info when tokens are generated |
|
|
|
Provides token for tokenized merchants submitting card number in transaction requests |
|
|
|
Used to provide details of Healthcare amounts |
|
|
|
Used to provide details of Healthcare amounts |
|
|
|
Must be set to true for Healthcare transactions |
|
|
|
Total of healthcare amounts. |
|
|
|
Prescription component of healthcare amounts. |
|
|
|
Vision component of healthcare amounts. |
|
|
|
Clinic/other component of healthcare amounts. |
|
|
|
Dental component of healthcare amounts. |
|
|
|
used for eCheck Verification |
|
|
|
used for eCheck Verification |
|
|
|
used for eCheck Verification |
|
|
billToAddress |
used for eCheck Verification |
|
|
fraudResult |
American Express AVS for email and phone |
|
|
|
Used to provide info about automatic NOC updates |
|
|
|
Used to provide info about automatic NOC updates |
|
|
|
Used to provide info about automatic NOC updates |
|
|
|
Note: The transaction tracking feature was added in October 2011 without a revision to the schema version. If you coded to V7.3 (or any 7.x version) prior to October 2011, you must modify your coding to take advantage of this feature. |
|
|
|
Used to sort transactions by marketing campaign |
|
|
|
Used to sort transactions by affiliate sales |
|
|
|
Used to sort transactions by merchant designated values |
|
|
|
Note: This control and its child was added in December 2011 without a revision to the schema version. If you coded to V7.3 (or any 7.x version) prior to December 2011, you must modify your coding to take advantage of this control. |
|
|
|
Used to indicate who merchant or Worldpay) controls recycling of the transaction should it be declined. Also determines where the transaction is counted for the purposes of A/B testing. |
|
|
|
Can be used as an alternate to Note: This identifier was added to V7.3 in February 2012 without a revision to the schema version. If you coded to V7.3 prior to February 2012, you must modify your coding to take advantage of this element. |
|
|
|
|
|
|
|
Note: This flag was added to V7.3 in February 2012 without a revision to the schema version. If you coded to V7.3 prior to February 2012, you must modify your coding to take advantage of this element. |
|
|
|
Contains a child element providing the Vantiv transaction Id of an associated credit transaction (see below). Note: This element was added to V7.3 in January 2013 without a revision to the schema version. If you coded to V7.3 prior to January 2013, you must modify your coding to take advantage of this element. |
|
|
|
The Vantiv transaction Id of the credit transaction automatically issued by the system when you use a Void transaction to halt the Recycling Engine, but the transaction is already approved and captured. (Auto-refund option must be enabled.) |
Other schema changes:
-
Beginning with cnpAPI schema version 7 response messages no longer include the
xmlns
attribute. -
Added new enumeration, FSA, as a a possible response (value) for the
type
element, whentype
is a child offundingSource
. -
All parents of the
token
element allow a choice between eithercard
andtoken
, orcard
,token
, andpaypal
.