Extended data in payments or credits

Some payment plug-ins require extra protocol data or keywords to communicate with a back-end system. This extra protocol data called extended data is in addition to the standard attributes defined in the PaymentInstruction definition. Extended data is any data other than the currency, amount of the payment instruction, and the payment method name. For example, credit card number, expiration, and billing address are extended data.


Collecting extended data

Extended data is collected in the following ways:


Editing extended data

Use the WebSphere Commerce Accelerator to add, edit, or delete extended data for payment instructions, pending payments or credit transactions. The extended data for a payment instruction lists both the common protocol keywords and unique keywords required for a payment method. This list corresponds to the list of keywords found in the JSP snippet supporting the payment method.


Optional parameters for all payment methods


Required parameters for all payment methods

For all the payment methods, a payMethodId is required. Also, we are strongly recommended to pass a policyId parameter from the store front. This is a very useful parameter for order processing.


Required parameters when using Address Verification Service (AVS)

To make use of the AVS feature, you should pass a billing_address_id parameter, or five parameters that combine to provide this information together. Namely, these are billto_firstname, billto_lastname, billto_address1, billto_city, and billto_stateprovince.


Paymentech specific

Unless specified, these attributes are optional.


Credit card specific


Electronic Check specific


Gift Certificates (GCt), Gift Cards (GCd) and Stored value (SV) cards in general


Cash on deliver (COD) or Bill me later


Credit Line or Line of Credit