Payments2Us Payment Notes

Previously known as Aakonsult Payments

Features

• The public forms do not allow members to update their details in Salesforce. Thankfully, the Batch Processor can be set up to take the values that are stored from the payment form and update Accounts and Contacts.
• Set up all your payment forms using the Demo Merchant Facility, then when you are ready to go live, just switch out the payment facility.
• A special frequency of “One-off – Authorise” can be used to charge a small amount up front, then charge the full amount using the Recurring Payment – Tokenise Charge facility later (as credit card details are not stored in your SF). Eg paying a deposit for an event, and charging the full fee on the day.
• You can also do a one-off charge to their card via Credit Card Token Payment. Make sure you have authorisation to do so.
• You can't do recurring payments with Paypal.
• You can do recurring payments with a variable amount that you have to manually set before each transaction occurs. I can't think of a business reason for this yet.
• You can do recurring payments as a payment schedule that emails the payee with a link to the payment form to ask them to pay now.
• For recurring payments. card expiry dates are stored in encrypted fields. The recurring payments processor will update a flag when the card is 30 days out from expiring and this will trigger an internal workflow to ask staff to contact the payee. You can update the card details or expiry date on the recurring payment.
• You can add manual payments or set up a recurring payment from the contact record.

Merchant Facility

Multiple MFs

Multiple MFs are needed for

• Different payments going into different bank accounts.
• Different logos on different payment forms
• Maybe different information required on the form depending on the State (eg Postal Address).

Form Width

• The form width parameter is not the width of the form elements you see on the screen, it is the width of the div that the form is rendered in - wrap. It has 20px padding all around.
• For some reason the form (content div) is 40px less than the stated form width, and is left aligned, so all 40px goes to the right hand side.
• That would be OK, but the Logo box is strangely aligned (left aligned 100% width but it's width is computed as 14px less than the wrap div - not sure why), so it will never align with the content div, and the content is centered in the table. It will never look right.

Logo

• The logo can not be the same width as the form.
• The logo is shrunk to 500px wide even if you put a larger one in there.
• The table the logo in has a 10px padding to left and right, so it will never line up with the left of the content div.

Overall, it looks a bit bad. You could of course fix this yourself with custom forms, and if you, like me, are measuring pixels, you probably want to have the custom form option anyway.

Payment Types

Naming

If you name your Payment Type any name with the word Event in it, the form layout will change to an Events form layout. This is not good if you are not using the AAK Events module. So just name your Payment Type Evnt or similar and it will show the right form.

Campaigns

When showing campaigns on the appeals section they must have an end date, be active, and have publish on web, and they are listed in alpha order.

Membership

When “Enable Membership Search” is enabled, the membership field will appear on the payment form. If the user specifies their correct Last Name and Membership No. combination then the rest of the known details on file will be automatically completed. Fabulous!

Forms

Field Sets

• Field sets are your friend, and allow you to change what is displayed on the payment form.
• NOTE: Changes to the main field sets changes all payment forms, so take care when changing them.
• It is possible to have one Payment Type using Custom Fields and another Payment Type using Custom 2 Fields field sets.
• Also use Workflows on create of the Payment Trx record to fill in any other custom fields that you want to display on the payment form.

• Some fields can't be shown in some field sets. Eg, I wanted the Company Name (Donation for) to appear in the My Contact Details section. I added a custom field, added that to the checkoutExternalName and checkoutInternalName field sets, then updated the Donation For field by a Workflow. 
• It seems lookup fields can't be shown on the public form, so make a text field, update that field by a workflow, and add the text field to the field set. 

Logos

• Logos must be inserted into the rich text field, not linked from a URL
• An Events checkout page does not have the logo at the top. 

Buttons

• I was creating a form that was payment for an Event, but it was not using the Events functionality (custom events website). I was still seeing the back button on the checkout form, which is weird (the Back button is only for Events). It turns out it was because the Transaction Source field was set to Event. As soon as I set it back to Checkout, the back button was gone. 

Amounts

• My Total Charged Amount was not showing correctly. I had to make sure all the amount fields were filled in and not null. The culprit for me was that the Freight field was null. 

Opportunities

• Check Create Opportunity on the MF. 
• Set the Opportunity Record Type in the PT. 
• Choose Enable Soft Credits in the PT (if you are using Nonprofit Success Pack - NPSP). 
• Create fields on the Opportunity to match any custom fields you had on the Payment Transaction. These will be automatically updated on the Opportunity when it is created. 
• Don't like the Opportunity Name as default? Then create a workflow to update the name to what you want. The prefix for the Opportunity Name comes from the Payment Type field on the PT. 

Matching

Auto Match

• Will work if either Batch Payment Processor is started - works every 10 minutes OR
  • Will work automatically if Batch Payment Processor is stopped AND
  • Will work if the MF Automatic Matching field is not set to Do Not Match.  

URL Tokens

Wow, URL Tokens are so powerful. You can create almost any type of payment as a custom form.

If you have a simple list of products you could almost use it in lieu of setting up a full shopping cart.

    eg "buy a goat to feed a village for a year for a one off payment of $120" or similar.

Using URL Tokes for member payments is great. All they do is click on a link and enter their credit card details.

Custom Ref Fields are fantastic! Make a custom Payment URL for Payment for any one of your Custom Objects - eg Payment for Course Tuition coming from your Enrollment Object. 

Custom Fields

For	Notes	PmtTxn	Field Set	Permissions	URL Token	Opportunity
		Add the field to the PmtTxn object	Add the field to one of the custom fields field sets	Ensure sites public access profile has read / write permissions	Add the file to the URLToken Object	Add the field to the Opportunity Object
Client to Fill in	A custom field shown on the payment form and the client fills it in.
Pre-filled for Client	A custom field shown on the payment form and it is pre-filled				Pre-fill the value on the URL Token
Internal	A field on the PmtTxn that you need to see on the Opp eg you want the PmtTxn Number to appear in the Opportunity Name. Create a new field on the PmtTxn named Opp_PmtTxn__c Create a new field on the Opp named Opp_PmtTxn__c Create a workflow on create of the PmtTxn to update the Opp_PmtTxn__c to the value of the PmtTxn Nubmer. Create a workflow on create of the Opp to include the Opportunity.Opp_PmtTxn__c field in the Opp Name			If using Batch Processor