Introduction. 1) Receiving Order Data via XML. Configuration. Receiving XML Data. Version 3 Integration Guide

(1)

Introduction

This guide explains how to integrate external custom applications with RedCart order data. It is intended for developers of lab software, studio management software, or any other custom application that would like to integrate with RedCart order data. There are essentially two methods that you can use to integrate with RedCart:

1) Receiving Order Data via XML: You can have RedCart send order data to your external application in XML form when orders are placed in the RedCart system.

2) Using RedCart to Process Payments: You can also use RedCart as an extension of your software application to process payments. Your custom software application can use RedCart as the checkout mechansim by posting transaction data to the cart in a standard HTML form post.

1) Receiving Order Data via XML

RedCart can be configured to automatically send order data to an external URL when orders are placed in the RedCart system. When orders are received, the system can be configured to automatically post XML data to an external URL. The XML data will contain the customer and order information, including all items ordered. The order data also contains cropping information for each image so that photo finishing labs can use the information to crop high resolution images and process the order. Please only activate order data integration if your studio management software, photo finishing lab, or custom application, has been developed to integrate with RedCart.

Configuration

To configure RedCart to send XML order data to an external URL, simply visit the Configuration -> Business Information screen from your RedCart Admin application and enter a URL into the Order Data Integration section. You can also utilize four custom pass through variables that will be included in the order XML for customer identification or other purposes. The values for these variables will simply pass through, and will be included in the XML for each order. The URL should point to a script running on your server that will parse the order XML data for use in your custom application. Also, make sure to check the Activate box!

Receiving XML Data

When order data integration has been activated, RedCart will post XML data to the configurable URL. However, if the receiving server is down or offline, there is no guarantee that the data is going to be received. RedCart will post the data to this URL but will not wait for a confirmation response. There is currently no logic in the RedCart system that will queue up the order and retry later if a confirmation was not received. Please note that we will be adding logic to repost the data in situations where a confirmation was not received in a future version of RedCart.

(2)

Example PHP code for receiving RedCart XML:

<?php

$rcxml = file_get_contents('php://input'); // do something with the xml

echo $rcxml; ?>

An Example Order XML String:

<?xml version="1.0" encoding="UTF-8"?> <RC_ORDER VERSION=”2.1”> <CUSTOMER_INFO> <CUSTOM1>test1</CUSTOM1> <CUSTOM2>test2</CUSTOM2> <CUSTOM3>test3</CUSTOM3> <CUSTOM4>test4</CUSTOM4> <ORDER_ID>1988</ORDER_ID> <ORDER_DATE>2009-08-29 16:36:16</ORDER_DATE> <FIRST_NAME>Kasi</FIRST_NAME> <LAST_NAME>Hyland</LAST_NAME>

<ADDRESS_1>1234 REDCART RD</ADDRESS_1> <ADDRESS_2></ADDRESS_2> <CITY>MINNEAPOLIS</CITY> <STATE>MN</STATE> <PROVINCE></PROVINCE> <COUNTY></COUNTY> <ZIP>55082</ZIP> <COUNTRY_CODE>US</COUNTRY_CODE> <PHONE>800-988-2278</PHONE> <EMAIL>[email protected]</EMAIL> <SHIPPING_SAME_AS_BILLING>TRUE</SHIPPING_SAME_AS_BILLING> <SHIP_FIRST_NAME></SHIP_FIRST_NAME> <SHIP_LAST_NAME></SHIP_LAST_NAME> <SHIP_ADDRESS_1></SHIP_ADDRESS_1> <SHIP_ADDRESS_2></SHIP_ADDRESS_2> <SHIP_CITY></SHIP_CITY> <SHIP_STATE></SHIP_STATE> <SHIP_PROVINCE></SHIP_PROVINCE> <SHIP_COUNTY></SHIP_COUNTY> <SHIP_ZIP></SHIP_ZIP> <SHIP_COUNTRY_CODE></SHIP_COUNTRY_CODE> <SHIP_PHONE></SHIP_PHONE> <SHIP_EMAIL></SHIP_EMAIL>

(3)

<TOTAL>3662.94</TOTAL> <SUBTOTAL>3645.95</SUBTOTAL> <MIN_AMOUNT>0.00</MIN_AMOUNT> <TOTAL_DISCOUNT>0</TOTAL_DISCOUNT> <DISCOUNT_CODE></DISCOUNT_CODE> <ORDER_STATUS>SUBMITTED</ORDER_STATUS> <TAX>0.00</TAX>

<TAX1_LABEL>SALES TAX (6.3%)</TAX1_LABEL> <TAX1_PERCENTAGE>6.3</TAX1_PERCENTAGE> <TAX2>0.00</TAX2> <TAX2_LABEL></TAX2_LABEL> <TAX2_PERCENTAGE></TAX2_PERCENTAGE> <SHIPPING TAXABLE=”TRUE”>16.99</SHIPPING> <PICKUP>2</PICKUP> <ORDER_URL>http://abc.com/RedCart/admin/index.php?rtr=1& orderID=1988</ORDER_URL> <CURRENCY_CODE>USD</CURRENCY_CODE> <PAYMENT_PROCESSOR>Pay in Studio</PAYMENT_PROCESSOR> <PAYMENT_STATUS>Pending</PAYMENT_STATUS> <PAYMENT_TXN_ID></PAYMENT_TXN_ID> <PAYMENT_RECEIPT_ID></PAYMENT_RECEIPT_ID> </CUSTOMER_INFO> <ORDER_LEVEL_NOTES>

Please rush this order if you can. Thanks! </ORDER_LEVEL_NOTES>

<ITEM_LEVEL_NOTES> <ITEM_NOTE>

<IMAGE_ID>IMG_9689</IMAGE_ID>

<GALLERY_TITLE>White Rocks Climbing</GALLERY_TITLE> <NOTE>I love this picture!</NOTE>

</ITEM_NOTE> <ITEM_NOTE>

<IMAGE_ID>03162007_1361</IMAGE_ID>

<GALLERY_TITLE>Jason Magic</GALLERY_TITLE>

<NOTE>Please remove any blemishes. Thanks!</NOTE> </ITEM_NOTE>

<ITEM_NOTE>

<PRODUCT_NAME>10''x10'' Flush Album</PRODUCT_NAME>

<NOTE>Can we look at more colors when we meet in the studio?</NOTE> </ITEM_NOTE>

<ITEM_NOTE>

<PRODUCT_NAME>Bob Jones' Balance Payment</PRODUCT_NAME> <NOTE>

This note was added by the customer from the My Cart screen inside RedCart. This note is for an external system item that was added to the cart after an HTML post to the RedCart index file.

</NOTE> </ITEM_NOTE> </ITEM_LEVEL_NOTES>

(4)

<IMAGE_ITEM FILENAME="IMG_9689" ITEM_RETAIL="171.96" SIZE="11X14" SIZE_DESC="11X14" PRINT_SIZE_ITEM_CODE="" UNIT="S" QTY="1" PAPER_TYPE="Lustre" PAPER_TYPE_ITEM_CODE="" TONE="B"

CUSTCROP="Y" ULX="7.66667" ULY="3.77778" LRX="95.79022" LRY="96.09769" TAXABLE=”TRUE”>

<FINISHING_SERVICES>

<FINISHING_SERVICE FS_ID="520" ITEM_CODE=""> Standout Board 3/4''

</FINISHING_SERVICE>

<FINISHING_SERVICE FS_ID="521" ITEM_CODE=""> Machine Texture

</FINISHING_SERVICE>

<FINISHING_SERVICE FS_ID="522" ITEM_CODE=""> Protective Coating Spray

</FINISHING_SERVICE> </FINISHING_SERVICES> </IMAGE_ITEM>

</GALLERY>

<IMAGE_ITEM FILENAME="03162007_1361" ITEM_RETAIL="12.99" SIZE="08X12" SIZE_DESC="8x12" PRINT_SIZE_ITEM_CODE=""

UNIT="S" QTY="3" PAPER_TYPE="Lustre" PAPER_TYPE_ITEM_CODE="" TONE="A" CUSTCROP="N" ULX="0.00000" ULY="0.00000" LRX="0.00000" LRY="0.00000" TAXABLE=”TRUE”>

<FINISHING_SERVICES></FINISHING_SERVICES> </IMAGE_ITEM>

</GALLERY>

<STORE_PRODUCTS>

<PRODUCT_NAME>10''x10'' Flush Album</PRODUCT_NAME> <PRODUCT_DESCRIPTION>

These custom designed albums are top of line and custom designed! We design each spread as a 10x20 image. There are so many options for these beautiful books! 10"x10" </PRODUCT_DESCRIPTION> <PRODUCT_ADD_ONS> <PRODUCT_ADD_ON ITEM_CODE=””> <ADD_ON_NAME>10''x10''</ADD_ON_NAME> <ADD_ON_VALUE ITEM_CODE=””>10x10</ADD_ON_VALUE> </PRODUCT_ADD_ON> <PRODUCT_ADD_ON ITEM_CODE=””> <ADD_ON_NAME>Leather Types/Colors</ADD_ON_NAME> <ADD_ON_VALUE ITEM_CODE=””>Napa Leather,

Raspberry</ADD_ON_VALUE> </PRODUCT_ADD_ON> </PRODUCT_ADD_ONS> </PRODUCT> </STORE_PRODUCTS> <EXTERNAL_SYSTEM_ITEMS>

(5)

ITEM_RETAIL="1860.02" QTY="1">

<PRODUCT_NAME>Bob Jones' Balance Payment</PRODUCT_NAME> <PRODUCT_DESCRIPTION>

This is the amount due on your account. <br />

<br />

This is the balance as of August 28, 2009. <br />

The minimum amount due by September 15th is $186.00 </b>

. <br /> <br />

Please edit this price to reflect the amount you would like to pay at this time.

<br /> <br /> Thank you! </PRODUCT_DESCRIPTION> <PASS_THRU_VAR1>L3KD9D90SLK333JD</PASS_THRU_VAR1> </EXT_SYS_ITEM> </EXTERNAL_SYSTEM_ITEMS> </RC_ORDER>

Table 1: XML Item Descriptions:

XML Item: Description:

<RC_ORDER> Root tag – contains all other tags for the orderRoot tag – contains the following attribute:

- VERSION [The version of the RedCart XML. The major digit will be incremented when changing or removing elements. The minor digit will be incremented when adding elements/attributes that shouldn't affect parsers of previous minor versions.]

<CUSTOMER_INFO> Parent tag – contains customer various tags about the customer and order

<ORDER_ID> Contains the numeric RedCart order id

<CUSTOM1> Custom pass through variable set by the photographer through the RedCart Admin. Useful to identify the customer.

(6)

<ORDER_DATE> The date and time the order was placed in the yyyy-mm-dd hh:mm:ss format

<FIRST_NAME> First name of the customer

<LAST_NAME> Last name of the customer

<ADDRESS_1> Customer’s address 1

<ADDRESS_2> Customer’s address 2

<CITY> Customer’s city

<STATE> Customer’s state

<PROVINCE> Customer’s province [only used outside US]

<COUNTY> Customer’s county [only used for customers in the UK]

<ZIP> Customer’s zip code or postcode

<COUNTRY_CODE> Customer’s two letter country code

<PHONE> The customer’s phone number

<EMAIL> The customer’s email address

<SHIPPING_SAME_AS_BILLIN

G> TRUE or FALSE – If true then the shipping fields will not contain any values.

<SHIP_FIRST_NAME> First name of the customer receiving the shipment

<SHIP_LAST_NAME> Last name of the customer receiving the shipment

(7)

<SHIP_ADDRESS_2> Shipping address 2

<SHIP_CITY> Shipping city

<SHIP_STATE> Shipping state

<SHIP_PROVINCE> Shipping province [only used outside US]

<SHIP_COUNTY> Shipping county [only used for customers in the UK]

<SHIP_ZIP> Shipping zip code or postcode

<SHP_COUNTRY_CODE> Shipping two letter country code

<SHIP_PHONE> Shipping phone number

<SHIP_EMAIL> Shipping email address

<TOTAL> The grand total of the order

<SUBTOTAL> The sub total of the order before any discounts or taxes

<MIN_AMOUNT> The amount that was added to the order to comply with the photographer’s minimum order requirement. The is only added when the photographer has a global minimum order requirement configured.

<TOTAL_DISCOUNT> The total discount or gift certificate amount

<DISCOUNT_CODE> The discount code used

<ORDER_STATUS> The status of the order. Initially and by default, all orders will be in the SUBMITTED status.

<TAX> The calculated sales tax

<TAX1_LABEL> The label for the sales tax (eg. SALES TAX, HST, or PST)

<TAX1_PERCENTAGE> The percentage value used in the sales tax calculation

<TAX2> Additional tax field (Canada uses this for GST where tax1 would be PST or HST)

(8)

<TAX2_PERCENTAGE> The percentage value used in the sales tax calculation

<SHIPPING> The shipping total. Contains the following attribute:

- TAXABLE [TRUE or FALSE]

<PICKUP> Indicates if the customer selected to pickup the order in the studio or if the order should be shipped. Possible values are:

- 1 [customer will pickup order]

- 2 [order should be shipped]

<ORDER_URL> The URL to the order details in the RedCart Admin panel

<CURRENCY_CODE> The currency code for the transaction (eg. USD)

<PAYMENT_STATUS> The status of the payment. Example Values:

- Zero Payment

- Completed

- Check Payment Status

- Manual

- Paying in Studio

- Mailing a check

- Manual Push

<PAYMENT_TXN_ID> The transaction id that corresponds to the payment processor.The payment processor’s receipt id (Paypal, MIGS)

<PAYMENT_RECEIPT_ID> The payment processor’s receipt id (Paypal, MIGS)

<ORDER_LEVEL_NOTES> Contains notes that the customer indicated on an higher order level.

<ITEM_LEVEL_NOTES> Parent tag - Contains <ITEM_NOTE> tags

<ITEM_NOTE> Parent tag – contains other tags relevant to the item note

<PRODUCT_NAME> The store product or external system item name that the note is in reference to. This tag will only be present if the note refers to a store item or external system item.

<GALLERY_TITLE> If the note is in reference to a gallery image, then the GALLERY_TITLE tag will be present. The gallery title refers to the gallery that the image belongs to.

<IMAGE_ID> If the note is in reference to a gallery image, then the IMAGE_ID tag will be present. This value is the filename of the image without the file extension.

(9)

<GALLERY> Represents a gallery. Contains a “Title” attribute and a list of <IMAGE_ITEM> tags for each image that was ordered from the gallery.

<IMAGE_ITEM> represents an “image item” or print. Contains the following attributes:

- FILENAME [the filename without the file extension]

- ITEM_RETAIL [the retail price]

- SIZE [the print size padded with zeros e.g, 04.0X06.0]

- SIZE_DESC [the print size description e.g, 4x6]

- UNIT [print size units S=standard, M=metric]

- QTY [the numeric quantity]

- PAPER_TYPE [paper type description]

- TONE [the color tone A=as shown, B=Black and White, S=Sepia]

- CUSTCROP [Indicates if the customer cropped the image. Y=yes, N=no]

- ULX [Indicates the Upper Left X coordinate percentage]

- ULY [Indicates the Upper Left Y coordinate percentage]

- LRX [Indicates the Lower Right X coordinate percentage]

- LRY [Indicates the Lower Right Y coordinate percentage]

- PRINT_SIZE_ITEM_CODE [the unique identifier that identifies the print size. This will only be populated if the item code was added by the photographer for this print size.]

- PAPER_TYPE_ITEM_CODE [the unique identifier that identifies the paper type. This will only be populated if the item code was added by the photographer for this paper type.]

• ULX, ULY, LRX, and LRY percentage numbers have eight significant figures and can range anywhere from 0.00000 to 100.00000. These are

percentages that can be used to crop the high resolution version of the image.

<FINISHING_SERVICES> Contains a list of finishing services for an “image item” or print.

<FINISHING_SERVICE> The text description of a finishing service that is related to an ordered print. Contains the following attributes:

- FS_ID [the RedCart finishing service id]

- ITEM_CODE [the unique identifier that identifies the finishing service. This will only be populated if the item code was added by the photographer for this finishing service.]

<STORE_PRODUCTS> Contains a list of products that are not prints. These products are not associated to any particular gallery and were ordered from the Store section of the cart.

(10)

<PRODUCT> Represents a single store product that was ordered. Contains the following attributes:

- PRODUCT_ID [the RedCart numeric product id]

- ITEM_RETAIL [the retail price]

- QTY [the quantity ordered]

- ITEM_CODE [the unique identifier that identifies the product. This will only be populated if the item code was added by the photographer for this product.] The <PRODUCT> tag is also a parent tag that encompasses other tags that describe the product:

- <PRODUCT_NAME>

- <PRODUCT_DESCRIPTION> - <PRODUCT_ADD_ONS> <PRODUCT_NAME> The name of the product

<PRODUCT_DESCRIPTION> The description of the product

<PRODUCT_ADD_ONS> Contains a list of Add-Ons that the customer selected for the product.

<PRODUCT_ADD_ON> Is a parent tag that contains other tags that describe the product add-on. Product add-ons are options that the photographer configured for the product that can be manipulated by the customer. These add-ons are options that the customer manipulated via drop-downs, checkboxes, text boxes, or text areas.

Contains the following attributes:

- ITEM_CODE [the unique identifier that identifies the add-on. This will only be populated if the item code was added by the photographer for this add-on.]

<ADD_ON_NAME> The name of the product add-on.

<ADD_ON_VALUE> The value of the product add-on. This could be text that the customer typed in, a “Y” or “N” if the add-on was represented by a checkbox, or a value that the photographer listed in a dropdown that the customer selected.

Contains the following attributes:

- ITEM_CODE [the unique identifier that identifies the value. This will only be populated if the item code was added by the photographer for this value. This is only used to identify different values within a “drop-down” type add-on. For example, If the add-on was a t-shirt that was available in small, medium, or large, the ITEM_CODE here would allow you to use a different item code for each size. ]

<EXTERNAL_SYSTEM_ITEMS> Parent tag that contains a list of EXT_SYS_ITEM elements that were added to the shopping cart via an external system form post. These items can be any item from

(11)

an external system (eg. balance payments, photo session fees...etc) and are not RedCart items that are defined by RedCart's “Product Pool.”

<EXT_SYS_ITEM> Is a parent tag that contains other tags that describe the external system item. Contains the following attributes:

− ITEM_ID [the unique item id assigned to this item]

− ITEM_COST [the photographer's cost]

− ITEM_RETAIL [the marked up retail price]

− QTY [the quantity ordered]

<PRODUCT_NAME> The product name that was passed into the cart from the external system form post.

<PRODUCT_DESCRIPTION> The product description that was passed into the cart from the external system form post.

<PASS_THRU_VAR1> The rc_passThruVar1 value that was passed into the cart from the external system for post.

(12)

2) Using RedCart to Process Payments

RedCart can be used as an extension of your software application to process payments. These can be balance payments or any other item that needs to be paid for by the customer. Your custom software application can use RedCart as the checkout mechanism by posting transaction data to the cart in a standard HTML form post. After the customer clicks on the submit button to submit the form to RedCart, all transaction data will be loaded into the cart and the customer will be able to click on an Add to Cart link to add the external system item to the shopping cart. The customer will also be able to browse the rest of the site and add other items to the cart such as photos from multiple galleries, store items...etc.

The form should post to the main index.php file located inside the photographer's RedCart directory: http://exampledomain.com/RedCart/index.php

Example PHP code for posting an external system item to RedCart:

<?php

// Stubbed in data for testing External System Items $rc_itemCost = "0";

$rc_itemRetail = "1860.02"; $rc_includeInSalesReports = "N"; $rc_qty = "1";

$rc_productName = "Bob Jones' Balance Payment";

$rc_productDescription = "This is the amount due on your account.<br/><br/>This is the balance as of August 28, 2009.<br/><br/><b>The minimum amount due by September 15th is " .

"$186.00</b>.<br/><br/>Please edit this price to reflect the amount you would like to pay at this time.<br/><br/>Thank you!";

$rc_passThruVar1 = "L3KD9D90SLK333JD"; $rc_priceEditable = "Y"; $rc_shippingItem = "N"; $rc_shippingWeight = "0"; $rc_shippingAdditionalCost = "0"; $rc_taxable = "N"; ?> <html> <head>

<title>External Item Post to RedCart Example</title> </head>

<body>

<?php echo "Price: $".$rc_itemRetail;?><br /><br />

(13)

$rc_includeInSalesReports;?>">

<?php echo "Quantity: ".$rc_qty;?><br /><br />

</body> </html>

Table 2: POST Variable Descriptions:

The following table lists the post variable name and a description of the variable.

Variable Name: Description:

* rc_itemCost The Item Cost is the photographer's cost to purchase the item. Item Cost will be taken into consideration for profit calculations in the financial reports. This value must be in the form of a number with no more than two places after the decimal.

* rc_itemRetail Item Retail is the marked up retail value. If rc_priceEditable is set to “N,” this value will be fixed to the client. If rc_priceEditable is set to “Y,” the Item Retail will be editable by the client. This is useful for balance payments where a client may only pay a portion of the balance due at a time. This value must also be in the form of a number with no more than two places after the decimal.

rc_passThruVar1 This is a pass through variable internal to the system which can be used for your own purposes to identify an item or for any other reason. If you are utilizing the feature that sends XML data to your application then you will receive this value back in the order data through the <PASS_THRU_VAR1> XML tag. This field is of type

(14)

* rc_productName This is the name of the item that the customer will add to the shopping cart. This field is of type varchar with a length of 100.

rc_productDescription This is the text description of the product which can include HTML formatting.

* rc_priceEditable The value of this field determines whether or not the Retail Price is editable by the customer. Acceptable values are either “Y” if the client is to be allowed to edit the price, and “N” if the price is to be fixed.

*

rc_includeInSalesReports This field determines if the item should be included in RedCart's financial reports. If this flag is set to “Y” then the item will be included in the financial reports. If the flag is set to “N” then the item will not be included in the financial reports. Generally speaking, this should be set to “N” for balance payment type items and should be set to “Y” for all other items that need to be included in financial reports. The financial reports will report on things like Gross Sales, Gross Profit...etc.

* rc_qty This is the quantity of the Linked Item to be added to the cart. The value of Quantity is always 1. This field is always editable by the client.

* rc_shippingItem This field indicates whether RedCart should include this item in shipping

calculations at the end of the checkout process. The value of this field should be “Y” if the item should be included in shipping calculations and “N” if the item should not be included in shipping calculations.

rc_shippingWeight This field will only be taken into account if rc_shippingItem is set to “Y” and if the photographer has their cart configured to use RedCart's Ballpark Shipping calculation. Item weights are only taken into account with the Ballpark Shipping calculation and are not used with any other RedCart shipping calculation. Item weight units need to correspond to the units that are selected inside of the RedCart Admin application -> Configuration -> Admin Options -> Weights & Measures. Weights can be in ounces or grams and can have up to two decimal places.

rc_shippingAdditionalCost This field will only be taken into account if rc_shippingItem is set to “Y.” This price should be set to 0.00 in most cases but can be used to add a specific dollar amount on top of the calculated shipping cost for this specific item. This is useful with heavy or bulky items that need additional shipping charges applied. If this value is > 0, then it will be added to the shipping calculation, regardless of the calculation being used (eg. Ballpark Calculation, Flate Rate, Percent of Subtotal).

* rc_taxable Set this field to “Y” if the item is taxable and if it should be included in sales tax calculations. Set this field to “N” if the item should not be included in sales tax calculations.

(15)

XML Change Log

<RC_ORDER> Version 2.1:

• Added PRINT_SIZE_ITEM_CODE attribute to <IMAGE_ITEM>. • Added PAPER_TYPE_ITEM_CODE attribute to <IMAGE_ITEM>. • Added ITEM_CODE attribute to <FINISHING_SERVICE>. • Added ITEM_CODE attribute to <PRODUCT>.

• Added ITEM_CODE attribute to <PRODUCT_ADD_ON>. • Added ITEM_CODE attribute to <ADD_ON_VALUE>. <RC_ORDER> Version 2.0:

• Added VERSION attribute to <RC_ORDER>. • Added TAXABLE attribute to <PRODUCT>. • Added TAXABLE attribute to <IMAGE_ITEM>. • Added <TAX1_LABEL> to <CUSTOMER_INFO>. • Added <TAX1_PERCENTAGE> to <CUSTOMER_INFO>. • Added <TAX2_LABEL> to <CUSTOMER_INFO>. • Added <TAX2_PERCENTAGE> to <CUSTOMER_INFO>. • Added <ORDER_URL> to <CUSTOMER_INFO>.

• Added <CURRENCY_CODE> to <CUSTOMER_INFO>. • Added <PAYMENT_PROCESSOR> to <CUSTOMER_INFO>. • Added <PAYMENT_TXN_ID> to <CUSTOMER_INFO>.

• Added <SHIPPING_SAME_AS_BILLING> to <CUSTOMER_INFO>. • Added <SHIP_FIRST_NAME> to <CUSTOMER_INFO>.

• Added <SHIP_LAST_NAME> to <CUSTOMER_INFO>. • Added <SHIP_ADDRESS_1> to <CUSTOMER_INFO>. • Added <SHIP_ADDRESS_2> to <CUSTOMER_INFO>. • Added <SHIP_CITY> to <CUSTOMER_INFO>. • Added <SHIP_STATE> to <CUSTOMER_INFO>. • Added <SHIP_PROVINCE> to <CUSTOMER_INFO>. • Added <SHIP_COUNTY> to <CUSTOMER_INFO>. • Added <SHIP_ZIP> to <CUSTOMER_INFO>.

• Added <SHIP_COUNTRY_CODE> to <CUSTOMER_INFO>. • Added <SHIP_PHONE> to <CUSTOMER_INFO>.

• Added <SHIP_EMAIL> to <CUSTOMER_INFO>.

• Removed <TXN_ID> from <CUSTOMER_INFO>. <TXN_ID> was replaced with <PAYMENT_TXN_ID> • Removed <RECEIPT_ID> from <CUSTOMER_INFO>. <RECEIPT_ID> was replaced with

<PAYMENT_RECEIPT_ID>

(16)

• Special characters from user input are now being encoded with the HTML entity equivalent to ensure valid and well formed XML.

<RC_ORDER> Version 1.0: Document created.