David Glick's Plone Conference 2009 talk showing tools for accepting payments via PloneGetPaid and recording the transactions in Salesforce.com

1. Integrating Plone
with E-Commerce
and Relationship Management
A Case Study in Integrating
PloneGetPaid and Salesforce.com
David Glick

2. Groundwire uses the power of technology
to connect people, organizations, and communities
working to build a sustainable society.

3. Idaho Conservation League
http://www.fickr.com/photos/sebastian_bergmann/2946960668/

4. Idaho Conservation League

5. Theory
of Change

6. Goal: Tools to help engage
• E-mail newsletter
• Online donations
• Membership signup
• Paid event registration

7. Tools
http://www.fickr.com/photos/lachlanhardy/227715761/

10. Why salesforce.com?
• Not open source, but open-ended,
customizable platform
• Active development community
• Salesforce Foundation donates 10 user
licenses to charitable organizations (worth
$15k/year)
• Managed service == reduced maintenance
complexity

11. But most of our goals require
integrating multiple tools...

12. General strategies
• separation of concerns – small pieces
loosely joined
• customization via configuration, not
programming
• reusability

13. E-mail newsletter signup

14. Salesforce-PloneFormGen
Adapter
Fie lds Ac tio n Ada pte rs
Mailer
Submit
Saved data
Salesforce.com

15. Salesforce-PloneFormGen
Adapter

16. Salesforce-PloneFormGen
Adapter

17. Passing preset values via
hidden fields

18. Lead Conversion

19. E-commerce options
http://www.fickr.com/photos/danielbroche/2258988806/sizes/m/

20. Standalone 3rd-party tool
(GiftTool, Network for Good, etc.)

21. Direct integration with
Salesforce.com
(Payment Connect)

22. Direct integration with
Salesforce.com
(Payment Connect)

23. Handcode it in Python

24. GetPaid for Plone

25. Considerations
• Costs both upfront and ongoing
(typically 2-5% of transaction depending on
the payment gateway)
• Method of funds transfer
• Access to and privacy of donation data
• Integration with your website

26. Payment Processor Choice?
• Authorize.net • PayPal
• Paymentech • Google Checkout
• Ogone • Payflo Pro
• DPS PXPay • others?
• ClickandBuy

27. Sync vs. Async
• Synchronous processors take in all info via
Plone and then process via a separate
backend request to the processor. (e.g.
authorize.net)
• Asynchronous processors redirect the user
to the processor's site to collect billing info,
then forward back to the store site. (e.g.
PayPal Website Payments Standard)

28. PCI compliance
• The credit card industry has some strict
standards for sites that deal with credit
card information.
https://www.pcisecuritystandards.org/
• Sites that store, process, or transmit credit
card info should complete a questionnaire
and be prepared for a server scan.
• Ask a consultant for advice.

29. Hosting considerations
• Most VPS providers are not going to certify
themselves as PCI compliant.
• If you're accepting credit card info directly
rather than sending the user to an offsite
processor, you need an SSL certificate …
and a unique IP address per domain.

30. Installing GetPaid
[buildout]
parts =
…
getpaid
…
[getpaid]
recipe = getpaid.recipe.release==1.9
addpackages =
getpaid.authorizedotnet
getpaid.formgen
getpaid.SalesforcePloneFormGenAdapter
getpaid.SalesforceOrderRecorder

31. Installing GetPaid

32. Configuring GetPaid

33. Donatable Types

34. Payment Options

35. Payment Processor Settings

36. One-page
member signup

37. One-page member signup,
recorded in Salesforce
Form
Payment Processor
1. Order placed
(getpaid.formgen)
2. Payment authorization
(getpaid.authorizedotnet, etc.)
GetPaid Checkout
3. Finance charge event → Info recorded
(getpaid.SalesforcePloneFormGenAdapter) Salesforce.com

38. GetPaid adapter
• getpaid.formgen
» Adds billing fields to form
» Adds item(s) to cart
» Initiates checkout

39. getpaid.formgen Configuration
Marking an item as a
“variable amount donation”

40. getpaid.formgen Configuration
Marking an item as a
“variable amount donation”

41. getpaid.formgen Configuration
Adding the action adapter

42. getpaid.formgen Configuration
Selecting the payable object

43. getpaid.formgen
Automatically adds
billing fields

44. collective.pfg.creditcardfields
• Provides a date widget with just year and
month.
• getpaid.formgen creates a standard date
field, but you can replace it with this.

45. GetPaid-PloneFormGen-
Salesforce adapter
• (getpaid.SalesforcePloneFormGenAdapter)
» Configures field mapping
» Stores form values in session before checkout
» Creates objects in Salesforce when order is financed

46. getpaid.SalesforcePloneFormGenAdapter
Data sources
Plo ne Fo rm Ge n Fo rm : Ge tPa id:
Custom felds Transaction ID, Billing Address, etc.
Ge tPa id-Sa le s fo rc e Ada pte r:
Confgures feld mapping for both sources
Salesforce.com

47. getpaid.SalesforcePloneFormGenAdapter
Adding the adapter

48. getpaid.SalesforcePloneFormGenAdapter
Configuring the object type

49. getpaid.SalesforcePloneFormGenAdapter
Configuring the field mapping

50. Remember:
• The GetPaid-PloneFormGen-Salesforce
adapter must go before GetPaid adapter.
(It needs to store things in the session
before the GetPaid adapter starts
checkout.)

51. Making events payable

52. Payable events

53. Events in shopping cart

54. Events checkout

55. getpaid.SalesforceOrderRecorder
• Map fields to Salesforce for standard
GetPaid checkout (no PloneFormGen
involved)

56. Lessons/Observations

57. Don't underestimate the effort
needed to learn new
processes and tools

58. Don't assume an existing
product does everything like
you want

59. Integrating systems
• Usually you don't need much code, but the
challenge is figuring out what it is and
where to put it.

60. Testing integrations with
third-party tools is hard

61. Testing integrations with
third-party tools is hard

62. Making integrations
configurable enough to be
reusable increases complexity
significantly

63. Warning
• May not be suitable for use under high
load.
(API calls to Salesforce.com are not
transaction-aware, so ConflictErrors could
lead to inconsistencies.)

64. The future
http://www.fickr.com/photos/locationscout/3595249806/

65. More automated form creation
for the simple donation use
case

66. Integration with RSVP for
Salesforce

67. Profile management

68. Get involved
• Plone-Salesforce
http://groups.google.com/group/plonesf
• GetPaid
http://code.google.com/p/getpaid/

69. Thanks to...
• Groundwire
• Andrew Burkhalter
• Jesse Snyder
• Brian Gershon
• Rob Larubbio
• Meyer Memorial Trust
• Everyone who has worked on GetPaid
• Many others :)