Reference > Shop flow URLs > Order Management subsystem URLs > Order payment


This URL changes the details of an existing payment instruction in an order.



Controller command


Implementation class


Commands called



URL structure


Diagram of the URL structure: The URL starts with the fully qualified name of the WebSphere Commerce Server and the configuration path, followed by the URL name, PIEdit , and the ? character. End the URL with a list of parameters in the form of name-value pairs. Separate each <a href=name-value pair with the & character. For a detailed description of the parameters and their values, see the list entitled Parameter values." />

Parameter values


Required: The identifier of the order for which the payment method is to be changed.


Required: The numeric identifier of the payment instruction to modify. The piId can be obtained from the EDPPaymentInstructionsDataBean data bean and represents the combination of the payment method, payment amount, and any protocol data.


The new amount in the order currency to be used for this payment instruction. The format of this number must fit the rules for a java.math.BigDecimal object. The number must use a period for a decimal place.


(Required if PayMethodId is not specified) The payment policy identifier. It is the primary key of the payment business POLICY table. (Table POLICY with column policytype_id = "Payment").


(Required if policyId is not specified) See Payment methods for supported methods.


Additional name-value pairs separated by an ampersand (&) that will be passed to the payment plug-in or payment processor as additional data required by that payment protocol. If an existing keyword is passed in, the value for the keyword will be overwritten in the payment instruction.


The flag to indicate whether the payment method should be edited even though the target amount is less than the authorized amount or there is some deposited amount for the payment method. For these scenarios, tickler will be created to make sure the CSR is notified. The default value is false.


The flag indicates whether the payment protocol data should be edited by this request.


Payment protocol data should be edited by this request. The default value.


Payment protocol data should not be edited by this request.


The flag to indicate whether the payment method amount should be edited by this request. If piAmount parameter is provided and this flag is true, the amount will be edited by this request. The default value is true.


The purchase order number specified to the order. This parameter is optional, if it is set, the value of the purchase order number will send back to the response properties to be displayed in the page.


The view name which is redirected to when the execution fails. If this parameter is provided, the default error view name is PaymentInstructionErrorView.


The billing address identifier.


The payment term and condition identifier for this payment instruction. This parameter is used by the business customer.


The flag to indicate whether the payment protocol data should be extracted from the payment term and condition identified by paymentTCId paramater and ignore any protocol data passed in the request properties.


Payment protocol data is extracted.


The default value. Payment protocol data is not extracted.


The URL to be redirected when the command completes successfully.

Example 1

The following example changes the payment amount associated with the AMEX credit card payment method (The payment policy identifier in POLICY table is -9803) for order 112233, to an amount of 75.01 USD for payment instruction 27022.


Example 2

The following example changes the check routing number (due to a typographical error) for an electronic check transaction. Because the check routing number is supplied as protocol data, the &check_routing_number name-value pair is entered. The other protocol data which are not passed by PIEdit will be kept the same as before.



Check if the order is locked by the current CSR. If the order is not locked and called by a CSR, or if it is locked by another CSR, an exception is thrown

If the payment instruction to be edited is unbound (An unbound payment instruction for the order only has the information for the payment method and the payment policy):


Exception conditions

Related concepts

Payment instructions

Payment methods

Related reference



PIRemove URL


Search Tips   |   Advanced Search