Schema Changes from V11.0 through V11.4
The V11.x schema include all functionality available in V10.x, as well as several features/capabilities added to V9.x, but not V10.x (e.g., ideal and giropay).
For all 11.x family of schema, the id
attribute is required. Linked transactions (i.e., transactions that use the litleTxnId
to reference the parent transaction) no longer return a response code of 001 - Transaction Received in the XML response message, as they did in V10.x. You receive either a 000 - Approved or a decline code, but you must still either pick up the Declined Transaction SSR report, or view the Declined transaction report in the eComm iQ to determine the final disposition of the approved transactions.
The table below includes elements added in schema version 11.0.
TABLE 1-9 New Elements in V11.0 through V11.4
New Element |
Parent of |
Child of |
Comments |
---|---|---|---|
|
|
|
Used for Gift Card Auth Reversals
|
|
|
|
Used to link reversal or capture transaction to original Gift Card transaction.
|
|
|
|
Used to link reversal or capture transaction to original Gift Card transaction.
|
|
|
|
Used to link reversal or capture transaction to original Gift Card transaction.
|
|
|
|
Used to link reversal transaction to original Gift Card transaction.
|
|
|
|
Used to link reversal or capture transaction to original Gift Card transaction.
|
|
|
|
Response to a giftCardAuthRevers al transaction.
|
|
|
|
Used for Gift Card Captures
|
|
|
|
Specifies the amount to capture. |
|
|
|
Response to a
|
|
|
|
Used for Gift Card Credits
|
|
|
|
Specifies the amount to credit. |
|
fraudResult |
|
Response to a
|
|
Note: Although shown in the schema,
|
|
Provides details about the beginning, ending, and available balance on a Gift Card, as well as the cash back amount, if applicable. Note: This element already existed in the schema. In this release,
|
|
|
|
Specifies the authorization code of the gift Card transaction. |
|
|
|
Specifies a Worldpay generated identifier associated with the transaction in our systems. Retain for possible use in reversal transactions. |
|
|
|
Specifies a Worldpay generated sequence number associated with the transaction in our systems. Retain for possible use in reversal transactions. |
|
|
|
Specifies a low value token, replacing the CVV value. |
(attribute) |
|
|
New attribute (boolean) for use by Payment Facilitators using Dynamic Payout and enabled for Same Day Funding. A value of True indicates the desire for same day funding of the funding instructions in the Batch. |
|
|
|
This element, which was removed in V10.0 and above, has been added back to the response message. |
(attribute) |
|
|
New attribute (boolean) for use by Payment Facilitators using Dynamic Payout and enabled for Same Day Funding. A value of True indicates the desire for same day funding of the funding instruction. |
|
|
litleOnlineRequest
|
The parent element for the transaction type that a Payment Facilitator uses to distribute funds to themselves (i.e., from the PayFac Settlement Account to the PayFac Operating Account). |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from the PayFac Operating Account back to the PayFac Settlement Account. |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from the PayFac Settlement Account to the Sub-merchant Account. |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from the Sub-merchant Account to the PayFac Settlement Account. |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from the PayFac Settlement Account to the PayFac Reserve Account. |
reserveDebit |
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from the PayFac Reserve Account to the PayFac Settlement Account. |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for information returned to you in response to a |
reserveDebitRespon se |
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from the PayFac Settlement Account to a third party that issues physical checks on behalf of the Payment Facilitator. |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from a third party who issues physical checks on the Payment Facilitator’s behalf to the PayFac Settlement Account. |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from the PayFac Settlement Account to a Vendor account. |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
The parent element for the transaction type that a Payment Facilitator uses to move funds from a Vendor account to the PayFac Settlement Account. |
|
|
|
The parent element for information returned to you in response to a |
|
|
|
A transaction type that allows you to void an unsettled Dynamic Payout Funding Instruction. |
|
|
|
The response message to a |
|
(choice) |
|
A Dynamic Payout transaction type that allows funds transfer to certain debit cards within 30 minutes.
|
|
|
|
The response message to a
|
Other schema changes:
-
The max length of the
id
attribute changed from 25 characters to 36 characters. -
The version element, a child of
applepay
changed from 20 characters to 10 characters. -
Dynamic Payout Funding Instructions, which were Batch only, are now available as Online transactions.
-
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
.