Schema Changes from V12.0 through V12.37
The tables below includes elements added in schema versions 12.0 through 12.37:
New Elements in V12.0 through V12.20
New Element |
Parent of |
Child of |
Comments |
---|---|---|---|
|
|
|
|
|
|
|
The |
|
|
|
You can use this element up to 12 times in a transaction to designate a list of preferred debit networks in priority order. The use of this element applies only to merchants using the Prime - PINless Debit Routing service. |
|
|
|
Defines the merchant preference for the routing of this transaction. Possible values are:
The use of this element applies only to merchants using the Prime - PINless Debit Routing service. |
|
|
|
Contains a repeatable child element (up to 12 times) that allows you to specify the preferred debit network or networks for processing this transaction. The use of this element applies only to merchants using the Prime - PINless Debit Routing service. |
|
|
|
The name(s) of the preferred debit network(s). You can include up to 12 names. |
|
|
|
A Worldpay assigned value representing the account range of the card used in the transaction. |
|
|
|
The value, assigned by the card network, is a constant correlation value that represents the cardholder account regardless of updated account numbers or reissued cards. Worldpay always returns the value, when the applicable card network makes it available. |
|
|
|
Defines the type of event occurring. Enum values are:
|
|
|
|
Define the account login name. |
|
|
|
Defines the SHA-2 hash of the password in hexadecimal format. Depending on the hash algorithm, the value must be either 128, 96, 64, or 56 characters. |
|
|
|
Describes the funds disbursement associated with the transaction. If you do not include this element, the value defaults to VMD, Merchant Disbursement. See the cnpAPI Reference Guide for a complete list of enum values. |
|
|
cnpOnlineRequest batchRequest |
A transaction type used to generate a low value token for a submitted high value token. |
|
|
|
Response message for a |
|
|
|
Defines a number of lodging related data points that, when submitted, can result in a more favorable interchange rate. |
|
|
|
Defines customer folio number from your system. |
|
|
|
The date the customer checked in. |
|
|
|
The date the customer checked out. |
|
|
|
Defines the number of nights the guest stays (or plans to stay) at the facility. Note: For Discover it is: # nights * # rooms. |
|
|
|
Defines customer service number of the facility |
|
|
|
Enum values:
|
|
|
|
Defines the per day room charges exclusive of any taxes and fees. |
|
|
|
Defines the per day room tax. |
|
|
|
Defines the total number of adult guests staying (or planning to stay) at the facility (i.e., all booked rooms). |
|
|
|
Defines local phone number of the facility. For a MasterCard transaction, you must include a value for this element to achieve better interchange rates. |
|
|
|
Defines whether or not the facility conforms to the requirements of the Hotel and Motel Fire Safety Act of 1990, or similar legislation. |
|
|
|
Through its child element, defines the type of additional charges associated with the stay of the guest. You can include this element a maximum of six times in a transaction. |
|
|
lodgingCharge |
Defines the type of additional charges associated with the stay of the guest. Enum values are:
|
|
|
|
The Id of the encryption key used to encrypt the account number and/or validation number. |
|
|
|
The encrypted account number. |
|
|
|
The encrypted card validation number. |
(Batch transactions only) |
|
|
You can use this element to submit a description of certain Instruction Based Dynamic Payout transactions (Sub-merchant Debit/Credit or Vendor Debit/Credit). You define the content using the |
|
|
|
The description of the Sub-merchant Debit/Credit or Vendor Debit/Credit transaction. The information appears in the extended detail section of the receiver’s bank statement, if supported by the receiving bank. |
|
|
|
Used to submit the token URL value when submitting an Account Updater request (Batch only) via Access Worldpay. This value must use the following pattern: http.?://.*/.* |
|
|
|
Added to all merchant use of Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
New transaction type for merchants using Dynamic Payout. |
|
|
|
Setting this element to true allows you to skip any real-time account updates on the submitted transaction. |
|
|
|
Used to indicate if the source of the update information is real-time (R) or non-real-time update from cache (N). |
|
|
|
Used to indicate if the authentication used 3DS1 or 3DS2. |
|
|
|
Used to dynamically set the MCC on a per transaction basis. |
|
|
|
Provides the processing location for merchants using Hot-Hot. |
|
|
|
Used for Mastercard Digital Secure Remote Payments |
|
|
|
Existing element added to two more transaction types. |
|
|
healthcareAmounts |
Allows the designation of copay amounts. |
|
|
pinlessDebitResponse |
Provides info about decline reason from the debit network. |
|
|
pinlessDebitResponse |
Provides info about decline reason from the debit network. |
|
|
authorization, captureGivenAuth, credit, forceCapture, sale |
Allows you to designate the transaction as consumer bill pay. |
|
|
capture, credit |
We added the orderId element to the (linked) capture and credit transactions allowing you to designate a new orderId for the capture or credit. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other schema changes (v12.0 through 12.20)
-
New enumerations added to the
processingType
element to support recurring and installment card on file transactions. The new enumerations are:initialRecurring
, andinitialInstallment
. -
New enumerations added to the
processingType
element to support card on file transactions. The new enumerations are:initialCOF
,merchantInitiatedCOF
, andcardholderInitiatedCOF
. -
The Submerchant Credit/Debit and Vendor Credit/Debit transactions moved from the cnpTransaction schema to both the cnpOnline and cnpBatch transaction schema files. This was done to accommodate the use of the
ctxPaymentInformation
element, which is Batch only. -
To accommodate 3DS2, the
authenticationTransactionId
changed from a Base 64 encoded item to a string. Also, the maxLength changed from 28 to 36. -
The maxLength of the
orderId
element changed from 25 to 256 characters. -
IC added as an enum value for the type element.
New Elements in V12.21 through V12.25
New Element |
Parent of |
Child of |
Comments |
---|---|---|---|
|
|
|
Defines the postal mailing address of the cardholder For FastAccess funding transactions. |
|
|
|
Defines the postal mailing address of the vendor in a |
|
|
|
Optional in the schema but required for the Guaranteed Payments service to process a successful fraud check with Signifyd. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Defines the postal mailing address and other information about the underlying retailer selling the product. Required for Discover Installment Payments and American Express Bill Pay. |
|
|
|
Defines additional Card on File data, including information for Visa installments and the Visa Buy Now, Pay Later (BNPL) program. |
|
|
|
Optional in the schema but required for the Guaranteed Payments service to process a successful fraud check with Signifyd.Required for Guaranteed Payments service. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Required for the Guaranteed Payments service. Describes the fulfillment method for the customer's order. Enum values are:
|
|
|
|
Required for the Guaranteed Payments service.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Defines optional lodging-related data points that, when submitted, can result in a more favorable interchange rate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Other schema changes (v12.21 through 12.25)
-
The maxLength of the
authenticationValue
element changed from 56 to 512 characters. -
The
fundingCustomerId
andfundingSubmerchantId
elements are now optional child elements forfastAccessFunding
andvendorCredit
andvendorDebit
. -
New enumerations added to
orderChannel
to support Guaranteed Payments. The new enumerations are:IN_STORE_KIOSK
,MARKETPLACE
,MIT
,MOBILE_APP
,PHONE
,SOCIAL
,WEB
.
New Elements in V12.26 through V12.37
The table below describes elements added, changed, or deleted in schema versions 12.26 through 12.37. Click the element links to navigate to the Worldpay eComm cnpAPI Reference Guide for further information.
Schema |
|
Comments |
---|---|---|
12.26
|
New Element added:
New Element added: tripLegData
|
New elements and child elements added in support of railway travel. |
Element change: addtionalCOFData
|
For successful payments using Visa’s Buy Now, Pay Later program, |
|
12.27
|
New Element added: authMax
|
Additional elements added to auth and sale responses when AuthMax is used with a Network Payment Token. |
Element changes:
|
Various changes to child elements of |
|
12.28 |
Element changes: tripLegData
|
Increases the Rail Travel tripLegCount usage limit for Discover and Mastercard to 998 from a current limit of 99. |
12.29 |
New Element added: sellerInfo
New Element added: sellerAddress
|
Use these optional elements if you are enabled for Guaranteed Payments and wish to pass additional details associated with transactions made by a third-party seller. |
12.30 |
New Element added:
New Element added:
|
Required if you submit an Incremental Authorization, used by certain Travel and Entertainment (T&E) merchants. when final purchase amounts are unknown. |
12.31 |
New Element added: foreignRetailerIndicator
|
New element must be present when the marketplace and retailer are not in the same region (country). A value of 'F' indicates that the retailer is located in a different country. |
12.32 |
Element changes: customerIpAddress
|
Data type change due to support for IPv6 for Guaranteed Payments and Fraudsight. |
12.33 |
New Element added: shipmentId
Element change: subscription
|
Optional elements added to support recurring and subscription merchants for the Guaranteed Payments Service. This is an added functionality for the existing |
12.34 |
New Element added: echeckCustomerId
Element changes:
|
Optional element added as a child of |
12.35 |
New Element added: accountFundingTransactionData
Element changes:
|
Optional element and child elements added to define the receiver of the account funding transaction. |
12.36 |
New Element added: fraudCheckAction
New Element added: finicityAccountRequest
New Element added: finicityAccountResponse
New Element added: finicityURLRequest
New Element added: finicityURLResponse
Element changes:
|
Optional element to support Guaranteed Payment Service.
The features associated with Finicity and Account Funding Transactions are not yet generally available. Please consult you Relationship Manager for additional information.
The same enum values added for |
12.37 |
New Element added: receiverAccountNumberType
New Element added: BNPLAuthorizationResponse
New Element added: BNPLCaptureRequest
New Element added: BNPLCaptureResponse
New Element added: BNPLRefundRequest
New Element added: BNPLRefundResponse
New Element added: BNPLCancelRequest
New Element added: BNPLCancelResponse
New Element added: BNPLInquiryRequest
New Element added: BNPLInquiryResponse
New Element added: postCheckoutRedirectUrl
New Element added: inquiryResult
New Element added: inquiryResultType
|
The features associated with Visa Buy Now Pay Later (BNPL) and Account Funding Transactions are not yet generally available. Please consult you Relationship Manager for additional information. |