In This Release

Product Delivery Message

We have added the product delivery message feature from service products to all products. You can add a message when creating or editing any product. This feature is great for giving your customers a link to a support forum, a phone number, or simply a message telling them “thank you.”

In addition we have given an option to expire the delivery message when the download limit has been reached.

Require Retyping Email on Checkout

You can now require that your customers enter their email twice for free and paid checkouts. This can cut down on deliveries to invalid email addresses. If you would like to enable this feature, click on Preferences in the left menu and enable the Require Email Retype on Checkout

Auto-return for Add to Cart Links

If you would like to bring your customers back to your site immediately after adding the product to the cart, check the Auto-return to continue shopping URL option in the button creator. For your existing links simply add in the &return=1 parameter to your links. A continue shopping URL is required to enable auto-return.

Other Improvements and Bug Fixes

• Fixed custom product price names not showing on the product chooser
• Fixed 2co delivery page redirect for Internet Explorer users
• Added guards to prevent double submitting the customerinfo form for free checkouts
• Allow multiple email integrations to be created
• Fixed quantity parameter in BBCode instant checkout generator
• Added pagination to coupon list
• Fixed custom product price names not being used on v2 carts in some cases
• Fixed import customer feature not importing the last line of the CSV file
• Added customer filter for whether or not they have opted out of newsletters

In this update we’ve released two major feature improvements:

Custom Field Improvements: External / Hidden Custom Fields and IPN / API passthrough

Vendors can now create hidden “external” custom fields in DPD and pass data to these fields through their add-to-cart URLs. The data will be stored with the transaction, and vendors can now get custom field data from both the DPD IPN System and the new DPD Cart API.

Adding custom field data to your add-to-cart URLs is as easy as appending a “custom_1=foo” to the end of the URL. This feature will solve a lot of advanced integration requests for vendors such as passing referral or ad source codes to DPD to include with the purchase, or passing landing page versions or sales page A/B testing info to DPD for later analysis.

An example of how to include this data in a DPD add-to-cart URL is available in our Cart Custom Fields knowledgebase entry.

For more information in our KB:

• Cart Custom Fields
• DPD IPN System
• DPD Cart API Information

Content Subscription Dunning Settings

DPD now gives vendors control over their dunning settings for handling failed subscription payments made through Stripe. Vendors can set the number of retry attempts and the number of days between retries when a credit card payment fails using the new Dunning option in the left menu for subscription stores. Once the failed payment attempts have been exhausted subscriber content access will be terminated.

Vendors can disable dunning by setting rebill attempts to 0 in their dunning settings. This will terminate access to subscription content without warning on the first failed payment and is probably a pretty bad idea, but the option is there!

DPD will automatically send a failed payment email when one occurs. This email contains a link for the subscriber to log in to the subscription area and update their credit card info. Vendors can edit this email along with all other subscription emails (or product store emails for that matter) by going to Email Templates in the left menu after logging in to DPD.

Automatic Virus Notifications

DPD regularly scans our servers and all uploaded products for viruses, trojans, and other malware. We do this for a number of reasons- PCI compliance, to protect our service’s reputation for delivering safe products, and to not be a vector for malicious users to deliver malware.

Previously, we’ve had to manually email vendors when we find a virus and tell them to clean their files up. As DPD has grown, this became a major pain to follow up with! Now, we’ll automatically send a notification when we detect an infected upload and automatically take action if the vendor does not upload a clean file.

If you get an infected file notification, take action! We can not allow distribution of infected files through our service under any circumstance.

This is nothing personal against the vendor! We do this to protect your customers, your business reputation, and DPD’s reputation as a safe and secure file delivery system.

Today we’ve released our first public API for getting data out of DPD. The DPD cart API is intended for programmers who want to integrate 3rd party systems with DPD.

The DPD API is a read-only window into your DPD account. It gives you access to storefronts, products, purchases, and subscriber data. The API does not support modifying any data at this time.

Along with the API we’ve released reference documentation and a sample PHP Library to get you started.

DPD API Information:

• API Reference
• PHP Library
• More Information

Let us know if you have any feedback for the API. It’s a new feature and a work in progress so we welcome your input!

Other Fixes and Improvements in this update:

• Added required option for custom field checkboxes
• Updated support tab to include knowledgebase search
• Fixed a problem with creating bundle purchases using the customer import feature
• Fixed a problem that caused duplicating products to not duplicate the product image

Share this:

• Facebook
• Twitter
• LinkedIn
• Reddit
• Pocket
• Pinterest

In today’s update we’ve released two new features and a tweak to our new Custom Fields feature related to free checkouts.

Edit Purchase Customer Info

You can now edit a purchase and change the name and email associated with that purchase. If the customer email that you’re changing the purchase to exists in your account already, we’ll automatically merge them. If they don’t, we’ll create a new customer record.

Additionally, for tangible orders you can edit the shipping address for the order. Of course, this only applies to orders with tangible goods and not downloadable orders.

This, along with the existing ability to change a customer record, should allow you to resolve any issues where a customer changes their email, typo’s their info, etc.

Set Default Payment Method

Most vendors allow for checkout through multiple methods, for example Stripe and PayPal. If you prefer to mark one processor as the default option to encourage buyers to use that method you can now set the default.

To set a default method, edit the payment method (found under Payment Methods in the left menu) and check the default box.

We add a star indicator to show which processor is default:

In the cart, that processor will be selected by default during checkout:

So, you can now encourage people to use in-cart credit card checkout, the processor where you pay the lowest fees, etc.

Custom Field Tweaks

Previously custom fields that were marked as required were not properly requiring an input for free checkouts. This is fixed, so all checkouts, free and paid, will require input on custom fields that are marked as required when creating them.

Other small tweaks:

• Removed unused styles to speed page loads
• Tweaks to new form styles for cross-browser compatibility
• Small change to PayPal Express method for reliability
• Fixed 404 error when editing default price points instead of editing the product record