| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| v:0.7.0:checkout [2011/05/17 22:33] – [Subscription Cancellation] foxybrett | v:0.7.0:checkout [2017/04/26 07:02] (current) – external edit 127.0.0.1 |
|---|
| |
| ==== What to name your fields ==== | ==== What to name your fields ==== |
| |
| You can name your fields anything you want, but **we recommend using the underscore (''_'') for spaces**, and capitalizing your input names as you'd like them displayed. For all receipts, we will convert underscores to spaces for you. | You can name your fields anything you want, but **we recommend using the underscore (''_'') for spaces**, and capitalizing your input names as you'd like them displayed. For all receipts, we will convert underscores to spaces for you. |
| |
| |
| ==== What about Receipts and the Datafeeds? ==== | ==== What about Receipts and the Datafeeds? ==== |
| |
| The custom fields will be inserted at the bottom of your your receipt (after checkout), as well as in any emails that include the ''^^receipt^^'' placeholder. | The custom fields will be inserted at the bottom of your your receipt (after checkout), as well as in any emails that include the ''^^receipt^^'' placeholder. |
| |
| Custom checkout fields are included in all XML datafeeds from version 0.3. | Custom checkout fields are included in all XML datafeeds from version 0.3. |
| ==== What if I'm using multiship and I need a custom field per shipto? ==== | |
| |
| | ==== What if I'm using multiship and I need a custom field per shipto? ==== |
| No problem! Just wrap your custom fields in ''^^multiship_custom_begin^^'' and ''^^multiship_custom_end^^'' and you're good to go. | No problem! Just wrap your custom fields in ''^^multiship_custom_begin^^'' and ''^^multiship_custom_end^^'' and you're good to go. |
| |
| |
| ==== A Note about Checkboxes ==== | ==== A Note about Checkboxes ==== |
| |
| **Checkboxes do not post** if they are unchecked. This is standard HTML form behavior, but it's worth noting, especially if you're using checkboxes for your XML datafeeds. | **Checkboxes do not post** if they are unchecked. This is standard HTML form behavior, but it's worth noting, especially if you're using checkboxes for your XML datafeeds. |
| |
| |
| <wrap important>You should not be collecting passwords using custom fields,</wrap> as they will be stored in cleartext and not hashed in our system. Though we work hard to keep our systems secure, it's just not a good idea to store passwords without a strong hashing algorithm. | <wrap important>You should not be collecting passwords using custom fields,</wrap> as they will be stored in cleartext and not hashed in our system. Though we work hard to keep our systems secure, it's just not a good idea to store passwords without a strong hashing algorithm. |
| | |
| | |
| | ===== Pre-Populating the Checkout with Customer Information ===== |
| | Though we generally recommend [[.:advanced:sso|Single Sign-On]] and synching [[.:customers|customers]] via [[.:advanced:api|the API]], there are certain situations where you may want to pre-populate the customer's billing or shipping fields without using SSO or the API. |
| | |
| | Pre-populating is done by passing in [[.:cheat_sheet#customer_information_pre-population|specific customer fields]] to [[.:cart|the cart]]. Once the customer fields have been passed into the cart, they will remain there just like [[.:session_variables|session variables]], and when the checkout is loaded the values will be inserted into the appropriate fields on the checkout. Note that this does //not// impact the user's ability to change the data, nor does it impact the customer's ability to checkout as a guest or to create an account. |
| |
| |
| |
| ==== "Update Info" Requests ==== | ==== "Update Info" Requests ==== |
| If the ''cart'' parameter is set to ''updateinfo'', the cart will immediately redirect to the checkout in "updateinfo" mode. Simply put, this will process an empty transaction, thus allowing the customer to update their password, address(es), or payment info. This updated information will be sent in a [[.:advanced_transaction_xml_datafeed:transaction datafeed]], but the [[:gateways:start|payment gateway]] will not be contacted during this checkout. | If the ''cart'' parameter is set to ''updateinfo'', the cart will immediately redirect to the checkout in "updateinfo" mode. Simply put, this will process an empty transaction, thus allowing the customer to update their password, address(es), or payment info. This updated information will be sent in a [[.:advanced:transaction_xml_datafeed|transaction datafeed]], but the [[:gateways:start|payment gateway]] will not be contacted during this checkout. |
| |
| The ''updateinfo'' process can be useful in certain situations, but especially if you're handling subscriptions you'll likely want to use the ''sub_token'' rather than the ''updateinfo'' approach. | The ''updateinfo'' process can be useful in certain situations, but especially if you're handling subscriptions you'll likely want to use the ''sub_token'' rather than the ''updateinfo'' approach. |
