For information about how to create or edit a part, as well as the tabs on the Edit Part screen, see Create and Edit Parts.
| 1. | From the Design tab, under General, enter how long to maintain shopping carts for users who add transactions but do not log in to your website. |
Warning: If you enter “0” in the Days to keep anonymous carts field, the program does not maintain cookies to identify users who are not logged in. If one of these anonymous user adds items to a shopping cart and does not check out, the user cannot return to the cart later. Depending on the browser, the cart is cleared either when the browsing session times out or when the user closes the browser.
For registered users on your website, the Payment 2.0 part maintains shopping carts until they process the items in their carts. However, the program can remove individual items such as event registrations when the parts place time limits on how long the items can remain in shopping carts.
| 2. | Under Confirmation screen, design the payment summary that appears after user check out in the shopping cart. |
In the HTML editor, enter content for the payment summary and format the appearance and layout. To include personalized information, use merge fields. To remove the changes you make to the default confirmation screen, click Load Confirmation Template.
For more information, see HTML Editor.
| 3. | Under Required Fields, select the checkbox for each field to make required on the payment form. To ensure you download complete constituent information, we recommend that you make all these fields required. |
| 4. | Under Payment methods, select the payment methods to offer to website users. You can allow users to pay with credit card and direct debit, or to make pledges to pay later. |
Warning: If you select Direct debit only, the Payment 2.0 part cannot process event registrations because the Event Registration Form part does not accept direct debit payments. You must either select an additional payment method or direct event registration transactions to a different Payment 2.0 part.
Note: To help you comply with the Payment Card Industry Data Security Standard (PCI DSS), the Payment 2.0 part directs users who pay with credit cards to the secure payment page to process payments. It does not direct users to this page when they make pledges or pay with direct debit. For information about the secure payment page, see Secure Payment Page.
| 5. | In the Merchant account field, select the merchant account to use to process credit card transactions. For example, you can use your organization’s IATS account. The system administrator sets up merchant accounts in Administration. For more information, see Merchant Accounts. |
Warning: If you create multiple Payment 2.0 parts for your website, you should use the same merchant account for each part. If you use multiple merchant accounts and users purchase items through more than one Payment 2.0 part, the program processes all items with the merchant account for the last item. If you set up merchant accounts for different currencies, this means users may pay for some items with the wrong currency.
| 6. | Click Next. The Acknowledgement email section appears. |
| 7. | Enter a name for the acknowledgement, a subject, and an address and name to include in the From field of the email message. |
| 8. | To receive responses from recipients at a different email address than the one you use to send the message, enter the return address in the Reply Address field. |
| 9. | Under Notifications are to be sent to the following addresses, select Failures to receive failure messages for email messages that are not delivered. In the field beside the checkbox, enter an email address to receive failure messages. |
Note: Failures are email addresses that do not receive the acknowledgement email. Failures can also be called non-delivery receipts, bouncebacks, UnDeliverables, or Delivery Status Notifications (DSN).
| 10. | In the HTML editor, enter content for the acknowledgement email message and format the appearance and layout. To include personalized information, use merge fields. |
For more information, see HTML Editor.
Note: You design acknowledgement messages for each part that routes transactions to a shopping cart. To include all these acknowledgements messages in the email message you design for the Payment 2.0 part, use the Acknowledgement Block merge field. For example, you can add the merge field to a Payment 2.0 part acknowledgement email message and then route transactions to the part from Donation Form and Membership Form parts. After website users check out, they receive a single Payment 2.0 acknowledgement email that includes acknowledgment messages from the Donation Form, and Membership Form parts. You can also use this merge field on the Payment 2.0 part’s confirmation screen.
| 11. | Click Save. You return to Parts. |