For example: Mr., Mrs., Ms., Dr. This field is commonly omitted. The initials. The first given name. Any subsequent given name or names. May also be used as middle initial. The family or inherited name(s). For example: Ph.D., Jr. (Junior), 3rd, Esq. (Exquire). This field is commonly omitted. Name of the destination. Address of the destination. This element contains information about the application contacting the webservice. This info is useful when debugging troubleshooting technical integration issues. The name of the plugin used to contact this webservice. The version of the plugin used to contact this webservice. The name of the plugin creator used to contact this webservice. The programming language used to contact this webservice. The operating system from which this webservice is contacted. The version number of the operating system from which this webservice is contacted. The full version number (including minor e.q. 1.3.0) of the xsd which is used during integration. DDP can make minor (non-breaking) changes to the xsd. These are reflected in a minor version number. It can therefore be useful to know if a different minor version of the xsd was used during merchant development than the one currently active in production. The name of the company. Chamber of commerce number. In the Netherlands KvK number is mandatory for a company. Other countries this is an optional feature. This field is for future usage. The European Union value added tax (EU VAT) is a value added tax encompassing member states in the European Union VAT area. Joining in this is compulsory for member states of the European Union. As consumption tax, the EU VAT taxes the consumption of goods and services in the EU VAT area. The EU VAT's key issue asks where the supply and consumption occurs thereby determining which member state will collect the VAT and which VAT rate will be charged. This field is for future usage. Care of, usually abbreviated as c/o on envelopes, signifies an intermediary who is responsible for transferring a piece of mail between the postal system and the final addressee. For example, when the addressee has no standard address, is under a corporate mail system, or is being manually forwarded mail sent to a more accessible location. In Australia and New Zealand c/- is often used in place of c/o. This field is for future usage. Address lines must be filled as specific as possible using the house number and optionally the house number addition field. The house number. The addition to the house number. A state or province. Is mandatory for Argentina, Brazil, Canada, China, Indonesia, India, Japan, Mexico, Thailand and the US of A. when PayPal is used as payment method. Shopper's full name. Shopper's e-mail address. Shopper's preferred language. Shopper's gender. Shopper's date of birth. Shopper's phone number. Shopper's mobile phone number. Ip address of the shopper. Will be used in the future for riskchecks. Can be ipv4 or ipv6. Merchant's login name. Merchant's password. The profile that is used to select the payment methods that can be used to pay this order. The expected number of days in which the payment should be processed, or be expired if not paid. Identifies the Point Of Sale terminal. Request for a payment. A reference identifying an initial payment. A linkID token, which is a UUID type 4 (see RFC-4122 and ITU-T Rec. X.667). The result of 3DS authentication done by the shopper. The MD - Merchant Data from the 3DS request/response. This is a parameter from the original start response, so the same type is used. The Payment Authentication Response, containing all relevant data according to the 3DS specifications. The result of iDEAL authorization done by the shopper. Refund zero or more items with a different quantity than originally ordered. Optionally, refund an additional amount. In all cases, the total of the refund request cannot exceed the original order including any already processed refunds. Additional amount to refund when refunding an order. The amount to refund additionally, including VAT. Optional description for this refund. The VAT rate of the additionally refunded amount. Item lines can only be used, when the original order contains the different item lines. Refund a single item code (the ordered quantity is refunded) and/or refund a specific amount. The total of the refund request cannot exceed the original order including any already processed refunds. Optional amount to refund A code or article number identifying an earlier supplied item. Needs to be unique under the payment order the payment is associated with. Optional description for this refund. A code and quantity referring to an earlier supplied item. The payment ID with check digit as generated by the payment system. The state of the authorization. Current known values: This is a new payment without any actions performed on it yet. For this payment the risk check was okay. The risk check for this payment triggered. The user has provided details and is authenticated. The payment system could not start the payment due to a technical error. The shopper is authenticated by the acquirer. The shopper is redirected to the acquirer web-site for authentication. The shopper is not authenticated by the acquirer. Unable to do the authentication of the shopper by the acquirer. This payment is authorized. The shopper is redirected to the acquirer web-site for authorization. Requested authorization for this payment, waiting for a notification from acquirer. The payment was not authorized due to a functional error. Unable to do the payment authorization due to a technical error. The payment is canceled. Payment is not canceled, due to functional error. Payment is not canceled, due to technical error. A cancel request sent to acquirer. Only present when there was a paymentRequest element in the request. The payment was successfully authorized. There was insufficient payment data in the paymentRequest. Redirect the shopper to the payment menu. There was an error initiating the payment. Optional additional data used for invoices. Total net amount for this order. Total VAT amount for this order. Information concerning the ordered items. Name and address to use for shipping. Additional description concerning the payment order. The number of days after communication to the shopper the exhortation period will be initiated. The profile that is used to determine the payment methods for this order during this exhortation period. Message in case of errors or validation failure(s). Message in case of a successful request. A single (line) item for this order. The human-readable name of this item. A code or article number identifying this item. Quantity of this item that's being ordered. Unit of measurement. The attribute can have the following values: PCS - pieces SEC- seconds BYT - bytes KB - kilobytes The description of the item. URL pointing to the location of the order item's image. The image itself can be subject to certain limitations on file size and image dimensions, defined by docdata. The net amount for a single piece of this item. The gross amount for a single piece of this item. The VAT amount for a single piece of this item. The total net amount for this item. The total gross amount for this item. The total VAT amount for this item. Payment information to start a payment. Payment method to be used. Generic credit or debit card payment input. This can be either: 1. A card number and an expiry date 2. A base64 encoded string containing the encrypted card details and the key alias Direct debit payment input. Bank transfer payment input. Point Of Sale payment input. Offline payment input. ELV payment input. iDEAL payment input. Contains considered safe details. When the system is unable to determine if the order is considered safe, this element is omitted. The initial total amount requested for the order. The amount for the order that is currently pending with the shopper. The amount for the order that is currently pending with an acquirer. The amount for the order that is currently approved by an acquirer. The currently captured total amount for the order. The currently refunded total amount for the order. The currently chargedback amount for the order. The currently reversed amount for the order. If multiple currencies are included in the totals, then the approximation, for convenience is based on a conversion. This is the currency that is used to convert to. If multiple currencies are included in the totals, then the approximation, for convenience is based on a conversion. This is the date on which the conversion was performed for the calculation of the totals. Payment method used for the payment. Extended payment information e.g. risk check scores and payment-specific information. Risk checks are controls which can prevent fraud. They can be configured in the back office. Note: there is no paymentInfo for PayPal, PaySafeCard, GiroPay, EPS and PostFinance. They only provide their PaymentMethodName. See the payment-element. The sum of all risk checks. The higher the score, the higher the risk. Scores of 100 or above are canceled automatically. American Express credit card payment information. MasterCard credit card payment information. Visa credit card payment information. Maestro payment information. Mister Cash payment information. Payment information concerning iDEAL. Payment information concerning Sofort. Payment information concerning the bank payment methods. Gift card payment information. Open invoice payment information. SEPA Direct Debit payment information. ELV payment information. Point Of Sale payment information. Point Of Sale payment receipt. The receipt type. A shopper receipt. A merchant receipt. Point Of Sale formatted payment receipt lines. Point Of Sale payment receipt values. Payment information concerning system payments. Shopper bank account information. The results of the cancel operation. No payments found for this order. All payments in this order were already canceled. All payments in this order are canceled successfully. At least one payment in this order was not canceled successfully. Use the status operation to get more details. A request for cancelation has been sent to the acquirer, but no response received for at least one payment in this order. Use the status operation to get more details. Allows to request a new order to be registered. Merchant credentials. Unique merchant reference to this order. Preferences to use for this payment. Preferences to be used for the webmenu. Information concerning the shopper who placed the order. Total order gross amount. Name and address to use for billing. The description of the order. The description that is used by payment providers on shopper statements. Indicates if the cost of the chosen payment method should be added (true) or should not be added (false) to the order amount. Default is false. Note that this will not work for every payment method. In the future, DocData may no longer support this feature. Optionally specifies a request. When it targets an existing previous payment, then that will be used to start a new payment with directly. If it does not point to a payment, then reservations are made as the starting point for upcoming repeated payments. Using "start" with the request instead is highly recommended. Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response of the payment order create request. An error occurred. No payment order was created. A payment order was successfully created. This does not mean that the whole request was processed successfully! The paymentResponse (see child elements) can still contain errors. Generated key identifying the merchant and payment order. Allows to request a full or partial refund. Merchant's credentials. The payment ID on which the refund request needs to be performed. Can be retrieved from the status report. Merchant's internal ID for identifying this refund. Either a simple a refund or a detailed refund. Indicator if any reserved (new) refunds should be canceled in favor of this refund. Default is false, meaning that this new refund is in addition to already reserved refunds. The date on which to refund. The first opportunity after this date for a refund will be used. The default is as soon as possible. Optional, refund bank account information for payment methods for which no information is known to the system yet. If provided here, but not needed, then it will be ignored (e.g. for iDEAL or credit card refunds). Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response to a refund request. An error occurred. No refund request was created. A request for refund was successfully accepted. This does not mean that the whole request will be or has been processed successfully! Allows to request cancellation of the order and its payments. Merchant credentials. Payment order key belonging to the order which needs to be canceled. Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response to a cancel request. Returns summarized information about cancelation of the payments of this order. Use "status" to retrieve more information. Allows to request the start of a new payment. Merchant's credentials. Payment order key belonging to the order for which a transaction needs to be started. Optional payment amount to be used. If left empty, the full payment order's amount will be used. Specifies a request for a recurring payment. It should target an existing previous payment that will be used to start a new payment with directly. Reservations are also made as the starting point for upcoming repeated payments if needed. Must be specified if not giving direct payment request input. Specifies the details needed for starting a payment for a shopper without showing the hosted payment pages. Must be specified if not a subsequent recurring payment. Pay with a token. Optional return url to be used. If left empty, no return url will be used. (Limit is set by Internet Explorer of 2083 characters) Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response to a start request. Allows to request proceeding a payment that was started earlier. Merchant's credentials. The ID of the payment that should be proceeded. 3DS Authentication result data. (tag name cannot start with a number) iDEAL authorization result data. No additional data is required. Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response to a proceed request. Allows to request capture of an amount for a payment authorization. Merchant's credentials. Payment id with check digit identifying the payment. Merchant's internal ID for identifying this capture. Will be returned in the capture response and in status reports. Amount to be captured. If no amount nor an order item code is specified, the capture will be done for the order's total amount. A code or article number identifying an item in the order. If specified, this order item's total (gross) amount will be used for this capture's amount and currency. Optional description for this capture. Indicator whether this is the final capture for this order. Indicator if any reserved (new) captures should be canceled in favor of this capture. Must always be true for captures. The date on which to capture. The first opportunity after this date for a capture will be used. The default is as soon as possible. Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response to a capture request. Allows to request the status of an order and its payments. Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response to a status request. Allows to request the extended status of an order and its payments. Test extensibility of client implementation by returning test elements and attributes indicated by with the names and string value "_any". Response to a extended status request. To be implemented in a future minor version upgrade. Merchant's credentials. Response to a listPaymentMethods request. The name of the sales person. Offline payment information. Key of the token Generic credit or debit card payment input. This can be either: 1. A security code 2. A base64 encoded string containing the encrypted card details and the key alias Redirect instructions. Shopper information needed by 3DS.