Payments2Us ManualsPayments2Us Installation Manual SecurityHow to set up external site security for payments (Classic version)

How to set up external site security for payments (Classic version)

How you set up security will depend on the needs of your organisation.

1.1. Select the Cog symbol on the RHS of your Salesforce home screen. (In Classic, click 'Setup' on the top RHS.)

1.2. A drop down menu will appear, select 'Setup'.

1.3. A new window or tab will open. In the quick search bar on left hand side type 'sites'.

1.4. Select 'Sites'

1.5. Select the Site from the list

Select the Site from the list

2. Select the 'Public Access Settings' button

3. Check the diagram below. If it looks the same, follow these steps:

These instructions are for older versions of Salesforce.

If the diagram does not match below, follow these instructions (enhanced version of Salesforce) to revert Salesforce back to the older version.

4. Set 'Record Types'.

4.1. Scroll down to 'Record Type Settings' heading

Scroll down to 'Record Type Settings' heading

4.2. Select 'Edit' on the Payment Txn's label

Select 'Edit' on the Payment Txn's label

4.3. Select all 'Available Record Types' to add them to 'Selected Record Types'

4.4. Set the 'Default Record Type' to Payment and Save.

Set the 'Default Record Type' to Payment and Save.

5. Allocate Permissions.

5.1. Scroll down to 'Standard Object Permissions' on the Payment Profile screen.

5.2. Select 'Edit'.

5.3. Match the permissions shown below.

You may need to scroll across to see all the diagram.

5.4. When and how are the permissions used?

Please note, these guidelines are new and have been put in place due to a recent Salesforce communication.  Our best efforts have been used to document the various requirements, but this may not cover all scenarios.
If removing any recommended Create or Read accesses, please test thoroughly and restore if any issues.

Account

  • Read required for Account Level, Subscription Group Level or Contact Level memberships.  In particular renewal URLs
  • Read required for Recurring Card Updates by Card holder
  • Read required when using URL Parameters "aid=", "cid=" or "MembershipId="
  • Read required when using URL Tokens and Account, or Contact specified
  • Create required if Batch Processor not started

Contact

  • Read required for Account Level, Subscription Group Level or Contact Level memberships.  In particular renewal URLs
  • Read required for Recurring Card Updates by Card holder
  • Read required when using URL Parameters  "cid=" or "MembershipId="
  • Read required when using URL Tokens and Contact specified
  • Create required if Batch Processor not started

Campaigns

  • Read required when Payment Form linked to Campaign
  • Read required when using URL Parameters "camId="
  • Read required when using URL Tokens and Campaign specified
  • Read required when using Events Module
  • Read required when using Peer-to-Peer fundraising
  • Create required if Batch Processor not started

Documents

  • Read required when using Checkout Form
  • Create required when using Peer-to-Peer Fundraising Registration

Opportunities

  • Read required when using URL Parameters "OppId="
  • Read required when using URL Tokens and Opportunity specified
  • Create required if Batch Processor not started

Pricebooks and Products

  • Read required when Product or Donation Product select on the "Payment Form"
  • Read required when using URL Parameters "ShoppingCartDetails="

Account Subscriptions and Account Subscription Payments

  • Read required for Account Level or Subscription Group Level.  In particular renewal URLs
  • Create required if Batch Processor not started

Account Subscriptions and Account Subscription Payments

  • Read required for Subscription Group Level or Contact Level memberships.  In particular renewal URLs
  • Create required if Batch Processor not started

Fundraiser IDs

  • Read required when using URL Parameters "MembershipId="
  • Read required when "Enable Membership Search" set on the "Payment Form"
  • Create required if Batch Processor not started

Team Members

  • Read required when using side bar widgets that show Peer-to-Peer Team Members
  • Create Required when using Peer-to-Peer Registration
  • Create required if Batch Processor not started

Tickets and Ticket Types

  • Create and Read required when using Events Module
  • Create required if Batch Processor not started

5.5. Select 'Save'.

6. Assign users.

6.1. Select 'View Users' on the Payments Profile screen.

6.2. Select user to be assigned Payments2Us access.

Select user to be assigned AAkonsult Payments access.

6.3. Check 'Name', 'Email' and 'Time Zone' - Important step for receipts

You may wish to edit the name of the Sites User Names and email as this is the one the payment receipts will come from by default.  

Also, check the timezone to make sure it is your local time zone so that payment creation dates reflect the right date.

6.4. Select 'Edit Assignments'

Select 'Edit Assignments'

6.5. Add 'Payments2Us Sites' to the Enabled Permission Sets.

Add 'AAkonsult Payment Sites' to the Enabled Permission Sets.

6.6. Select 'Save'

7. Revert Salesforce to the enhanced version (if originally unticked for security set up)

Only follow this step if you originally unticked the Enhanced Version of Salesforce for a simpler set up.